<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/linux.git/drivers/gpu/drm/fsl-dcu, branch dev-4.6</title>
<subtitle>Intel OpenBMC Linux kernel source tree (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-4.6</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-4.6'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/'/>
<updated>2016-03-04T17:16:45+00:00</updated>
<entry>
<title>drm/fsl-dcu: removed optional dummy crtc mode_fixup function.</title>
<updated>2016-03-04T17:16:45+00:00</updated>
<author>
<name>Carlos Palminha</name>
<email>CARLOS.PALMINHA@synopsys.com</email>
</author>
<published>2016-02-16T14:19:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=de3aa0aae639560dfe394aecdcb1f10c79c96b7a'/>
<id>urn:sha1:de3aa0aae639560dfe394aecdcb1f10c79c96b7a</id>
<content type='text'>
This patch set nukes all the dummy crtc mode_fixup implementations.
(made on top of Daniel topic/drm-misc branch)

Signed-off-by: Carlos Palminha &lt;palminha@synopsys.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/a9827a57b25509dae29c0e8d09a9063a11970647.1455630967.git.palminha@synopsys.com
</content>
</entry>
<entry>
<title>drm/fsl-dcu: fix register initialization</title>
<updated>2016-02-26T00:13:16+00:00</updated>
<author>
<name>Stefan Agner</name>
<email>stefan@agner.ch</email>
</author>
<published>2016-01-15T01:24:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=f76b9873d7db0afb51f2df389a99284ef484b86f'/>
<id>urn:sha1:f76b9873d7db0afb51f2df389a99284ef484b86f</id>
<content type='text'>
The layer enumeration start with 0 (0-15 for LS1021a and 0-63 for
Vybrid) whereas the register enumeration start from 1 (1-10 for
LS1021a and 1-9 for Vybrid). The loop started off from 0 for both
iterations and initialized the number of layers inclusive, which
is one layer too many.

All extensively written registers seem to be unassigned, it seems
that the write to those registers did not do any harm in practice.

Signed-off-by: Stefan Agner &lt;stefan@agner.ch&gt;
</content>
</entry>
<entry>
<title>drm/fsl-dcu: use mode flags for hsync/vsync polarity</title>
<updated>2016-02-26T00:13:16+00:00</updated>
<author>
<name>Stefan Agner</name>
<email>stefan@agner.ch</email>
</author>
<published>2015-11-18T03:10:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=4bc390c6337b6c73e0b44895e0ade7212f2815bf'/>
<id>urn:sha1:4bc390c6337b6c73e0b44895e0ade7212f2815bf</id>
<content type='text'>
The current default configuration is as follows:
- Invert VSYNC signal (active LOW)
- Invert HSYNC signal (active LOW)

The mode flags allow to specify the required polarity per
mode. Furthermore, none of the current driver settings is
actually a standard polarity.

This patch applies the current driver default polarities as
explicit flags to the display which has been introduced with
the driver (NEC WQVGA "nec,nl4827hc19-05b"). The driver now
also parses the flags field and applies the configuration
accordingly, by using the following values as standard
polarities: (e.g. when no flags are specified):
- VSYNC signal not inverted (active HIGH)
- HSYNC signal not inverted (active HIGH)

Acked-by: Thierry Reding &lt;treding@nvidia.com&gt;
Signed-off-by: Stefan Agner &lt;stefan@agner.ch&gt;
</content>
</entry>
<entry>
<title>drm/fsl-dcu: fix alpha blending</title>
<updated>2016-02-26T00:13:16+00:00</updated>
<author>
<name>Stefan Agner</name>
<email>stefan@agner.ch</email>
</author>
<published>2015-11-18T22:47:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=69855819c7683c88e7f136f98b790392ebf9fe88'/>
<id>urn:sha1:69855819c7683c88e7f136f98b790392ebf9fe88</id>
<content type='text'>
Fix alpha blending by enabling alpha blending for the whole frame if
a color mode with alpha channel is selected (DRM_FORMAT_ARGB*). Also
support color modes without alpha channel (DRM_FORMAT_XRGB*) by just
not enabling alpha blending on layer level.

Signed-off-by: Stefan Agner &lt;stefan@agner.ch&gt;
</content>
</entry>
<entry>
<title>drm/fsl-dcu: mask all interrupts on initialization</title>
<updated>2016-02-26T00:13:16+00:00</updated>
<author>
<name>Stefan Agner</name>
<email>stefan@agner.ch</email>
</author>
<published>2015-11-19T01:27:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=638c93f61988c6fcc821646399f1fdd3895a34a2'/>
<id>urn:sha1:638c93f61988c6fcc821646399f1fdd3895a34a2</id>
<content type='text'>
The state of the interrupt mask register on initialization is
unknown, e.g. U-Boot could already used the DCU. So depending on
the boot loader, the outcome of the interrupt mask register could
be different. A defined state is much more preferable. Also, there
is no value in keeping interrupts enabled which we don't need.
Therefor, mask all interrupts on initialization.

Signed-off-by: Stefan Agner &lt;stefan@agner.ch&gt;
</content>
</entry>
<entry>
<title>drm/fsl-dcu: handle initialization errors properly</title>
<updated>2016-02-26T00:13:16+00:00</updated>
<author>
<name>Stefan Agner</name>
<email>stefan@agner.ch</email>
</author>
<published>2015-11-17T00:25:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=7566e247672d6ab67ce2a4c0fe03c17d695481b7'/>
<id>urn:sha1:7566e247672d6ab67ce2a4c0fe03c17d695481b7</id>
<content type='text'>
If initialization fails (e.g. due to missing panel node or deferred
probe) make sure to roll-back all operations and return the error
code.

Signed-off-by: Stefan Agner &lt;stefan@agner.ch&gt;
</content>
</entry>
<entry>
<title>drm/fsl-dcu: avoid memory leak on errors</title>
<updated>2016-02-26T00:13:16+00:00</updated>
<author>
<name>Stefan Agner</name>
<email>stefan@agner.ch</email>
</author>
<published>2015-11-16T23:43:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=72cc05a5182079a2506c85f2cf4782dca3ac7e21'/>
<id>urn:sha1:72cc05a5182079a2506c85f2cf4782dca3ac7e21</id>
<content type='text'>
Improve error handling during CRTC initialization. Especially avoid
memory leaks in the primary plane initialization error path.

Signed-off-by: Stefan Agner &lt;stefan@agner.ch&gt;
</content>
</entry>
<entry>
<title>drm/fsl-dcu: remove regmap return value checks</title>
<updated>2016-02-26T00:13:16+00:00</updated>
<author>
<name>Stefan Agner</name>
<email>stefan@agner.ch</email>
</author>
<published>2015-11-19T00:50:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=e291d2985b2f7d7e0eb0953d8812d3a06f111ec2'/>
<id>urn:sha1:e291d2985b2f7d7e0eb0953d8812d3a06f111ec2</id>
<content type='text'>
It is not common to do regmap return value checks, especially not
for memory mapped device. We can rule out most error returns since
the conditions are static and we know they are ok (e.g. offset
aligned to register stride). Also without proper error handling
they are not really valuable for the user. Hence remove most of
them.

The check in the interrupt handler is worth keeping since a
volatile register won't be readable in case register caching is
still enabled.

Signed-off-by: Stefan Agner &lt;stefan@agner.ch&gt;
</content>
</entry>
<entry>
<title>drm/fsl-dcu: specify volatile registers</title>
<updated>2016-02-26T00:13:16+00:00</updated>
<author>
<name>Stefan Agner</name>
<email>stefan@agner.ch</email>
</author>
<published>2015-11-18T02:05:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=efb8b49196c0cb0723024182e04072abaec96cdf'/>
<id>urn:sha1:efb8b49196c0cb0723024182e04072abaec96cdf</id>
<content type='text'>
Since we are using cached registers, we need to specify volatile
registers explicitly to avoid reading their value from the cache.
This allows to read the correct interrupt status in fsl_dcu_drm_irq
and clear the asserted bits only.

Signed-off-by: Stefan Agner &lt;stefan@agner.ch&gt;
</content>
</entry>
<entry>
<title>drm: fsl-dcu: Fix no fb check bug</title>
<updated>2016-02-26T00:13:16+00:00</updated>
<author>
<name>Meng Yi</name>
<email>meng.yi@nxp.com</email>
</author>
<published>2016-01-06T04:12:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=a36c9867d44718487262643cdefd12a386841b41'/>
<id>urn:sha1:a36c9867d44718487262643cdefd12a386841b41</id>
<content type='text'>
For state-&gt;fb or state-&gt;crtc may be NULL in fsl_dcu_drm_plane_atomic_check
function, if so, return 0.

Signed-off-by: Meng Yi &lt;meng.yi@nxp.com&gt;
Signed-off-by: Jianwei Wang &lt;jianwei.wang.chn@gmail.com&gt;
Signed-off-by: Stefan Agner &lt;stefan@agner.ch&gt;
</content>
</entry>
</feed>
