From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: dts updates for arm 32 bits for v4.20
Date: Wed, 3 Oct 2018 11:18:23 +0200 [thread overview]
Message-ID: <a2295a12-db8b-978f-69ad-b0078d763135@gmail.com> (raw)
In-Reply-To: <CAK8P3a0dih9hFib05L2C31ONnraxN67H4wJAzQWD9gMg2Ek1Eg@mail.gmail.com>
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
next prev parent reply other threads:[~2018-10-03 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 15:18 [GIT PULL] ARM: dts updates for arm 32 bits for v4.20 Matthias Brugger
2018-10-02 9:12 ` Arnd Bergmann
2018-10-02 10:34 ` Matthias Brugger
2018-10-02 11:10 ` Arnd Bergmann
2018-10-03 9:18 ` Matthias Brugger [this message]
2018-10-04 14:55 ` Arnd Bergmann
2018-10-05 8:30 ` Matthias Brugger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a2295a12-db8b-978f-69ad-b0078d763135@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).