Re: [PATCH 1/2] dt-bindings: pinctrl: qcom: Add qcom,remote-owned for ownership update
From: Linus Walleij
Date: Sat Nov 21 2026 - 15:47:02 EST
On Tue, Nov 10, 2026 at 2:28 PM Krzysztof Kozlowski <krzk@xxxxxxxxxx> wrote:
> On Fri, Nov 06, 2026 at 01:29:41PM +0530, Pankaj Patil wrote:
> > Add "qcom,remote-owned" boolean flag for egpio capable pins since they can
> > be owned by remote island io independently of the selected mux function
> > even if function is non-egpio.
> >
> > Presently egpio is treated as a mux function level decision where as
> > hardware programming guide(hpg) specifies it as pin conf level decision
> > i.e setting egpio bit is independent of selected mux function, the
> > driver/apps claims the ownership of the pin if it's egpio capable in
> > case of mux function being specified as anything other than egpio.
>
> I don't understand this. If the pin is not owned by Linux, then simply
> do not list it. What is the point of listing a pin configuration which
> should be skipped?
We have instances of device trees which are maintained in Linux
being used by e.g. secure world, U-Boot...
So something else is using it perhaps?
But I don't think the device tree should decide system partitioning
like that. I think the boot loader should set gpio-reserved-ranges = ...
before passing the devicetree to Linux instead, then pass
other reserved ranges to other operating systems in the
same physical system etc.
Yours,
Linus Walleij