From: Krzysztof Kozlowski <krzk@kernel.org>
To: mr.nuke.me@gmail.com,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: ipq9574: Use 'usb-phy' for node names
Date: Wed, 10 Dec 2025 07:03:46 +0100 [thread overview]
Message-ID: <ca3934c2-532f-4744-bf7c-2480048c7fef@kernel.org> (raw)
In-Reply-To: <b167f406-c5e6-437d-bb34-57f253258f54@gmail.com>
On 09/12/2025 22:59, mr.nuke.me@gmail.com wrote:
>
>
> On 12/9/25 3:48 PM, Krzysztof Kozlowski wrote:
>> On 09/12/2025 17:26, mr.nuke.me@gmail.com wrote:
>>> On 12/9/25 10:17 AM, Dmitry Baryshkov wrote:
>>>> On Tue, Dec 09, 2025 at 10:07:54AM -0600, Alexandru Gagniuc wrote:
>>>>> The devicetree spec allows node names of "usb-phy". So be more
>>>>> specific for the USB PHYs, and name the nodes "usb-phy" instead of
>>>>> just "phy".
>>>>
>>>> Why? "phy" is more generic.
>>>
>>> Hi Dmitry,
>>>
>>> The goal is to be more specific. I find usb-phy, ethernet-phy and others
>>
>> We do not have such goal. Where did you find that goal documented?
>
> If the goal isn't to be specific, clear, and readable, what is it? Why not be generic, and call subnodes node@, or dev@ ?
Did you read the spec you referred to? What sort of class of devices
represents "node"?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-10 6:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 16:07 [PATCH] arm64: dts: qcom: ipq9574: Use 'usb-phy' for node names Alexandru Gagniuc
2025-12-09 16:17 ` Dmitry Baryshkov
2025-12-09 16:26 ` mr.nuke.me
2025-12-09 21:48 ` Krzysztof Kozlowski
2025-12-09 21:59 ` mr.nuke.me
2025-12-10 6:03 ` Krzysztof Kozlowski [this message]
2025-12-10 16:44 ` mr.nuke.me
2025-12-09 21:47 ` Krzysztof Kozlowski
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=ca3934c2-532f-4744-bf7c-2480048c7fef@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mr.nuke.me@gmail.com \
--cc=robh@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).