linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Paul Mackerras <paulus@samba.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Khuong Dinh <khuong@os.amperecomputing.com>,
	Alexey Brodkin <abrodkin@synopsys.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Andy Gross <agross@kernel.org>,
	linux-snps-arc@lists.infradead.org, devicetree@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, Vladimir Zapolskiy <vz@mleia.com>,
	Rob Herring <robh+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Felipe Balbi <balbi@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org,
	Patrice Chotard <patrice.chotard@st.com>,
	linux-kernel@vger.kernel.org,
	Serge Semin <Sergey.Semin@baikalelectronics.ru>,
	Vineet Gupta <vgupta@synopsys.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH RESEND v9 5/5] arm64: dts: apm: Harmonize DWC USB3 DT nodes name
Date: Sun, 26 Jun 2022 12:49:06 +0200	[thread overview]
Message-ID: <8b9c2b8e-fb65-2b65-1294-47d3b5623f66@linaro.org> (raw)
In-Reply-To: <20220624205902.y2un4lr7d3zkc6jx@mobilestation>

On 24/06/2022 22:59, Serge Semin wrote:
> On Fri, Jun 24, 2022 at 07:17:53PM +0200, Krzysztof Kozlowski wrote:
>> On 24/06/2022 16:16, Serge Semin wrote:
>>> In accordance with the DWC USB3 bindings the corresponding node
>>> name is suppose to comply with the Generic USB HCD DT schema, which
>>> requires the USB nodes to have the name acceptable by the regexp:
>>> "^usb(@.*)?" . Make sure the "snps,dwc3"-compatible nodes are correctly
>>> named despite of the warning comment about possible backward
>>> compatibility issues.
>>
> 
>> Sometimes node name is exposed to user-space which depends on it. How
>> did you check there is no issue here?
> 
> I well remember the Qcom problem caused by one of my patch:
> https://lore.kernel.org/lkml/CALAqxLX_FNvFndEDWtGbFPjSzuAbfqxQE07diBJFZtftwEJX5A@mail.gmail.com/
> 
> The next patch caused the same problem, but hasn't been reverted.
> https://lore.kernel.org/lkml/CALAqxLWGujgR7p8Vb5S_RimRVYxwm5XF-c4NkKgMH-43wEBaWg@mail.gmail.com/
> 
> As before I am more inclined to thinking that the problem was mainly caused
> by the improper node-name utilization. Anyway John later noted that the
> problem was fixed in the user-space. 

Yes, I remember. The node names are not considered ABI, therefore any
reliance on them is not correct.

I wonder however what was the reasoning for this comment in APM DTS.

> That why afterwards you were able
> to provide the commit b77a1c4d6b05 ("arm64: dts: qcom: correct DWC3
> node names and unit addresses").
> 
> Anyway I am not able to track the way the node-name is used on the
> affected platform and can't make sure that the dts would be still
> working well on that devices. But seeing nobody responded/commented on
> this patch for more than a year we can at least try to merge this in
> and see whether it causes any problem should the denoted platform is
> still in use. If it does we can revert the update back and forget
> about it.

The APM is kind of abandoned, so indeed we might never get a reply.

I'll take it.

Best regards,
Krzysztof

  reply	other threads:[~2022-06-26 10:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 14:16 [PATCH RESEND v9 0/5] dt-bindings: usb: Harmonize xHCI/EHCI/OHCI/DWC3 nodes name Serge Semin
2022-06-24 14:16 ` [PATCH RESEND v9 1/5] arc: dts: Harmonize EHCI/OHCI DT " Serge Semin
2022-06-24 22:11   ` Vineet Gupta
2022-06-24 22:28     ` Serge Semin
2022-06-24 14:16 ` [PATCH RESEND v9 2/5] arm: dts: lpc18xx: " Serge Semin
2022-06-24 17:14   ` Krzysztof Kozlowski
2022-06-24 20:41     ` Serge Semin
2022-06-24 17:19   ` (subset) " Krzysztof Kozlowski
2022-06-24 14:16 ` [PATCH RESEND v9 3/5] powerpc: dts: akebono: " Serge Semin
2022-06-24 14:16 ` [PATCH RESEND v9 4/5] arm: dts: stih407-family: Harmonize DWC USB3 " Serge Semin
2022-06-24 17:18   ` Krzysztof Kozlowski
2022-06-24 20:45     ` Serge Semin
2022-06-26 10:42       ` Krzysztof Kozlowski
2022-06-27 21:55         ` Serge Semin
2022-06-26 10:46   ` Krzysztof Kozlowski
2022-06-24 14:16 ` [PATCH RESEND v9 5/5] arm64: dts: apm: " Serge Semin
2022-06-24 17:17   ` Krzysztof Kozlowski
2022-06-24 20:59     ` Serge Semin
2022-06-26 10:49       ` Krzysztof Kozlowski [this message]
2022-06-26 10:50   ` (subset) " 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=8b9c2b8e-fb65-2b65-1294-47d3b5623f66@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=Sergey.Semin@baikalelectronics.ru \
    --cc=abrodkin@synopsys.com \
    --cc=agross@kernel.org \
    --cc=balbi@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fancer.lancer@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=khuong@os.amperecomputing.com \
    --cc=krzk@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=patrice.chotard@st.com \
    --cc=paulus@samba.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=vgupta@synopsys.com \
    --cc=vz@mleia.com \
    /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).