<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/include/drm/drm_mipi_dsi.h, branch linux-3.17.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-3.17.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-3.17.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2014-08-06T14:44:16Z</updated>
<entry>
<title>drm/dsi: Replace upcasting macro by function</title>
<updated>2014-08-06T14:44:16Z</updated>
<author>
<name>Thierry Reding</name>
<email>treding@nvidia.com</email>
</author>
<published>2014-08-05T07:01:32Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=77df01dcd3040a7d664d85d085d4a21533824bc1'/>
<id>urn:sha1:77df01dcd3040a7d664d85d085d4a21533824bc1</id>
<content type='text'>
Using a function instead of a macro provides proper type checking.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/dsi: Use peripheral's channel for DCS commands</title>
<updated>2014-07-22T07:06:32Z</updated>
<author>
<name>Thierry Reding</name>
<email>treding@nvidia.com</email>
</author>
<published>2014-07-21T10:28:25Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=3c523d7d38a17b17371a9ea952c04a9b65c8a357'/>
<id>urn:sha1:3c523d7d38a17b17371a9ea952c04a9b65c8a357</id>
<content type='text'>
When executing DCS commands, use the channel associated with the DSI
peripheral rather than one explicitly specified in the function call.
Devices shouldn't be able to step on each others' toes like this.

Acked-by: Andrzej Hajda &lt;a.hajda@samsung.com&gt;
Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/dsi: Make mipi_dsi_dcs_write() return ssize_t</title>
<updated>2014-07-22T07:06:16Z</updated>
<author>
<name>Thierry Reding</name>
<email>treding@nvidia.com</email>
</author>
<published>2014-07-21T10:22:26Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=371c359f83b4d19d2688e975a07dc44add307e24'/>
<id>urn:sha1:371c359f83b4d19d2688e975a07dc44add307e24</id>
<content type='text'>
This function returns the value of the struct mipi_dsi_host_ops'
.transfer() so make sure the return types are consistent.

Acked-by: Andrzej Hajda &lt;a.hajda@samsung.com&gt;
Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/dsi: Flag for non-continuous clock behavior</title>
<updated>2014-07-14T08:22:26Z</updated>
<author>
<name>Alexandre Courbot</name>
<email>acourbot@nvidia.com</email>
</author>
<published>2014-07-08T12:32:11Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=884d6a0b558c9c31fdf0d950bd07a2c804876445'/>
<id>urn:sha1:884d6a0b558c9c31fdf0d950bd07a2c804876445</id>
<content type='text'>
As per section 5.6.1 of the DSI specification, all DSI transmitters must
support continuous clock behavior on the clock lane, while non-continuous
mode support is only optional. Add a flag that allows devices to indicate
that they support non-continuous clock mode so host drivers can adapt
their behavior accordingly.

Signed-off-by: Alexandre Courbot &lt;acourbot@nvidia.com&gt;
Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/dsi: Support device shutdown</title>
<updated>2014-06-05T14:42:19Z</updated>
<author>
<name>Thierry Reding</name>
<email>treding@nvidia.com</email>
</author>
<published>2014-04-29T15:19:57Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=d16218030f7d5195fcf83a424d8e48b89b013a51'/>
<id>urn:sha1:d16218030f7d5195fcf83a424d8e48b89b013a51</id>
<content type='text'>
Hook up the MIPI DSI bus's .shutdown() function to allow drivers to
implement code that should be run when a device is shut down.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/mipi_dsi: add flags to DSI messages</title>
<updated>2014-04-04T12:24:47Z</updated>
<author>
<name>Andrzej Hajda</name>
<email>a.hajda@samsung.com</email>
</author>
<published>2014-03-28T11:52:36Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=1d96d4a6772ba8f5614a6d8de8baf6d090a9de0b'/>
<id>urn:sha1:1d96d4a6772ba8f5614a6d8de8baf6d090a9de0b</id>
<content type='text'>
This patch adds flags field to mipi_dsi_msg structure and two flags:
- MIPI_DSI_MSG_REQ_ACK - request ACK from peripheral for given message,
- MIPI_DSI_MSG_USE_LPM - use Low Power Mode to transmit message.
The first flag is usually helpful during DSI diagnostic, the second
flag is required by some peripherals during configuration phase.

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: Add MIPI DSI bus support</title>
<updated>2013-12-17T17:09:43Z</updated>
<author>
<name>Andrzej Hajda</name>
<email>a.hajda@samsung.com</email>
</author>
<published>2013-12-04T15:35:12Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=068a00233969833f1ba925e7627797489efd6041'/>
<id>urn:sha1:068a00233969833f1ba925e7627797489efd6041</id>
<content type='text'>
MIPI DSI bus allows to model DSI hosts and DSI peripherals using the
Linux driver model. DSI hosts are registered by the DSI host drivers.
During registration DSI peripherals will be created from the children
of the DSI host's device tree node. Support for registration from
board-setup code will be added later when needed.

DSI hosts expose operations which can be used by DSI peripheral drivers
to access associated devices.

Signed-off-by: Andrzej Hajda &lt;a.hajda@samsung.com&gt;
Signed-off-by: Kyungmin Park &lt;kyungmin.park@samsung.com&gt;
Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
</feed>
