mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Vinod Koul <vkoul@kernel.org>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] dt-bindings: phy: uniphier-ahci: Fix missing reset-names
Date: Wed, 30 Mar 2022 08:48:32 +0900	[thread overview]
Message-ID: <1dbe4ef7-25bc-2f8a-6ce5-3a39453a8b1c@socionext.com> (raw)
In-Reply-To: <1ff5682f-3f59-8635-631f-d648e604044f@linaro.org>

Hi Krzysztof,

On 2022/03/29 20:45, Krzysztof Kozlowski wrote:
> On 29/03/2022 12:55, Kunihiko Hayashi wrote:
>> Hi Krzysztof,
>>
>> Thank you for reviewing.
>>
>> On 2022/03/29 3:58, Krzysztof Kozlowski wrote:
>>> On 28/03/2022 04:05, Kunihiko Hayashi wrote:
>>>> Add missing "phy" reset-names to fix the following warning:
>>>>
>>>>     uniphier-pro4-ace.dtb: ahci-phy@10: resets: [[26, 28], [26, 12], [26,
>>>> 30], [36, 0], [36, 1], [36, 2]] is too long
>>>>         From schema:
>>>> Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml
>>>>     uniphier-pro4-ace.dtb: ahci-phy@10: reset-names: 'oneOf' conditional
>>>> failed, one must be fixed:
>>>>         ['link', 'gio', 'phy', 'pm', 'tx', 'rx'] is too long
>>>>         From schema:
>>>> Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml
>>>
>>> There is no ahci-phy in current sources...
>>
>> Oops, I'm going to add ahci controller to the existing devicetree,
>> but not yet. I shouldn't write the future warning in the commit message,
>> so I'll fix it.
>>
>>>>
>>>> Fixes: 34f92b67621f ("dt-bindings: phy: uniphier-ahci: Add bindings for
>>>> Pro4 SoC")
>>>> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
>>>> ---
>>>>    .../devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml   | 3 ++-
>>>>    1 file changed, 2 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git
>>>> a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml
>>>> b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml
>>>> index 3b400a85b44a..14f7579e7daa 100644
>>>> ---
>>>> a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml
>>>> +++
>>>> b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml
>>>> @@ -43,13 +43,14 @@ properties:
>>>>
>>>>      resets:
>>>>        minItems: 2
>>>> -    maxItems: 5
>>>> +    maxItems: 6
>>>>
>>>>      reset-names:
>>>>        oneOf:
>>>
>>> As a separate commit, this oneOf should be converted into allOf:if:then:
>>> cases which will enforce the resets per compatible.
>>>
>>> Can you do that as well?
>>
>> Ok, I've found some examples using "allOf:if:them:" cases,
>> so I'll try to convert it with another commit.
>>
> 
> For an example, you can take a look at (linux-next):
> Documentation/devicetree/bindings/clock/samsung,exynos7885-clock.yaml
> 
> and clocks/clock-names properties.

Thanks for your suggestion.
I understand how to write it and am trying to convert the *-names to this case.

I also found such cases and some mistakes in the other phys (usb3 and pcie),
so I'll fix and resend them next.

Thank you,

---
Best Regards
Kunihiko Hayashi

      reply	other threads:[~2022-03-29 23:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28  2:05 [PATCH 0/3] dt-bindings: phy: Fix uniphier descriptions Kunihiko Hayashi
2022-03-28  2:05 ` [PATCH 1/3] dt-bindings: phy: uniphier-usb2: Add vbus-supply Kunihiko Hayashi
2022-03-28 18:53   ` Krzysztof Kozlowski
2022-03-28  2:05 ` [PATCH 2/3] dt-bindings: phy: uniphier-usb3ss: Treat vbus-supply as optional Kunihiko Hayashi
2022-03-28 18:54   ` Krzysztof Kozlowski
2022-03-28  2:05 ` [PATCH 3/3] dt-bindings: phy: uniphier-ahci: Fix missing reset-names Kunihiko Hayashi
2022-03-28 18:58   ` Krzysztof Kozlowski
2022-03-29 10:55     ` Kunihiko Hayashi
2022-03-29 11:45       ` Krzysztof Kozlowski
2022-03-29 23:48         ` Kunihiko Hayashi [this message]

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=1dbe4ef7-25bc-2f8a-6ce5-3a39453a8b1c@socionext.com \
    --to=hayashi.kunihiko@socionext.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=mhiramat@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=vkoul@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

all inboxes | Powered by JetHome®