On 14/05/2024 11:07, Krzysztof Kozlowski wrote:
On 14/05/2024 10:44, Neil Armstrong wrote:
On 13/05/2024 18:41, Dmitry Baryshkov wrote:
On Mon, 13 May 2024 at 16:17, Rob Herring wrote:
On Thu, May 09, 2024 at 11:42:50AM +0200, Krzysztof Kozlowski wrote:
Hi,
Cleanups for display panel bindi
On 14/05/2024 10:44, Neil Armstrong wrote:
> On 13/05/2024 18:41, Dmitry Baryshkov wrote:
>> On Mon, 13 May 2024 at 16:17, Rob Herring wrote:
>>>
>>> On Thu, May 09, 2024 at 11:42:50AM +0200, Krzysztof Kozlowski wrote:
Hi,
Cleanups for display panel bindings.
Rob, maybe yo
On 13/05/2024 18:41, Dmitry Baryshkov wrote:
On Mon, 13 May 2024 at 16:17, Rob Herring wrote:
On Thu, May 09, 2024 at 11:42:50AM +0200, Krzysztof Kozlowski wrote:
Hi,
Cleanups for display panel bindings.
Rob, maybe you could take entire set if it applies? I based it on
linux-next, so letl m
On Mon, 13 May 2024 at 16:17, Rob Herring wrote:
>
> On Thu, May 09, 2024 at 11:42:50AM +0200, Krzysztof Kozlowski wrote:
> > Hi,
> >
> > Cleanups for display panel bindings.
> >
> > Rob, maybe you could take entire set if it applies? I based it on
> > linux-next, so letl me know if I need to reba
On Thu, May 09, 2024 at 11:42:50AM +0200, Krzysztof Kozlowski wrote:
> Hi,
>
> Cleanups for display panel bindings.
>
> Rob, maybe you could take entire set if it applies? I based it on
> linux-next, so letl me know if I need to rebase on your for-next.
Applied. These 2 don't exist in my tree:
Hi,
Cleanups for display panel bindings.
Rob, maybe you could take entire set if it applies? I based it on
linux-next, so letl me know if I need to rebase on your for-next.
I actually do not know if devices affected here take more than one chip
select or DSI virtual channel number. I assume DTS
