Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Muzaffer Kadir <muzafferkadir@mainlining.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh@kernel.org>, Linus Walleij <linusw@kernel.org>,
	Bartosz Golaszewski <brgl@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] pinctrl: qcom: Add MSM8952 tlmm pinctrl driver
Date: Mon, 7 Sep 2026 17:19:26 +0300	[thread overview]
Message-ID: <c8f9e9c9-d619-4094-8968-c162d6b2b361@mainlining.org> (raw)
In-Reply-To: <d1ec9149-7034-4002-beaf-d389f0603fc3@oss.qualcomm.com>

On Mon, 7 Sep 2026 15:39:18 +0200, Konrad Dybcio wrote:
> On 9/7/26 3:32 PM, Muzaffer Kadir wrote:
>> Hi Konrad,
>>
>> On Mon, 7 Sep 2026 14:04:59 +0200, Konrad Dybcio wrote:
>>> On 04-Sep-26 14:55, Muzaffer Kadir via B4 Relay wrote:
>>> I told the robot to take a look again (and again and again
>>> a couple more times until it stopped complaining)..
>>>
>>> The following feedback is meaningful:
>>>
>>> Hi Muzaffer,
>>>
>>>   `qdss_tracedata_b_groups` advertises GPIOs that cannot actually select
>>>   the function. Please populate the corresponding PINGROUP slots:
>>>
>>>     GPIO8:  mux 11
>>>     GPIO9:  mux 12
>>>     GPIO12: mux 12
>>>     GPIO13: mux 12
>>
>> I will add these to their pins by sending v5.
>>
>> But also I want to ask,
>> does atest_combodac_to_gpio_native
>> have any mux on gpio12/13/20/21/29/30 ?Or are they wrongly set ?
> 
> Yes they do, the robot pointed that out too but I figured it pulled it
> from the internal data and not from the existing driver. They don't
> really have much of a use outside validation testing I believe, but
> since they're there already:
> 
> pin	func_idx
> 12	14
> 13	14
> 20	11
> 21	11
> 29	10
> 30	11

Hi Konrad,
I noticed that I forgot to say pin 41 (Sorry about that).
Could you provide it too?

Also can I add mpm pins as a seperate commit in v5?
Or should I wait until adding mpm to msm8952 device tree?

Thanks again.

Best regards,
Muzaffer Kadir

  reply	other threads:[~2026-09-07 14:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 12:55 [PATCH v4 0/2] Add pinctrl support for MSM8952 Muzaffer Kadir via B4 Relay
2026-09-04 12:55 ` [PATCH v4 1/2] dt-bindings: pinctrl: qcom: Add MSM8952 pinctrl Muzaffer Kadir via B4 Relay
2026-09-07  9:56   ` Krzysztof Kozlowski
2026-09-04 12:55 ` [PATCH v4 2/2] pinctrl: qcom: Add MSM8952 tlmm pinctrl driver Muzaffer Kadir via B4 Relay
2026-09-07 12:04   ` Konrad Dybcio
2026-09-07 13:32     ` Muzaffer Kadir
2026-09-07 13:39       ` Konrad Dybcio
2026-09-07 14:19         ` Muzaffer Kadir [this message]
2026-09-07 14:28           ` Konrad Dybcio

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=c8f9e9c9-d619-4094-8968-c162d6b2b361@mainlining.org \
    --to=muzafferkadir@mainlining.org \
    --cc=andersson@kernel.org \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --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=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