From: Hui-Ping Chen <hpchen0nvt@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
vkoul@kernel.org, kishon@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: phy: nuvoton,ma35-usb2-phy: add new bindings
Date: Tue, 30 Jul 2024 16:03:35 +0800 [thread overview]
Message-ID: <85a4b5c2-89f1-40d1-baec-b17479f5cae2@gmail.com> (raw)
In-Reply-To: <c4c2b30a-8ff9-4fc4-a1ed-adcd366d15a7@kernel.org>
Dear Krzysztof,
Thank you for your reply.
On 2024/7/29 下午 03:29, Krzysztof Kozlowski wrote:
> On 29/07/2024 08:15, hpchen0 wrote:
>> Add dt-bindings for USB2 PHY found on the Nuvoton MA35 SoC.
>>
>> Signed-off-by: hpchen0 <hpchen0nvt@gmail.com>
> Please use proper name.
Okay, I will make the correction and use the correct name.
>> ---
>> .../bindings/phy/nuvoton,ma35-usb2-phy.yaml | 51 +++++++++++++++++++
>> 1 file changed, 51 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/phy/nuvoton,ma35-usb2-phy.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/phy/nuvoton,ma35-usb2-phy.yaml b/Documentation/devicetree/bindings/phy/nuvoton,ma35-usb2-phy.yaml
>> new file mode 100644
>> index 000000000000..415ea2c45975
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/phy/nuvoton,ma35-usb2-phy.yaml
>> @@ -0,0 +1,51 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/phy/nuvoton,ma35-usb2-phy.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Nuvoton MA35 USB2 phy
>> +
>> +maintainers:
>> + - hpchen0 <hpchen0nvt@gmail.com>
> Same here
Okay, I will make the correction and use the correct name.
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - nuvoton,ma35-usb2-phy
> All other devices have name ma35d1. Is this a different SoC?
The SoC is the same as ma35d1. I will modify ma35 to ma35d1.
Originally, I intended to create a series of shared drivers.
>> +
>> + "#phy-cells":
>> + const: 0
>> +
>> + clocks:
>> + maxItems: 1
>> + description: USB PHY clock
> Drop description, it's obvious.
Okay, I will remove the description.
>> +
>> + clock-names:
>> + const: usbd_gate
> Drop clock-names, you do not bring any new information.
Okay, I will remove the clock-names.
>> +
>> + nuvoton,sys:
>> + $ref: /schemas/types.yaml#/definitions/phandle
>> + description:
>> + phandle of the system-management node.
> Describe what is it for.
Because this driver has some status bits located in the sys, it is
necessary to reference the sys link.
>> +
>> +required:
>> + - compatible
>> + - clocks
>> + - nuvoton,sys
>> + - "#phy-cells"
> Keep the same order as in properties.
Okay, I will correct this issue.
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> Where do you use it?
This is not used and will be removed. Thanks for the reminder.
>> + #include <dt-bindings/clock/nuvoton,ma35d1-clk.h>
>> +
>> + usb_phy: usb-phy {
>> + compatible = "nuvoton,ma35-usb2-phy";
>> + clocks = <&clk USBD_GATE>;
>> + clock-names = "usbd_gate";
>> + nuvoton,sys = <&sys>;
>> + #phy-cells = <0>;
>> + };
> Best regards,
> Krzysztof
Best regards,
Hui-Ping Chen
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2024-07-30 8:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 6:15 [PATCH 0/2] Add support for nuvoton ma35 usb2 phy hpchen0
2024-07-29 6:15 ` [PATCH 1/2] dt-bindings: phy: nuvoton,ma35-usb2-phy: add new bindings hpchen0
2024-07-29 7:29 ` Krzysztof Kozlowski
2024-07-30 7:44 ` Hui-Ping Chen
2024-07-30 8:10 ` Krzysztof Kozlowski
2024-07-30 8:25 ` Hui-Ping Chen
2024-07-30 8:03 ` Hui-Ping Chen [this message]
2024-07-29 6:15 ` [PATCH 2/2] phy: nuvoton: add new driver for the Nuvoton MA35 SoC USB 2.0 PHY hpchen0
2024-07-29 7:32 ` Krzysztof Kozlowski
2024-07-30 8:05 ` Hui-Ping Chen
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=85a4b5c2-89f1-40d1-baec-b17479f5cae2@gmail.com \
--to=hpchen0nvt@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).