Hi Geert,
Thanks for your feedback.
On 2025-03-17 20:21:14 +0100, Geert Uytterhoeven wrote:
> Hi Niklas,
>
> On Mon, 17 Mar 2025 at 16:37, Niklas Söderlund
> <niklas.soderlund+renesas@xxxxxxxxxxxx> wrote:
> > On 2025-03-17 15:57:31 +0100, Krzysztof Kozlowski wrote:
> > > On 17/03/2025 12:50, Niklas Söderlund wrote:
> > > > On 2025-03-17 12:33:07 +0100, Krzysztof Kozlowski wrote:
> > > >> On Sat, Mar 15, 2025 at 04:27:02PM +0100, Niklas Söderlund wrote:
> > > >>> ports:
> > > >>> $ref: /schemas/graph.yaml#/properties/ports
> > > >>> @@ -103,10 +138,14 @@ properties:
> > > >>> required:
> > > >>> - compatible
> > > >>> - reg
> > > >>> + - reg-names
> > > >>> - interrupts
> > > >>> + - interrupt-names
> > > >>> - clocks
> > > >>> + - clock-names
> > > >>> - power-domains
> > > >>> - resets
> > > >>> + - reset-names
> > > >>
> > > >> Another point, this will spawn bunch of warnings for no real reason.
> > > >> Just drop all the xxx-names from properties and from here.
> > > >
> > > > I'm sorry maybe I'm missing something, but if I drop them from
> > > > properties how can I add checks to makesure the names are either "cs" or
> > >
> > > Why do you need to check for the names? There will be no names, so
> > > nothing to check for.
> >
> > Ahh I see. But I would like to have names if possible.
> >
> > The driver is backward compatible with the old bindings, and going
> > forward we have better bindings with names. All users are updated in the
> > next commits in this series so the warnings will go way rather quickly.
>
> Note that the driver does not _have_ to obtain the "cs" clock by name,
> as it will always be the first clock anyway ("make dtbs_check" will
> sort-of enforce that). So you can simplify the code by obtaining
> the first clock without specifying a name, and the second (optional)
> clock with a name.
I understand that, and for this fix this would be acceptable. I'm just
trying to think a head, something I should have done when first writing
these bindings...
I'm fearing a scenario where we will need to add a 3rd reg region or
clock. I don't think we will need that for the compatible values we have
here, but then I never though we get the documentation that now allows
us to describe the second region...
If you and Krzysztof are happy without names I can move forward with
that too, I'm just trying to learn from my mistakes ;-) I will give it a
few days and then head down this road without names.
--
Kind Regards,
Niklas Söderlund
