From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Alex Elder <elder@kernel.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 1/3] dt-bindings: sram: qcom,imem: Allow modem-tables subnode
Date: Wed, 18 Feb 2026 14:21:57 +0100 [thread overview]
Message-ID: <9bfb4ef0-49a1-4127-aad4-2ba1b9dd8e95@kernel.org> (raw)
In-Reply-To: <193d236b-864b-45bd-b0a9-6efbdccf6db9@oss.qualcomm.com>
On 18/02/2026 13:26, Konrad Dybcio wrote:
>
>
> On 18-Feb-26 12:56, Krzysztof Kozlowski wrote:
>> On 18/02/2026 12:05, Konrad Dybcio wrote:
>>> On 2/17/26 9:25 PM, Krzysztof Kozlowski wrote:
>>>> On Tue, Feb 17, 2026 at 02:30:31PM +0100, Konrad Dybcio wrote:
>>>>> From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>>>>>
>>>>> The IP Accelerator hardware/firmware owns a sizeable region within the
>>>>> IMEM, named 'modem-tables', containing various packet processing
>>>>> configuration data.
>>>>>
>>>>> It's not actually accessed by the OS, although we have to IOMMU-map it
>>>>> with the IPA device, so that presumably the firmware can act upon it.
>>>>>
>>>>> Allow it as a subnode of IMEM.
>>>>
>>>> You do not have compatible, so rely on the node name as ABI, which is
>>>> fine in general but... I do not see usage of it in the driver. Why do
>>>> you need to define modem-tables child then?
>>>
>>> I don't really *need* the node name to be an ABI. However, the current
>>> binding for IMEM only allows a named "pil-reloc@.." subnode (which is
>>> consumed via of_find_compatible_node() in the remoteproc subsystem) so I
>>> figured the intention was to keep the list of allowed subnodes strictly
>>> moderated
>>>
>>> If you'd prefer a blanket pattern declaration with say '^[a-z]@[0-9a-z]+$'
>>> with just a reg requirement inside, I'm fine with that too
>>
>> No, the problem is that you do not use the ABI here at all. Neither
>> would you use the blanket pattern, so my question stays: why adding ABI
>> which is not used?
>
> The subnode I'm trying to introduce is going to be consumed (via a
> phandle reference) from the IPA node, as done by the remaining 2
> patches in this series.
And that's the problem - I do not see consuming child. I see
of_parse_phandle to sram node, not the child.
>
> I would much prefer not to touch this binding file, but there's an
> additionalProperties: false and just adding it as-is results in a:
>
> arch/arm64/boot/dts/qcom/sc7280-idp.dtb: sram@146a5000: 'modem-tables@1234' does not match any of the regexes: '^pil-reloc@[0-9a-f]+$', 'pinctrl-[0-9]+'
> from schema $id: http://devicetree.org/schemas/sram/qcom,imem.yaml#
>
> Konrad
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-18 13:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 13:30 [net-next PATCH v3 0/3] Grab IPA IMEM slice through DT Konrad Dybcio
2026-02-17 13:30 ` [PATCH net-next v3 1/3] dt-bindings: sram: qcom,imem: Allow modem-tables subnode Konrad Dybcio
2026-02-17 18:01 ` Alex Elder
2026-02-17 20:25 ` Krzysztof Kozlowski
2026-02-18 11:05 ` Konrad Dybcio
2026-02-18 11:56 ` Krzysztof Kozlowski
2026-02-18 12:26 ` Konrad Dybcio
2026-02-18 13:21 ` Krzysztof Kozlowski [this message]
2026-02-18 13:32 ` Konrad Dybcio
2026-02-19 11:01 ` Krzysztof Kozlowski
2026-02-19 11:01 ` Krzysztof Kozlowski
2026-02-17 13:30 ` [PATCH net-next v3 2/3] dt-bindings: net: qcom,ipa: Add sram property for describing IMEM slice Konrad Dybcio
2026-02-17 13:30 ` [PATCH net-next v3 3/3] net: ipa: Grab IMEM slice base/size from DTS Konrad Dybcio
2026-02-17 18:01 ` Alex Elder
2026-02-18 10:39 ` [net-next,v3,3/3] " Simon Horman
2026-02-18 11:21 ` Konrad Dybcio
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=9bfb4ef0-49a1-4127-aad4-2ba1b9dd8e95@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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