[RFC PATCH v2 1/6] dt-bindings: pinctrl: starfive: Add JH8100 pinctrl
Rob Herring
robh at kernel.org
Wed Feb 28 09:03:38 PST 2024
On Sat, Feb 24, 2024 at 07:20:30PM +0000, Conor Dooley wrote:
> On Sat, Feb 24, 2024 at 09:46:53AM +0100, Krzysztof Kozlowski wrote:
> > > I would like a solution though. The only idea I have is passing
> > > SystemReady cert, but that's an Arm thing.
>
> I don't know jack about SystemReady
AIUI, Risc-V is working on something similar...
The primary intent of it is to enable installing off-the-shelf OSs.
> - I had it in my head that it was a
> system level certification. I am wondering how you think that
> SystemReady certification would apply to a whole binding (I can see it
> being a per-compatible thing, but that would be a mess I am sure).
There's a lot of pieces, but I'll stick to the DT aspects (which is
SystemReady IR band). Certification applies to a specific firmware build
(which includes the DTB) on a specific board. The testing requirements
at the moment (for 2.x) are every binding (compatible) must have a
schema, but warnings are allowed.
So a "stable" tag would apply to a DTS as a whole. That of course
implies that everything within the DTS is stable too.
One wrinkle is that SR has no direct requirement that the DTB come from
anything upstream. Indirectly, the schemas must exist and be upstream
(or acked on the lists) and various distro kernels have to actually
boot. For that reason, if we had some tag, it would have to be
distinct from SR.
Rob
More information about the linux-riscv
mailing list