[GIT,PULL] ARM: dts updates for arm 32 bits for v4.20

Message ID 0195dc38-908e-c403-5f12-d266a037ca1b@gmail.com
State New
Headers show
Series
  • [GIT,PULL] ARM: dts updates for arm 32 bits for v4.20
Related show

Pull-request

https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/

Message

Matthias Brugger Sept. 29, 2018, 3:18 p.m.
Hi Olof and Arnd,

Please take the following pull request into account.

Thanks a lot,
Matthias


---

The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:

  Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/
tags/v4.19-next-dts32

for you to fetch changes up to 5646a2f6d584e80bd4555c2ce3e286b35b9eaa61:

  arm: dts: mt7623: add jpeg decoder device node (2018-09-25 17:44:35 +0200)

----------------------------------------------------------------
mt7623:
- add pmu node
- add subsystem clocks
- add nodes needed for iommu
- add node for the jpeg decoder

----------------------------------------------------------------
Ryder Lee (4):
      arm: dts: mt7623: add a performance counter unit device node
      arm: dts: mt7623: update subsystem clock controller device nodes
      arm: dts: mt7623: add iommu/smi device nodes
      arm: dts: mt7623: add jpeg decoder device node

 arch/arm/boot/dts/mt7623.dtsi | 124 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 124 insertions(+)

Comments

Arnd Bergmann Oct. 2, 2018, 9:12 a.m. | #1
On Sat, Sep 29, 2018 at 5:18 PM Matthias Brugger <matthias.bgg@gmail.com> wrote:

> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
>   Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>
> are available in the Git repository at:
>
>   https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/
> tags/v4.19-next-dts32
>
> for you to fetch changes up to 5646a2f6d584e80bd4555c2ce3e286b35b9eaa61:
>
>   arm: dts: mt7623: add jpeg decoder device node (2018-09-25 17:44:35 +0200)
>
> ----------------------------------------------------------------
> mt7623:
> - add pmu node
> - add subsystem clocks
> - add nodes needed for iommu
> - add node for the jpeg decoder

None of these (aside from the pmu) seem to have DT bindings
or drivers posted on the list. Can you explain why that is and what
the plan is for supporting them?

Not pulled for now.

       Arnd
Matthias Brugger Oct. 2, 2018, 10:34 a.m. | #2
On 02/10/2018 11:12, Arnd Bergmann wrote:
> On Sat, Sep 29, 2018 at 5:18 PM Matthias Brugger <matthias.bgg@gmail.com> wrote:
> 
>> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>>
>>   Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>>
>> are available in the Git repository at:
>>
>>   https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/
>> tags/v4.19-next-dts32
>>
>> for you to fetch changes up to 5646a2f6d584e80bd4555c2ce3e286b35b9eaa61:
>>
>>   arm: dts: mt7623: add jpeg decoder device node (2018-09-25 17:44:35 +0200)
>>
>> ----------------------------------------------------------------
>> mt7623:
>> - add pmu node
>> - add subsystem clock>> - add nodes needed for iommu
>> - add node for the jpeg decoder
> 
> None of these (aside from the pmu) seem to have DT bindings
> or drivers posted on the list. Can you explain why that is and what
> the plan is for supporting them?
> 

We rely on the fallback compatible here, as mt2701 and mt7623 are identically in
most of their components. If you require to get the bindings documented before
merging the DT, then I propose to drop the pull request for now.

Other option would be to get the bindings documented in v4.21. AFAIK up to now
there haven't been sent any patches to update the bindings.

Regards,
Matthias
Arnd Bergmann Oct. 2, 2018, 11:10 a.m. | #3
On Tue, Oct 2, 2018 at 12:34 PM Matthias Brugger <matthias.bgg@gmail.com> wrote:
> On 02/10/2018 11:12, Arnd Bergmann wrote:
> > On Sat, Sep 29, 2018 at 5:18 PM Matthias Brugger <matthias.bgg@gmail.com> wrote:
> >
> >> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
> >>
> >>   Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
> >>
> >> are available in the Git repository at:
> >>
> >>   https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/
> >> tags/v4.19-next-dts32
> >>
> >> for you to fetch changes up to 5646a2f6d584e80bd4555c2ce3e286b35b9eaa61:
> >>
> >>   arm: dts: mt7623: add jpeg decoder device node (2018-09-25 17:44:35 +0200)
> >>
> >> ----------------------------------------------------------------
> >> mt7623:
> >> - add pmu node
> >> - add subsystem clock>> - add nodes needed for iommu
> >> - add node for the jpeg decoder
> >
> > None of these (aside from the pmu) seem to have DT bindings
> > or drivers posted on the list. Can you explain why that is and what
> > the plan is for supporting them?
> >
>
> We rely on the fallback compatible here, as mt2701 and mt7623 are identically in
> most of their components. If you require to get the bindings documented before
> merging the DT, then I propose to drop the pull request for now.
>
> Other option would be to get the bindings documented in v4.21. AFAIK up to now
> there haven't been sent any patches to update the bindings.

Ok, I missed that the mt2701 strings are all documented and used in drivers,
so I don't think it's a problem to merge your changes. How about you add
another patch to your tree to update the respective bindings? I think that
should be fine even for 4.20.

        Arnd
