<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/drivers/gpu/drm/msm/mdp, branch linux-4.1.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.1.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.1.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2015-05-21T04:31:45Z</updated>
<entry>
<title>drm/msm/mdp5: fix incorrect parameter for msm_framebuffer_iova()</title>
<updated>2015-05-21T04:31:45Z</updated>
<author>
<name>Stephane Viau</name>
<email>sviau@codeaurora.org</email>
</author>
<published>2015-05-20T14:57:27Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=755c814a7d826257d5488cfaa801ec19377c472a'/>
<id>urn:sha1:755c814a7d826257d5488cfaa801ec19377c472a</id>
<content type='text'>
The index of -&gt;planes[] array (3rd parameter) cannot be equal to MAX_PLANE.
This looks like a typo that is now fixed.

Signed-off-by: Stephane Viau &lt;sviau@codeaurora.org&gt;
Acked-by: Rob Clark &lt;robdclark@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/msm/mdp5: Fix iteration on INTF config array</title>
<updated>2015-05-14T15:29:20Z</updated>
<author>
<name>Stephane Viau</name>
<email>sviau@codeaurora.org</email>
</author>
<published>2015-04-30T17:45:52Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=fe34464df5e8bd4b09db170477f32db4eade0444'/>
<id>urn:sha1:fe34464df5e8bd4b09db170477f32db4eade0444</id>
<content type='text'>
The current iteration in get_dsi_id_from_intf() is wrong:
instead of iterating until hw_cfg-&gt;intf.count, we need to iterate
until MDP5_INTF_NUM_MAX here.

Let's take the example of msm8x16:

 hw_cfg-&gt;intf.count = 1
 intfs[0] = INTF_Disabled
 intfs[1] = INTF_DSI

If we stop iterating once i reaches hw_cfg-&gt;intf.count (== 1),
we will miss the test for intfs[1].

Actually, this hw_cfg-&gt;intf.count entry is quite confusing and is not
(or *should not be*) used anywhere else; let's remove it.

Signed-off-by: Stephane Viau &lt;sviau@codeaurora.org&gt;
</content>
</entry>
<entry>
<title>drm/msm/mdp5: Enable DSI connector in msm drm driver</title>
<updated>2015-04-01T23:29:38Z</updated>
<author>
<name>Hai Li</name>
<email>hali@codeaurora.org</email>
</author>
<published>2015-03-26T23:25:17Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=d5af49c92a8aff8236e7b0bb35e9af364000c017'/>
<id>urn:sha1:d5af49c92a8aff8236e7b0bb35e9af364000c017</id>
<content type='text'>
This change adds the support in mdp5 kms driver for single
and dual DSI. Dual DSI case depends on the framework API
and sequence change to support dual data path.

v1: Initial change
v2: Address Rob Clark's comment
- Separate command mode encoder to a new file mdp5_cmd_encoder.c
- Rebase to not depend on msm_drm_sub_dev change

Signed-off-by: Hai Li &lt;hali@codeaurora.org&gt;
Signed-off-by: Rob Clark &lt;robdclark@gmail.com&gt;
</content>
</entry>
<entry>
<title>drm/msm/mdp5: Move *_modeset_init out of construct_encoder function</title>
<updated>2015-04-01T23:29:37Z</updated>
<author>
<name>Hai Li</name>
<email>hali@codeaurora.org</email>
</author>
<published>2015-03-26T23:25:14Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=5722a9e303be25adbe25c174f66c5e1e9e17c276'/>
<id>urn:sha1:5722a9e303be25adbe25c174f66c5e1e9e17c276</id>
<content type='text'>
This change is to make the content in construct_encoder reflect its
name.
Also, DSI connector may be connected to video mode or command mode
encoder, so that 2 different encoders need to be constructed for DSI.

Signed-off-by: Hai Li &lt;hali@codeaurora.org&gt;
Signed-off-by: Rob Clark &lt;robdclark@gmail.com&gt;
</content>
</entry>
<entry>
<title>drm/msm/mdp5: Remove CTL flush dummy bits</title>
<updated>2015-04-01T23:29:37Z</updated>
<author>
<name>Stephane Viau</name>
<email>sviau@codeaurora.org</email>
</author>
<published>2015-03-24T13:30:02Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=531db9ff3d3aabc36772bb02a9c636e398d0f21c'/>
<id>urn:sha1:531db9ff3d3aabc36772bb02a9c636e398d0f21c</id>
<content type='text'>
This TODO can now be removed and replaced by the previous patch
"drm/msm/mdp5: Update headers (add CTL flush bits)"

