Re: [PATCH v5 5/7] arm64: dts: qcom: Add device tree for Nord Embedded variant

[Shawn Guo]

On Wed, Jul 15, 2026 at 03:03:57PM -0500, Bjorn Andersson wrote:
> On Tue, Jul 14, 2026 at 08:15:24PM +0800, Shawn Guo wrote:
> > On Sun, Jul 12, 2026 at 10:39:44AM -0500, Bjorn Andersson wrote:
> > > On Thu, Jul 09, 2026 at 09:20:11PM +0800, Shawn Guo wrote:
> > > > Unlike the GearVM variant, Nord Embedded variant has platform resources
> > > > (clocks, regulators, powerdomains, pins, etc.) directly controlled by
> > > > Linux.
[...]
> > > > +&ufs_mem_hc {
> > > > +	reg = <0x0 0x01d44000 0x0 0x3000>,
> > > > +	      <0x0 0x01d60000 0x0 0x15000>;
> > > > +	reg-names = "std",
> > > > +		    "mcq";
> > > 
> > > All other changes in this patch directly relates to resource providers,
> > > why does the UFS controller's mmio ranges change?
> > 
> > We can have them in nord.dtsi just like all other device nodes, but we
> > will need to delete reg-names from nord-gearvm.dtsi, since
> > qcom,sa8255p-ufshc binding doesn't require reg-names.
> > 
> > @@ -2907,5 +2907,6 @@ &ufs_mem_hc {
> >         compatible = "qcom,sa8797p-ufshc",
> >                      "qcom,sa8255p-ufshc";
> >         reg = <0x0 0x01d44000 0x0 0x3000>;
> > +       /delete-property/ reg-names;
> >         power-domains = <&scmi3_pd 0>;
> >  };
> > 
> > I will do this with v6, unless you hate delete-property.
> > 
> 
> Now I see the answer is was actually looking for: the SCMI-based variant
> doesn't list the mcq region. Why is that?

Good question! It seems to be a binding problem to me. I just proposed
a fix [1] and will move reg/reg-names into nord.dtsi to be shared by both
variants. It will be neat. But that also means we will have one more
dependency for v6 of the series, sadly.

Shawn

[1] https://lore.kernel.org/all/20260716083313.2367249-1-shengchao.guo@xxxxxxxxxxxxxxxx/