<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/drivers/gpu/drm/exynos/exynos_drm_fimd.c, branch linux-4.17.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.17.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.17.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2017-08-25T05:30:27Z</updated>
<entry>
<title>drm/exynos: simplify set_pixfmt() in DECON and FIMD drivers</title>
<updated>2017-08-25T05:30:27Z</updated>
<author>
<name>Tobias Jakobi</name>
<email>tjakobi@math.uni-bielefeld.de</email>
</author>
<published>2017-08-22T14:19:44Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=5b7b1b7fa10145c014750b09ff4cf31ac4e1843a'/>
<id>urn:sha1:5b7b1b7fa10145c014750b09ff4cf31ac4e1843a</id>
<content type='text'>
DRM core already checks the validity of the pixelformat.

Signed-off-by: Tobias Jakobi &lt;tjakobi@math.uni-bielefeld.de&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos: consistent use of cpp</title>
<updated>2017-08-25T05:06:48Z</updated>
<author>
<name>Tobias Jakobi</name>
<email>tjakobi@math.uni-bielefeld.de</email>
</author>
<published>2017-08-22T14:19:43Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=ac60944ccf2388901412a0c9a0e7e3e4b56520a4'/>
<id>urn:sha1:ac60944ccf2388901412a0c9a0e7e3e4b56520a4</id>
<content type='text'>
A recent commit (272725c7db4da1fd3229d944fc76d2e98e3a144e) has removed
the use of 'bits_per_pixel' in DRM. However the corresponding Exynos
driver code still uses the ambiguous 'bpp', even though it is now
initialized from fb-&gt;cpp[0].

Consistenly use 'cpp' in FIMD, DECON7 and DECON5433 drivers.

Signed-off-by: Tobias Jakobi &lt;tjakobi@math.uni-bielefeld.de&gt;
</content>
</entry>
<entry>
<title>drm/exynos: kill mode_set_nofb callback</title>
<updated>2017-06-01T07:21:35Z</updated>
<author>
<name>Andrzej Hajda</name>
<email>a.hajda@samsung.com</email>
</author>
<published>2017-03-15T14:41:07Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=c7954aa6f79b1fff83453e33edb359c236eea5df'/>
<id>urn:sha1:c7954aa6f79b1fff83453e33edb359c236eea5df</id>
<content type='text'>
All Exynos CRTCs are fully configured by .enable callback. The only users
of mode_set_nofb actually did nothing in their callbacks - they immediately
returned because devices were in suspend state - mode_set_nofb is always
called on disabled device.

Signed-off-by: Andrzej Hajda &lt;a.hajda@samsung.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos: kill pipe field from drivers contexts</title>
<updated>2017-06-01T07:21:34Z</updated>
<author>
<name>Andrzej Hajda</name>
<email>a.hajda@samsung.com</email>
</author>
<published>2017-03-15T14:41:06Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=2949390eb1be95633afdc39923f53ea5b326242a'/>
<id>urn:sha1:2949390eb1be95633afdc39923f53ea5b326242a</id>
<content type='text'>
Since possible_crtcs are set by Exynos core helper pipe fields have no
raison d'etre. The only place it was used, as a hack, is
fimd_clear_channels, to avoid calling drm_crtc_handle_vblank, but DRM core
has already other protection mechanism (vblank-&gt;enabled), so it could be
safely removed.

Signed-off-by: Andrzej Hajda &lt;a.hajda@samsung.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos: set plane possible_crtcs in exynos_plane_init</title>
<updated>2017-06-01T07:21:34Z</updated>
<author>
<name>Andrzej Hajda</name>
<email>a.hajda@samsung.com</email>
</author>
<published>2017-03-15T14:41:05Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=2c82607b56ad7035077dbb0d37093d8f2b21e235'/>
<id>urn:sha1:2c82607b56ad7035077dbb0d37093d8f2b21e235</id>
<content type='text'>
All Exynos planes are assigned to exactly one CRTC, it allows to simplify
initialization by moving setting of possible_crtcs to exynos_plane_init.

Signed-off-by: Andrzej Hajda &lt;a.hajda@samsung.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos: kill exynos_drm_private::pipe</title>
<updated>2017-06-01T07:21:34Z</updated>
<author>
<name>Andrzej Hajda</name>
<email>a.hajda@samsung.com</email>
</author>
<published>2017-03-15T14:41:04Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=f44d3d2f84d6bc6b685f40a18e08b4bdcaf3d1ef'/>
<id>urn:sha1:f44d3d2f84d6bc6b685f40a18e08b4bdcaf3d1ef</id>
<content type='text'>
The field duplicates drm_dev-&gt;mode_config.num_crtc.

Signed-off-by: Andrzej Hajda &lt;a.hajda@samsung.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos: kill exynos_drm_crtc::pipe</title>
<updated>2017-06-01T07:21:34Z</updated>
<author>
<name>Andrzej Hajda</name>
<email>a.hajda@samsung.com</email>
</author>
<published>2017-05-29T01:05:25Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=d644951c2b2b013751e7dd5efe886340e196fab4'/>
<id>urn:sha1:d644951c2b2b013751e7dd5efe886340e196fab4</id>
<content type='text'>
Since crtc index is stored in drm_crtc pipe field became redundant.
The patch beside removing the field simplifies also
exynos_drm_crtc_get_pipe_from_type.

Signed-off-by: Andrzej Hajda &lt;a.hajda@samsung.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos/fimd: signal frame done interrupt at front porch</title>
<updated>2017-03-21T04:17:22Z</updated>
<author>
<name>Andrzej Hajda</name>
<email>a.hajda@samsung.com</email>
</author>
<published>2017-03-14T08:27:59Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=82a01783252be726d76cdbbababc16540f582cec'/>
<id>urn:sha1:82a01783252be726d76cdbbababc16540f582cec</id>
<content type='text'>
VBLANK interrupt should be signalled as soon as scanout ends, front porch
is the best moment.

Signed-off-by: Andrzej Hajda &lt;a.hajda@samsung.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos: move crtc event handling to drivers callbacks</title>
<updated>2017-03-21T04:17:21Z</updated>
<author>
<name>Andrzej Hajda</name>
<email>a.hajda@samsung.com</email>
</author>
<published>2017-03-14T08:27:56Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=a392276d1dec63e5aabe6f527c37de29a729559a'/>
<id>urn:sha1:a392276d1dec63e5aabe6f527c37de29a729559a</id>
<content type='text'>
CRTC event is currently send with next vblank, or instantly in case crtc
is being disabled. This approach usually works, but in corner cases it can
result in premature event generation. Only device driver is able to verify
if the event can be sent. This patch is a first step in that direction - it
moves event handling to the drivers.

Signed-off-by: Andrzej Hajda &lt;a.hajda@samsung.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos: Remove support for Exynos4415 (SoC not supported anymore)</title>
<updated>2017-03-21T04:17:21Z</updated>
<author>
<name>Krzysztof Kozlowski</name>
<email>krzk@kernel.org</email>
</author>
<published>2017-03-11T18:04:16Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=6bdc92ee4980ca10171a8de338fad612f00bb48f'/>
<id>urn:sha1:6bdc92ee4980ca10171a8de338fad612f00bb48f</id>
<content type='text'>
Support for Exynos4415 is going away because there are no internal nor
external users.

Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"),
the platform cannot be instantiated so remove also the drivers.

Signed-off-by: Krzysztof Kozlowski &lt;krzk@kernel.org&gt;
Acked-by: Kukjin Kim &lt;kgene@kernel.org&gt;
Acked-by: Rob Herring &lt;robh@kernel.org&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
</feed>
