From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michal Simek <michal.simek@amd.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, Andrew Davis <afd@ti.com>,
Arnd Bergmann <arnd@arndb.de>,
Bjorn Andersson <andersson@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Heiko Stuebner <heiko@sntech.de>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Nishanth Menon <nm@ti.com>, Olof Johansson <olof@lixom.net>,
linux-rockchip@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
linux-amlogic@lists.infradead.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2] docs: dt-bindings: add DTS Coding Style document
Date: Tue, 21 Nov 2023 09:37:21 +0100 [thread overview]
Message-ID: <ec901578-95b6-4fcc-a8dd-e927b7f77ece@linaro.org> (raw)
In-Reply-To: <CAMuHMdV_gqmf2=cXmZmYgE3aLxvPBr1DVp0cz0C+YrfBVG-8mg@mail.gmail.com>
On 21/11/2023 09:08, Geert Uytterhoeven wrote:
>>>>> I guess there are (many) other examples...
>>>>
>>>> OK, I never had such in my hands. Anyway, the SoM which can run
>>>> standalone has a meaning of a board, so how exactly you want to
>>>> rephrase the paragraph?
>>>
>>> What about?
>>>
>>> 2. If applicable: DTSI with common or re-usable parts of the hardware (e.g.
>>> entire System-on-Module). DTS if runs standalone.
>>
>> OK, but then it's duplicating the option 3. It also suggests that SoM
>> should be a DTS, which is not what we want for such case. Such SoMs must
>> have DTSI+DTS.
>
> So you want us to have a one-line <SoM>.dts, which just includes <SoM>.dtsi?
> IMHO that adds more files for no much gain.
Yes, if this is a real SoM, then yes. There is much gain - it clearly
represents the hardware like we in general expect. It allows re-usage by
in- and out-tree users, while documenting this possibility.
We structure DTS according to main components of the hardware, which
serves as self-documenting, re-usable and easy to grasp solution.
> Users of a SoM can easily include <SoM>.dts.
Which is confusing during review and not a welcomed pattern.
> 'git grep "#include .*dts\>"' tells you we have plenty of users of that scheme.
Yeah, you can put C functions inside header (included only once). You
can include C file in other C file. But just because you can do it, it
does not mean you should do it. It's not the way we want to make code
organized.
Best regards,
Krzysztof
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-11-21 8:37 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 8:40 [PATCH v2] docs: dt-bindings: add DTS Coding Style document Krzysztof Kozlowski
2023-11-20 9:04 ` Neil Armstrong
2023-11-20 9:38 ` Heiko Stübner
2023-11-20 11:43 ` AngeloGioacchino Del Regno
2023-11-20 14:57 ` Krzysztof Kozlowski
2023-11-21 10:25 ` AngeloGioacchino Del Regno
2023-11-20 14:01 ` Michal Simek
2023-11-20 14:53 ` Krzysztof Kozlowski
2023-11-20 19:18 ` Geert Uytterhoeven
2023-11-20 19:31 ` Krzysztof Kozlowski
2023-11-21 7:33 ` Michal Simek
2023-11-21 7:47 ` Krzysztof Kozlowski
2023-11-21 8:08 ` Geert Uytterhoeven
2023-11-21 8:37 ` Krzysztof Kozlowski [this message]
2023-11-21 10:13 ` Dmitry Baryshkov
2023-11-21 10:28 ` Krzysztof Kozlowski
2023-11-21 11:53 ` Michal Simek
2023-11-21 11:55 ` Michal Simek
2023-11-21 12:36 ` Krzysztof Kozlowski
2023-11-21 16:04 ` Geert Uytterhoeven
2023-11-22 8:01 ` Krzysztof Kozlowski
2023-11-22 8:15 ` Dragan Simic
2023-11-20 20:15 ` Andrew Lunn
2023-11-21 7:36 ` Michal Simek
2023-11-21 7:47 ` Krzysztof Kozlowski
2023-11-22 8:18 ` Krzysztof Kozlowski
2023-11-21 13:50 ` Rafał Miłecki
2023-11-22 8:05 ` Krzysztof Kozlowski
2023-11-22 8:09 ` Chen-Yu Tsai
2023-11-22 8:21 ` Krzysztof Kozlowski
2023-11-22 8:28 ` Geert Uytterhoeven
2023-11-22 8:29 ` Dragan Simic
2023-11-22 8:49 ` Michal Simek
2023-11-22 8:53 ` Geert Uytterhoeven
2023-11-22 8:57 ` Michal Simek
2023-11-22 9:09 ` Krzysztof Kozlowski
2023-11-22 14:34 ` Rob Herring
2023-11-22 14:42 ` Dragan Simic
2023-11-22 8:59 ` Dragan Simic
2023-11-22 14:55 ` Rob Herring
2023-11-25 18:44 ` Krzysztof Kozlowski
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=ec901578-95b6-4fcc-a8dd-e927b7f77ece@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=afd@ti.com \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=heiko@sntech.de \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=michal.simek@amd.com \
--cc=neil.armstrong@linaro.org \
--cc=nm@ti.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.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).