LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alex Elder <firstname.lastname@example.org>
To: Rob Herring <email@example.com>
Cc: Alex Elder <firstname.lastname@example.org>,
Bjorn Andersson <email@example.com>,
"Gross, Andy" <firstname.lastname@example.org>,
David Miller <email@example.com>,
Jakub Kicinski <firstname.lastname@example.org>,
Evan Green <email@example.com>,
Alex Elder <firstname.lastname@example.org>,
Subject: Re: [PATCH net-next 1/3] dt-bindings: net: qcom,ipa: make imem interconnect optional
Date: Tue, 3 Aug 2021 07:24:06 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
On 7/28/21 10:33 AM, Rob Herring wrote:
> On Mon, Jul 26, 2021 at 9:59 AM Alex Elder <firstname.lastname@example.org> wrote:
>> On 7/23/21 3:52 PM, Rob Herring wrote:
>>> On Mon, Jul 19, 2021 at 04:24:54PM -0500, Alex Elder wrote:
>>>> On some newer SoCs, the interconnect between IPA and SoC internal
>>>> memory (imem) is not used. Reflect this in the binding by moving
>>>> the definition of the "imem" interconnect to the end and defining
>>>> minItems to be 2 for both the interconnects and interconnect-names
>>>> Signed-off-by: Alex Elder <email@example.com>
>>>> .../devicetree/bindings/net/qcom,ipa.yaml | 18 ++++++++++--------
>>>> 1 file changed, 10 insertions(+), 8 deletions(-)
>>>> diff --git a/Documentation/devicetree/bindings/net/qcom,ipa.yaml b/Documentation/devicetree/bindings/net/qcom,ipa.yaml
>>>> index ed88ba4b94df5..4853ab7017bd9 100644
>>>> --- a/Documentation/devicetree/bindings/net/qcom,ipa.yaml
>>>> +++ b/Documentation/devicetree/bindings/net/qcom,ipa.yaml
>>>> @@ -87,16 +87,18 @@ properties:
>>>> - const: ipa-setup-ready
>>>> + minItems: 2
>>>> - - description: Interconnect path between IPA and main memory
>>>> - - description: Interconnect path between IPA and internal memory
>>>> - - description: Interconnect path between IPA and the AP subsystem
>>>> + - description: Path leading to system memory
>>>> + - description: Path between the AP and IPA config space
>>>> + - description: Path leading to internal memory
>>>> + minItems: 2
>>>> - const: memory
>>>> - - const: imem
>>>> - const: config
>>>> + - const: imem
>>> What about existing users? This will generate warnings. Doing this for
>>> the 2nd item would avoid the need for .dts updates:
>>> - enum: [ imem, config ]
In other words:
- const: memory
- enum: [ imem, config ]
- const: imem
What do I do with the "interconnects" descriptions in that case?
How do I make the "interconnect-names" specified this way align
with the described interconnect values? Is that necessary?
>> If I understand correctly, the effect of this would be that
>> the second item can either be "imem" or "config", and the third
>> (if present) could only be "imem"?
> Yes for the 2nd, but the 3rd item could only be 'config'.
Sorry, yes, that's what I meant. I might have misread the
>> And you're saying that otherwise, existing users (the only
>> one it applies to at the moment is "sdm845.dtsi") would
>> produce warnings, because the interconnects are listed
>> in an order different from what the binding specifies.
>> Is that correct?
>> If so, what you propose suggests "imem" could be listed twice.
>> It doesn't make sense, and maybe it's precluded in other ways
>> so that's OK.
> Good observation. There are generic checks that the strings are unique.
I think I don't like that quite as much, because that
"no duplicates" rule is implied. It also avoids any
confusion in the "respectively" relationship between
interconnects and interconnect-names.
I understand what you're suggesting though, and I would
be happy to update the binding in the way you suggest.
I'd like to hear what you say about my questions above
before doing so.
>> But I'd be happy to update "sdm845.dtsi" to
>> address your concern. (Maybe that's something you would rather
> Better to not change DT if you don't have to. You're probably okay if
> all clients (consumers of the dtb) used names and didn't care about
In the IPA driver, wherever names are specified for things in DT,
names (only) are used to look them up. So I'm "probably okay."
> the order. And I have no idea if all users of SDM845 are okay with a
> DTB change being required. That's up to QCom maintainers. I only care
> that ABI breakages are documented as such.
>> Also, I need to make a separate update to "sm8350.dtsi" because
>> that was defined before I understood what I do now about the
>> interconnects. It uses the wrong names, and should combine
>> its first two interconnects into just one.
> If the interconnects was ignored in that case, then the change doesn't matter.
That platform is not yet fully supported by the IPA driver, thus
there is (so far) no instance where it is used. Resolving this
is part of enabling support for that.
next prev parent reply other threads:[~2021-08-03 12:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 21:24 [PATCH net-next 0/3] arm64: dts: qcom: DTS updates Alex Elder
2021-07-19 21:24 ` [PATCH net-next 1/3] dt-bindings: net: qcom,ipa: make imem interconnect optional Alex Elder
2021-07-23 20:52 ` Rob Herring
2021-07-26 15:59 ` Alex Elder
2021-07-28 15:33 ` Rob Herring
2021-08-03 12:24 ` Alex Elder [this message]
2021-08-03 18:05 ` Rob Herring
2021-07-19 21:24 ` [PATCH net-next 2/3] arm64: dts: qcom: sc7280: add IPA information Alex Elder
2021-07-19 21:24 ` [PATCH net-next 3/3] arm64: dts: qcom: sc7180: define ipa_fw_mem node Alex Elder
2021-07-20 14:20 ` [PATCH net-next 0/3] arm64: dts: qcom: DTS updates patchwork-bot+netdevbpf
2021-07-20 15:59 ` Bjorn Andersson
2021-07-26 15:44 ` Alex Elder
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: [PATCH net-next 1/3] dt-bindings: net: qcom,ipa: make imem interconnect optional' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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).