Matthias Brugger Oct. 3, 2018, 9:18 a.m. | #4
On 02/10/2018 13:10, Arnd Bergmann wrote:
> On Tue, Oct 2, 2018 at 12:34 PM Matthias Brugger <matthias.bgg@gmail.com> wrote:
>> On 02/10/2018 11:12, Arnd Bergmann wrote:
>>> On Sat, Sep 29, 2018 at 5:18 PM Matthias Brugger <matthias.bgg@gmail.com> wrote:
>>>
>>>> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>>>>
>>>>   Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>>>>
>>>> are available in the Git repository at:
>>>>
>>>>   https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/
>>>> tags/v4.19-next-dts32
>>>>
>>>> for you to fetch changes up to 5646a2f6d584e80bd4555c2ce3e286b35b9eaa61:
>>>>
>>>>   arm: dts: mt7623: add jpeg decoder device node (2018-09-25 17:44:35 +0200)
>>>>
>>>> ----------------------------------------------------------------
>>>> mt7623:
>>>> - add pmu node
>>>> - add subsystem clock>> - add nodes needed for iommu
>>>> - add node for the jpeg decoder
>>>
>>> None of these (aside from the pmu) seem to have DT bindings
>>> or drivers posted on the list. Can you explain why that is and what
>>> the plan is for supporting them?
>>>
>>
>> We rely on the fallback compatible here, as mt2701 and mt7623 are identically in
>> most of their components. If you require to get the bindings documented before
>> merging the DT, then I propose to drop the pull request for now.
>>
>> Other option would be to get the bindings documented in v4.21. AFAIK up to now
>> there haven't been sent any patches to update the bindings.
> 
> Ok, I missed that the mt2701 strings are all documented and used in drivers,
> so I don't think it's a problem to merge your changes. How about you add
> another patch to your tree to update the respective bindings? I think that
> should be fine even for 4.20.
> 

I just send a series of 4 patches which updates the binding documentation. I
realized that there were more bindings missing, hopefully I caught them all.

The series applies cleanly against linux-next, so I suppose there won't be any
merge conflicts if you decide to take it through your tree for v4.20.

If you want to send me another pull request, just let me know.

Regards,
Matthias
Arnd Bergmann Oct. 4, 2018, 2:55 p.m. | #5
On Wed, Oct 3, 2018 at 11:18 AM Matthias Brugger <matthias.bgg@gmail.com> wrote:
> On 02/10/2018 13:10, Arnd Bergmann wrote:
> > On Tue, Oct 2, 2018 at 12:34 PM Matthias Brugger <matthias.bgg@gmail.com> wrote:
> >> On 02/10/2018 11:12, Arnd Bergmann wrote:
> >>> On Sat, Sep 29, 2018 at 5:18 PM Matthias Brugger <matthias.bgg@gmail.com> wrote:
> >>
> >> We rely on the fallback compatible here, as mt2701 and mt7623 are identically in
> >> most of their components. If you require to get the bindings documented before
> >> merging the DT, then I propose to drop the pull request for now.
> >>
> >> Other option would be to get the bindings documented in v4.21. AFAIK up to now
> >> there haven't been sent any patches to update the bindings.
> >
> > Ok, I missed that the mt2701 strings are all documented and used in drivers,
> > so I don't think it's a problem to merge your changes. How about you add
> > another patch to your tree to update the respective bindings? I think that
> > should be fine even for 4.20.
> >
>
> I just send a series of 4 patches which updates the binding documentation. I
> realized that there were more bindings missing, hopefully I caught them all.
>
> The series applies cleanly against linux-next, so I suppose there won't be any
> merge conflicts if you decide to take it through your tree for v4.20.
>
> If you want to send me another pull request, just let me know.

Yes, please do, the patches you sent all look fine. I've pulled
tags/v4.19-next-dts32 into next/dt now, so please base the branch
on top of that.

      arnd
Matthias Brugger Oct. 5, 2018, 8:30 a.m. | #6
On 04/10/2018 16:55, Arnd Bergmann wrote:
> On Wed, Oct 3, 2018 at 11:18 AM Matthias Brugger <matthias.bgg@gmail.com> wrote:
>> On 02/10/2018 13:10, Arnd Bergmann wrote:
>>> On Tue, Oct 2, 2018 at 12:34 PM Matthias Brugger <matthias.bgg@gmail.com> wrote:
>>>> On 02/10/2018 11:12, Arnd Bergmann wrote:
>>>>> On Sat, Sep 29, 2018 at 5:18 PM Matthias Brugger <matthias.bgg@gmail.com> wrote:
>>>>
>>>> We rely on the fallback compatible here, as mt2701 and mt7623 are identically in
>>>> most of their components. If you require to get the bindings documented before
>>>> merging the DT, then I propose to drop the pull request for now.
>>>>
>>>> Other option would be to get the bindings documented in v4.21. AFAIK up to now
>>>> there haven't been sent any patches to update the bindings.
>>>
>>> Ok, I missed that the mt2701 strings are all documented and used in drivers,
>>> so I don't think it's a problem to merge your changes. How about you add
>>> another patch to your tree to update the respective bindings? I think that
>>> should be fine even for 4.20.
>>>
>>
>> I just send a series of 4 patches which updates the binding documentation. I
>> realized that there were more bindings missing, hopefully I caught them all.
>>
>> The series applies cleanly against linux-next, so I suppose there won't be any
>> merge conflicts if you decide to take it through your tree for v4.20.
>>
>> If you want to send me another pull request, just let me know.
> 
> Yes, please do, the patches you sent all look fine. I've pulled
> tags/v4.19-next-dts32 into next/dt now, so please base the branch
> on top of that.
> 

Done! Thanks for taking these patches so late in the cycle.

Regards,
Matthias