From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: Conor Dooley <conor@kernel.org>, Rob Herring <robherring2@gmail.com>
Cc: ksummit@lists.linux.dev, Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [MAINTAINERS SUMMIT] State of dt-bindings and DT source files, and invitation request
Date: Thu, 12 Sep 2024 16:01:20 +0300 [thread overview]
Message-ID: <9d1af9dd-680a-4df8-a6c7-49a6f809d6f2@arinc9.com> (raw)
In-Reply-To: <20240910-specked-rigging-e255283d1f99@spud>
On 11/09/2024 00:53, Conor Dooley wrote:
> On Tue, Sep 10, 2024 at 10:46:03AM -0500, Rob Herring wrote:
>> On Tue, Sep 10, 2024 at 5:53 AM Arınç ÜNAL <arinc.unal@arinc9.com> wrote:
>>>
>>> Hello.
>>>
>>> I maintain the MediaTek DSA subdriver and some devicetree bindings and
>>> source files for MediaTek hardware.
>>>
>>> I am especially interested in the best practices of maintaining dt-bindings
>>> and DT source files.
>>>
>>> There's this false impression with some maintainers that, as the
>>> dt-bindings and the DT source files are being hosted on the Linux
>>> repository, Linux drivers have influence over the design of bindings or
>
>>> fixing DT source files that did not comply with the bindings.
>
> What does "fixing DT source files that did not comply" have to do with
> Linux, I'm afraid I do not understand what your point is there. The
> bindings are the ABI, and fixing incorrect source files would happen
> regardless of how the project is hosted?
That's exactly what I think. I had a maintainer that argued otherwise is my
point. Which is why I want to strengthen the Linux documentation.
>
>>> I'd be very interested to be involved in or kick start the efforts to take
>>> dt-bindings and DT source files out of the Linux repository into its own,
>>> separate repository. I believe, this would be a great step in addressing
>>> all the project-dependent bindings of Linux, U-Boot, OpenWrt, and all other
>>> projects, to have a single, unified repository to describe all the hardware
>>> that exists in the world.
>>
>> This! This is precisely why we don't move things out of the kernel.
>> The kernel is the location that has the most hardware support in the
>> world by far. It is not even close. Really, the only h/w missing are
>> things too small to run Linux. And with all that h/w support, comes
>> the people who understand the various classes of h/w. Those people are
>> not going to come along to a separate project. It would be more work
>> and there aren't any maintainers looking for extra work.
>>
>> We already have a separate repository[1]. U-boot has recently
>> incorporated it and is happily (AFAIK) using it. It happens to be
>> generated from the kernel tree, but what doesn't work for you there?
>> I'm happy to discuss what it needs to work better.
>>
>>> I am already working towards this goal by
>>> improving the dt-bindings and DT source files on the Linux repository
>>> whenever I can.
>>
>> That's great, still plenty of work to do there no matter what
>> repository is hosting it.
>>
>>> I must be quite late to make a topic suggestion but I'd be very happy to be
>>> able to attend to the maintainers summit. I've already registered for the
>>> Linux Plumbers Conference 2024.
>>
>> This is probably not a maintainers summit topic. There's a DT BoF
>> scheduled already that Krzysztof is running and supporting other
>> projects is on the agenda already. I won't be there in person nor will
>> I be awake at the scheduled time.
>
> FWIW, I will be there.
Me too, I'd be very happy to meet you!
Arınç
next prev parent reply other threads:[~2024-09-12 13:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 10:52 Arınç ÜNAL
2024-09-10 15:46 ` Rob Herring
2024-09-10 21:53 ` Conor Dooley
2024-09-12 13:01 ` Arınç ÜNAL [this message]
2024-09-12 15:12 ` Mark Brown
2024-09-12 17:05 ` Conor Dooley
2024-09-13 5:50 ` Arınç ÜNAL
2024-09-12 12:57 ` Arınç ÜNAL
2024-09-13 8:08 ` David Woodhouse
2024-09-13 15:38 ` Arınç ÜNAL
2024-09-13 16:13 ` Conor Dooley
2024-09-14 13:49 ` Arınç ÜNAL
2024-09-19 14:55 ` Rob Herring
2024-09-20 9:53 ` Arınç ÜNAL
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=9d1af9dd-680a-4df8-a6c7-49a6f809d6f2@arinc9.com \
--to=arinc.unal@arinc9.com \
--cc=conor@kernel.org \
--cc=krzk@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=robherring2@gmail.com \
/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