Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement

2022-06-13 Thread Melissa Wen
On 06/10, Javier Martinez Canillas wrote: > Hello Melissa, > > On 6/10/22 13:05, Melissa Wen wrote: > > On 06/08, Javier Martinez Canillas wrote: > > [snip] > > > > > Hi Javier, > > > > Thanks for waiting a little. > > > > Stefan guided me to the missing part and I'm okay on this serie. > > >

Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement

2022-06-10 Thread Javier Martinez Canillas
Hello Melissa, On 6/10/22 13:05, Melissa Wen wrote: > On 06/08, Javier Martinez Canillas wrote: [snip] > > Hi Javier, > > Thanks for waiting a little. > > Stefan guided me to the missing part and I'm okay on this serie. > No worries and thanks for the testing. > If there's any r-b missing

Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement

2022-06-10 Thread Melissa Wen
On 06/08, Javier Martinez Canillas wrote: > Hello Melissa, > > On 6/8/22 17:51, Melissa Wen wrote: > > [snip] > > >>> > >>> I can take the last 3 patches through the Broadcom ARM SoC pull request, > >>> but the first three should probably go via the DRM tree unless you want > >>> me to merge t

Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement

2022-06-10 Thread Melissa Wen
On 06/09, Stefan Wahren wrote: > Hi Melissa, > > Am 08.06.22 um 14:51 schrieb Melissa Wen: > > On 06/03, Peter Robinson wrote: > > > This is a follow up from my v4 patchset. The power management pieces have > > > been split out to a separate independent set of patches by Stefan [1]. > > > This >

Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement

2022-06-08 Thread Stefan Wahren
Hi Melissa, Am 08.06.22 um 14:51 schrieb Melissa Wen: On 06/03, Peter Robinson wrote: This is a follow up from my v4 patchset. The power management pieces have been split out to a separate independent set of patches by Stefan [1]. This version 5 of the DRM patches are independent and given the

Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement

2022-06-08 Thread Javier Martinez Canillas
Hello Melissa, On 6/8/22 17:51, Melissa Wen wrote: [snip] >>> >>> I can take the last 3 patches through the Broadcom ARM SoC pull request, >>> but the first three should probably go via the DRM tree unless you want >>> me to merge them all? >> >> I can merge the first 3 patches through the drm

Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement

2022-06-08 Thread Melissa Wen
On 06/08, Javier Martinez Canillas wrote: > Hello Florian, > > On 6/8/22 11:26, Florian Fainelli wrote: > > > > > > On 6/3/2022 11:26 AM, Peter Robinson wrote: > >> This is a follow up from my v4 patchset. The power management pieces have > >> been split out to a separate independent set of patc

Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement

2022-06-08 Thread Melissa Wen
On 06/03, Peter Robinson wrote: > This is a follow up from my v4 patchset. The power management pieces have > been split out to a separate independent set of patches by Stefan [1]. This > version 5 of the DRM patches are independent and given the V3D driver has > been upstream for some time the two

Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement

2022-06-08 Thread Javier Martinez Canillas
Hello Florian, On 6/8/22 11:26, Florian Fainelli wrote: > > > On 6/3/2022 11:26 AM, Peter Robinson wrote: >> This is a follow up from my v4 patchset. The power management pieces have >> been split out to a separate independent set of patches by Stefan [1]. This >> version 5 of the DRM patches ar

Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement

2022-06-08 Thread Florian Fainelli
On 6/3/2022 11:26 AM, Peter Robinson wrote: This is a follow up from my v4 patchset. The power management pieces have been split out to a separate independent set of patches by Stefan [1]. This version 5 of the DRM patches are independent and given the V3D driver has been upstream for some tim

[PATCH v6 0/6] Raspberry PI 4 V3D enablement

2022-06-03 Thread Peter Robinson
This is a follow up from my v4 patchset. The power management pieces have been split out to a separate independent set of patches by Stefan [1]. This version 5 of the DRM patches are independent and given the V3D driver has been upstream for some time the two patches to enable it in defconfigs can