[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4349c714-a49b-4814-81d1-b0bb6120f34b@linaro.org>
Date: Sat, 30 Sep 2023 17:15:31 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Piyush Mehta <piyush.mehta@....com>, gregkh@...uxfoundation.org,
michal.simek@....com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
peter.chen@...nel.org, linus.walleij@...aro.org,
paul@...pouillou.net, arnd@...db.de
Cc: linux-usb@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, git@....com
Subject: Re: [RFC PATCH 1/3] dt-binding: usb: ulpi-phy: add ulpi-phy binding
On 29/09/2023 08:48, Piyush Mehta wrote:
> Create an ulpi-phy binding to read and write PHY registers with explicit
> control of the address and data using the usb.VIEWPORT register.
>
> Signed-off-by: Piyush Mehta <piyush.mehta@....com>
Subject: dt-bindings, not dt-binding.
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching.
> ---
> This binding patch was created to support generic platforms. This binding
> will be modified in accordance with patch [3/3] procedures.
I don't understand this. How binding can be updated by further
procedures? Your patch 3 is a driver, so how driver can modify a binding?
Best regards,
Krzysztof
Powered by blists - more mailing lists