| Message ID | 20250523-topic-ipa_imem-v1-1-b5d536291c7f@oss.qualcomm.com |
|---|---|
| State | New |
| Headers | show |
| Series | Grab IPA IMEM slice through DT | expand |
On 5/22/25 6:08 PM, Konrad Dybcio wrote: > From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> > > The IP Accelerator hardware/firmware owns a sizeable region within the > IMEM, ominously named 'modem-tables', presumably having to do with some > internal IPA-modem specifics. > > 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. > > Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> So this will just show up as a subnode of an sram@... node, the way "qcom,pil-reloc-info" does. This is great. Is it called "modem-tables" in internal documentation? Or did you choose this ominous name? Reviewed-by: Alex Elder <elder@riscstar.com> > --- > Documentation/devicetree/bindings/sram/qcom,imem.yaml | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/devicetree/bindings/sram/qcom,imem.yaml b/Documentation/devicetree/bindings/sram/qcom,imem.yaml > index 2711f90d9664b70fcd1e2f7e2dfd3386ed5c1952..7c882819222dc04190db357ac6f9a3a35137cc9e 100644 > --- a/Documentation/devicetree/bindings/sram/qcom,imem.yaml > +++ b/Documentation/devicetree/bindings/sram/qcom,imem.yaml > @@ -51,6 +51,9 @@ properties: > $ref: /schemas/power/reset/syscon-reboot-mode.yaml# > > patternProperties: > + "^modem-tables@[0-9a-f]+$": > + description: Region reserved for the IP Accelerator > + > "^pil-reloc@[0-9a-f]+$": > $ref: /schemas/remoteproc/qcom,pil-info.yaml# > description: Peripheral image loader relocation region >
On 5/23/25 7:59 PM, Alex Elder wrote: > On 5/22/25 6:08 PM, Konrad Dybcio wrote: >> From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> >> >> The IP Accelerator hardware/firmware owns a sizeable region within the >> IMEM, ominously named 'modem-tables', presumably having to do with some >> internal IPA-modem specifics. >> >> 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. >> >> Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> > > So this will just show up as a subnode of an sram@... node, > the way "qcom,pil-reloc-info" does. This is great. > > Is it called "modem-tables" in internal documentation? Or > did you choose this ominous name? Downstream. It's hard to find accurate information on this. Konrad
diff --git a/Documentation/devicetree/bindings/sram/qcom,imem.yaml b/Documentation/devicetree/bindings/sram/qcom,imem.yaml index 2711f90d9664b70fcd1e2f7e2dfd3386ed5c1952..7c882819222dc04190db357ac6f9a3a35137cc9e 100644 --- a/Documentation/devicetree/bindings/sram/qcom,imem.yaml +++ b/Documentation/devicetree/bindings/sram/qcom,imem.yaml @@ -51,6 +51,9 @@ properties: $ref: /schemas/power/reset/syscon-reboot-mode.yaml# patternProperties: + "^modem-tables@[0-9a-f]+$": + description: Region reserved for the IP Accelerator + "^pil-reloc@[0-9a-f]+$": $ref: /schemas/remoteproc/qcom,pil-info.yaml# description: Peripheral image loader relocation region