From: Rob Herring <robh@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Alex Soo <yuklin.soo@starfivetech.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Hal Feng <hal.feng@starfivetech.com>,
Ley Foon Tan <leyfoon.tan@starfivetech.com>,
Jianlong Huang <jianlong.huang@starfivetech.com>,
Emil Renner Berthing <kernel@esmil.dk>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Drew Fustini <drew@beagleboard.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Subject: Re: [RFC PATCH v2 1/6] dt-bindings: pinctrl: starfive: Add JH8100 pinctrl
Date: Wed, 28 Feb 2024 11:03:38 -0600 [thread overview]
Message-ID: <20240228170338.GA239206-robh@kernel.org> (raw)
In-Reply-To: <20240224-smudgy-eldercare-d5d8640d9961@spud>
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
next prev parent reply other threads:[~2024-02-28 17:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 6:42 [RFC PATCH v2 0/6] Add Pinctrl driver for Starfive JH8100 SoC Alex Soo
2024-02-20 6:42 ` [RFC PATCH v2 1/6] dt-bindings: pinctrl: starfive: Add JH8100 pinctrl Alex Soo
2024-02-20 8:11 ` Krzysztof Kozlowski
2024-02-20 19:10 ` Conor Dooley
2024-02-21 7:24 ` Krzysztof Kozlowski
2024-02-21 19:39 ` Conor Dooley
2024-02-23 0:24 ` Rob Herring
2024-02-24 8:46 ` Krzysztof Kozlowski
2024-02-24 19:20 ` Conor Dooley
2024-02-28 17:03 ` Rob Herring [this message]
2024-02-28 19:34 ` Conor Dooley
2024-02-20 6:42 ` [RFC PATCH v2 2/6] pinctrl: starfive: jh8100: add main and sys_east driver Alex Soo
2024-02-29 13:03 ` Linus Walleij
2024-05-03 11:12 ` Yuklin Soo
2024-02-20 6:42 ` [RFC PATCH v2 3/6] pinctrl: starfive: jh8100: add pinctrl driver for sys_west domain Alex Soo
2024-02-20 6:42 ` [RFC PATCH v2 4/6] pinctrl: starfive: jh8100: add pinctrl driver for sys_gmac domain Alex Soo
2024-02-20 6:42 ` [RFC PATCH v2 5/6] pinctrl: starfive: jh8100: add pinctrl driver for AON domain Alex Soo
2024-02-20 6:42 ` [RFC PATCH v2 6/6] riscv: dts: starfive: jh8100: add pinctrl device tree nodes Alex Soo
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=20240228170338.GA239206-robh@kernel.org \
--to=robh@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=bartosz.golaszewski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=drew@beagleboard.org \
--cc=hal.feng@starfivetech.com \
--cc=jianlong.huang@starfivetech.com \
--cc=kernel@esmil.dk \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=leyfoon.tan@starfivetech.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=yuklin.soo@starfivetech.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).