Signed-off-by: Stephane Viau &lt;sviau@codeaurora.org&gt;
Signed-off-by: Rob Clark &lt;robdclark@gmail.com&gt;
</content>
</entry>
<entry>
<title>drm/msm/mdp5: Update headers (add CTL flush bits)</title>
<updated>2015-04-01T23:29:36Z</updated>
<author>
<name>Stephane Viau</name>
<email>sviau@codeaurora.org</email>
</author>
<published>2015-03-24T13:30:01Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=87ed66c41441589b9718331410ceea7aeb8a740b'/>
<id>urn:sha1:87ed66c41441589b9718331410ceea7aeb8a740b</id>
<content type='text'>
Some upcoming targets have more bits to set in CTL_FLUSH
registers.

Example: msm8x16 needs to set TIMING1 bit so that some of the
INTF1's interface registers get flushed.

Signed-off-by: Stephane Viau &lt;sviau@codeaurora.org&gt;
Signed-off-by: Rob Clark &lt;robdclark@gmail.com&gt;
</content>
</entry>
<entry>
<title>drm/msm/mdp5: Add hardware configuration for msm8x16</title>
<updated>2015-04-01T23:29:36Z</updated>
<author>
<name>Stephane Viau</name>
<email>sviau@codeaurora.org</email>
</author>
<published>2015-03-24T19:06:02Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=02dfd9d2ba2b86068a23fb1ff8b9b633a61e732e'/>
<id>urn:sha1:02dfd9d2ba2b86068a23fb1ff8b9b633a61e732e</id>
<content type='text'>
This change adds the hw configuration for msm8x16 chipsets in
mdp5_cfg module.

Note that only one external display interface is present in this
configuration (DSI) but has not been enabled yet. It will be enabled
once drm/msm driver supports DSI connectors.

v2: add CTL flush register's hardware mask [pointed by Archit]

Signed-off-by: Stephane Viau &lt;sviau@codeaurora.org&gt;
Signed-off-by: Rob Clark &lt;robdclark@gmail.com&gt;
</content>
</entry>
<entry>
<title>drm/msm/mdp5: Get SMP client list from mdp5_cfg</title>
<updated>2015-04-01T23:29:36Z</updated>
<author>
<name>Stephane Viau</name>
<email>sviau@codeaurora.org</email>
</author>
<published>2015-03-09T13:11:06Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=6fa6acdfa37737fce6f69a7aa50606825ccea5ea'/>
<id>urn:sha1:6fa6acdfa37737fce6f69a7aa50606825ccea5ea</id>
<content type='text'>
SMP blocks are configured for specific client IDs (ports).
These client IDs can be different from one chip to another for a
given pipe.

e.g.: DMA0 pipe fetch Y component is connected to:
 - port #10 for MDP5 v1.3
 - port #4 for MDP5 v1.6

In order to be compatible for upcoming versions of MDP5, the
client ID list is passed through the MDP5 config module rather
than using a list of hard-coded enum values.

Signed-off-by: Stephane Viau &lt;sviau@codeaurora.org&gt;
Signed-off-by: Rob Clark &lt;robdclark@gmail.com&gt;
</content>
</entry>
<entry>
<title>drm/msm/mdp5: Update headers (remove enum mdp5_client_id)</title>
<updated>2015-04-01T23:29:36Z</updated>
<author>
<name>Stephane Viau</name>
<email>sviau@codeaurora.org</email>
</author>
<published>2015-03-09T13:11:05Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=de50d351b37ba43a8d9e944e78c4df37f88d4ae2'/>
<id>urn:sha1:de50d351b37ba43a8d9e944e78c4df37f88d4ae2</id>
<content type='text'>
This patch contains the generated header file of the following
change "drm/msm/mdp5: Get SMP client list from mdp5_cfg".

Signed-off-by: Stephane Viau &lt;sviau@codeaurora.org&gt;
Signed-off-by: Rob Clark &lt;robdclark@gmail.com&gt;
</content>
</entry>
<entry>
<title>drm/msm/mdp5: Separate MDP5 domain from MDSS domain</title>
<updated>2015-04-01T23:29:36Z</updated>
<author>
<name>Stephane Viau</name>
<email>sviau@codeaurora.org</email>
</author>
<published>2015-03-09T13:11:04Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=f52538125e4dfb2a74f2efd915430d6fc39d0124'/>
<id>urn:sha1:f52538125e4dfb2a74f2efd915430d6fc39d0124</id>
<content type='text'>
MDP block is actually contained inside the MDSS block. For some
chipsets, the base address of the MDP registers is different from the
current (assumed) 0x100 offset.

Like CTL and LM blocks, this changes introduce a dynamic offset
for the MDP instance, which can be found out at runtime, once the
MDSS HW version is read.

Signed-off-by: Stephane Viau &lt;sviau@codeaurora.org&gt;
Signed-off-by: Rob Clark &lt;robdclark@gmail.com&gt;
</content>
</entry>
</feed>
