On Mon, 2017-05-22 at 16:16 +0200, Hans Verkuil wrote:
> On 05/22/2017 04:14 PM, Matthias Brugger wrote:
> >
> >
> > On 22/05/17 11:09, Hans Verkuil wrote:
> >> On 05/12/2017 05:22 AM, Minghsiu Tsai wrote:
> >>
> >> Who should take care of the dtsi changes? I'm not sure who maintains the
> >> md
On 05/22/2017 04:14 PM, Matthias Brugger wrote:
>
>
> On 22/05/17 11:09, Hans Verkuil wrote:
>> On 05/12/2017 05:22 AM, Minghsiu Tsai wrote:
>>
>> Who should take care of the dtsi changes? I'm not sure who maintains the mdp
>> dts.
>
> I will take care of the dtsi patches.
>
>>
>> The driver c
On 22/05/17 11:09, Hans Verkuil wrote:
On 05/12/2017 05:22 AM, Minghsiu Tsai wrote:
Who should take care of the dtsi changes? I'm not sure who maintains the mdp
dts.
I will take care of the dtsi patches.
The driver change and the dtsi change need to be in sync, so it is probably
easiest
On 05/12/2017 05:22 AM, Minghsiu Tsai wrote:
Who should take care of the dtsi changes? I'm not sure who maintains the mdp
dts.
The driver change and the dtsi change need to be in sync, so it is probably
easiest
to merge this via one tree.
Here is my Acked-by for these three patches:
Acked-by:
Changes in v3:
- Upload patches again because forget to add v2 in title
Changes in v2:
- Update commit message
If the mdp_* nodes are under an mdp sub-node, their corresponding
platform device does not automatically get its iommu assigned properly.
Fix this by moving the mdp component nodes up a
5 matches
Mail list logo