mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pankaj Patil <pankaj.patil@oss.qualcomm.com>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
	 Bjorn Andersson <andersson@kernel.org>,
	Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Prasad Sodagudi <quic_psodagud@quicinc.com>,
	Rajendra Nayak <quic_rjendra@quicinc.com>,
	 linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: pinctrl: qcom: Add qcom,remote-owned for ownership update
Date: Tue, 10 Nov 2026 14:28:38 +0100	[thread overview]
Message-ID: <20261110-modest-significant-ostrich-8dd408@quoll> (raw)
In-Reply-To: <20261106-egpio_fix-v1-1-569d220a4748@oss.qualcomm.com>

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?

Best regards,
Krzysztof


  reply	other threads:[~2026-11-10 13:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06  7:59 [PATCH 0/2] pinctrl: qcom: Allow eGPIO ownership independent of the mux function Pankaj Patil
2026-11-06  7:59 ` [PATCH 1/2] dt-bindings: pinctrl: qcom: Add qcom,remote-owned for ownership update Pankaj Patil
2026-11-10 13:28   ` Krzysztof Kozlowski [this message]
2026-11-06  7:59 ` [PATCH 2/2] pinctrl: qcom: Add qcom,remote-owned pin configuration support Pankaj Patil
2026-11-10 11:27   ` Bartosz Golaszewski

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=20261110-modest-significant-ostrich-8dd408@quoll \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pankaj.patil@oss.qualcomm.com \
    --cc=quic_psodagud@quicinc.com \
    --cc=quic_rjendra@quicinc.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

all inboxes | Powered by JetHome®