[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAFBinCDCtaqZG4a5jbw64RK4mrccSJTmznTiMPpp+gJNmo2LkA@mail.gmail.com>
Date: Tue, 27 Apr 2021 21:03:28 +0200
From: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
To: Bjorn Andersson <bjorn.andersson@...aro.org>
Cc: linux-remoteproc@...r.kernel.org,
linux-amlogic@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, ohad@...ery.com, robh+dt@...nel.org
Subject: Re: [PATCH 3/5] dt-bindings: remoteproc: Add the documentation for
Meson AO ARC rproc
Hi Bjorn,
On Tue, Apr 13, 2021 at 10:59 PM Bjorn Andersson
<bjorn.andersson@...aro.org> wrote:
[...]
> Describing these kinds blocks in DT is indeed tricky, I've had
> both cases where a block maps to multiple "functions" or where they
> contain misc registers to be used in relation to some other block.
>
> The prior typically lends itself to be modelled as a "simple-mfd" and
> the latter as a "syscon".
I think here the former description matches better
each set of registers has one very specific purpose (pinctrl, GPIO,
I2C, RTC, IR receiver, ...). there's only one exception inside the
whole AO region called "PMU" (which mostly contains power management
registers and a few clock control bits)
> So perhaps you could do a simple-mfd that spans the entire block and
> then describe the remoteproc, watchdog?, pinctrl pieces as children
> under that?
I can send patches for the simple-mfd conversion (syscon won't be
involved) so Rob can also give his feedback.
in my opinion this would not change the dt-bindings for the AO ARC
remote-processor.
Please let me know if there would be any dt-bindings changes so I can
also include this when updating this series.
Best regards,
Martin
Powered by blists - more mailing lists