<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<br id="lineBreakAtBeginningOfMessage">
<div><br>
<blockquote type="cite">
<div>Le 7 déc. 2023 à 21:31, Conor Dooley <conor@kernel.org> a écrit :</div>
<br class="Apple-interchange-newline">
<div><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">What
on earth has happened here with quoting? Please fix your mail</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">client
man, this mail is a mess to read.</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
</div>
</blockquote>
Conor: Hopefully I have now fixed MacOS Mail configuration… </div>
<div>For all: please accept my apologies on past inconveniences.</div>
<div><br>
<blockquote type="cite">
<div><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">On
Thu, Dec 07, 2023 at 08:24:01PM +0000, ff wrote:</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<br>
<br>
Le 7 déc. 2023 à 19:51, Rob Herring <robh+dt@kernel.org> a écrit :<br>
<br>
On Thu, Dec 7, 2023 at 2:08 AM ff <ff@shokubai.tech> wrote:<br>
<br>
<br>
<br>
Le 6 déc. 2023 à 21:42, Rob Herring <robh+dt@kernel.org> a écrit :<br>
<br>
On Tue, Dec 5, 2023 at 11:05 PM Sumit Garg <sumit.garg@linaro.org> wrote:<br>
<br>
On Tue, 5 Dec 2023 at 15:39, Krzysztof Kozlowski<br>
<krzysztof.kozlowski@linaro.org> wrote:<br>
<br>
On 05/12/2023 10:45, Sumit Garg wrote:<br>
+ U-boot custodians list<br>
<br>
On Tue, 5 Dec 2023 at 12:58, Krzysztof Kozlowski<br>
<krzysztof.kozlowski@linaro.org> wrote:<br>
<br>
On 05/12/2023 08:13, Sumit Garg wrote:<br>
@DT bindings maintainers,<br>
<br>
Given the ease of maintenance of DT bindings within Linux kernel<br>
source tree, I don't have a specific objection there. But can we ease<br>
DTS testing for firmware/bootloader projects by providing a versioned<br>
release package for DT bindings? Or if someone else has a better idea<br>
here please feel free to chime in.<br>
<br>
This doesn't work for you?:<br>
<br>
https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebasing.git/<br>
<br>
Thanks, this is certainly a good step which I wasn't aware of. Further<br>
simplification can be done to decouple devicetree source files from DT<br>
bindings.<br>
<br>
Why?<br>
<br>
I suppose you are already aware that Linux DTS files are a subset of<br>
what could be supported by devicetree schemas. There can be<br>
firmware/bootloader specific properties (one example being [1]) which<br>
Linux kernel can simply ignore. Will you be willing to add all of<br>
those DT properties to Linux DTS files and maintain them?<br>
<br>
We already added them and we already maintain them. DTS describes the<br>
hardware, not the OS-subset of the hardware.<br>
<br>
Let look at some numbers if your statement is justified or not for the<br>
example I gave:<br>
<br>
u-boot$ git grep -nr bootph-* arch/arm* | wc -l<br>
4079<br>
<br>
linux$ git grep -nr bootph-* arch/arm* | wc -l<br>
267<br>
<br>
I have no control over whether anyone has submitted the other 3812 instances.<br>
<br>
It looks like there is always going to be a catch up game regarding DT<br>
properties which either Linux kernel or u-boot or any other<br>
firmware/bootloader project don't care about.<br>
<br>
As long as dts files in u-boot are manually sync'ed, yes. That is the<br>
problem and it doesn't matter if we have a standalone repository or<br>
not.<br>
<br>
If you want to move in that direction, start automating what u-boot<br>
imports. You need to do that for bindings if you want to run<br>
validation, so why not dts files too?<br>
<br>
However, DT bindings are something which should be common, the<br>
hardware description of a device should be universal. IMO, splitting<br>
<br>
Both DT bindings and DTS should be common. I don't see the difference.<br>
<br>
If we really care about DTS to be common then the contribution model<br>
has to change where there is a single repo hosting DT bindings and<br>
DTS. All other projects whether it is Linux kernel or u-boot or any<br>
other OS/firmware/bootloader are just consuming DTS files from that<br>
single repo.<br>
<br>
Really, only the kernel and u-boot matter. No, I don't mean I don't<br>
care about other projects, but those are the 2 with the widest h/w<br>
support by far and which have a major effort to sync copies of dts<br>
files in both projects. The rest are just noise in terms of this<br>
problem.<br>
<br>
I suppose this is something that Linux DT maintainers<br>
have objected to in the past for ease of maintenance. I am not sure if<br>
you folks are willing to change that stance.<br>
<br>
The issue is no one steps up to help maintain such a repository while<br>
there is lots of review and maintainer work on what goes into the<br>
kernel tree. I'm happy to direct my binding review attention to<br>
wherever the majority of the bindings go. But the work on the DTS side<br>
is mostly SoC tree maintainers and sub-maintainers.<br>
<br>
Assume for a minute we have this standalone repo. What happens next?<br>
We start with an empty repo and then merge and move platforms 1 by 1?<br>
<br>
What about leveraging SystemReady-IR compliant board maintainers and start with a core of motivated people ?<br>
<br>
I think there are 2 ATM. Synquacer and i.MX8 variants.<br>
<br>
Based on https://www.arm.com/architecture/system-architectures/systemready-certification-program/ir<br>
roughly 30 boards.<br>
<br>
Synquacer only<br>
has a DT in u-boot, so not really anything to do there.<br>
I'm pretty<br>
sure the certified DTBs for i.MX8 don't match what's in u-boot or the<br>
kernel tree. Hopefully, it's just a subset, but still, there's a gap.<br>
I don't know that there is motivation there either.<br>
Note that SystemReady currently only requires every node with<br>
'compatible' have a schema. It does not yet require no schema<br>
warnings. If we went with a 1 by 1 approach, I would push that<br>
platforms have to be free of warnings.<br>
<br>
How many years will that take?<br>
<br>
Should all platforms following that organization be a goal?<br>
<br>
You mean should all platforms be moved? Absolutely. I don't think we<br>
want to solve the problem of having DTS files in 2 places by creating<br>
a 3rd place.<br>
</blockquote>
<br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">I
think this bit here is the only thing you actually wrote:</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
Actually, if we limit he DTS in the third place for SystemReady-IR,<br>
there should be no DTB in the Linux distribution.<br>
It would be the equivalent as ACPI boards . So is it still an issue ?<br>
A reference to the the third repo may be hinted in a text file.<br>
</blockquote>
<br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">SystemReady
is only for one architecture, why would using it as the</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">centralised
point for devicetree files make sense?</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
</div>
</blockquote>
SystemReady is an Arm certification but built on EBBR which is </div>
<div>the important part and also adopted by RISC-V.</div>
<div>So when I said SystemReady, one should read EBBR.</div>
<div>EBBR is promoting a DT life cycle that is in line with</div>
<div>having an out of OS/Firmware repos definitions.</div>
<div>
<blockquote type="cite">
<div>
<blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<br>
I don't really think 1 by 1 is the right approach. I was just<br>
enumerating how this could work. It's not that useful to say we need a<br>
standalone repo without working thru the logistics of how exactly that<br>
will work.<br>
<br>
Rob</blockquote>
</div>
</blockquote>
</div>
<br>
</body>
</html>