public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Linus Walleij <linusw@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Robert Marko <robimarko@gmail.com>,
	Guru Das Srinagesh <linux@gurudas.dev>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: [PATCH 4/9] pinctrl: qcom: Introduce IPQ5210 TLMM driver
Date: Mon, 16 Mar 2026 16:28:26 +0530	[thread overview]
Message-ID: <384f366f-b2b6-4bdc-a2a8-ba86714aa094@oss.qualcomm.com> (raw)
In-Reply-To: <c89449b8-f28c-4364-a1be-5267f0d99c01@oss.qualcomm.com>


On 3/16/2026 3:16 PM, Konrad Dybcio wrote:
> On 3/16/26 9:58 AM, Kathiravan Thirumoorthy wrote:
>> On 3/13/2026 6:24 PM, Konrad Dybcio wrote:
>>> On 3/11/26 10:45 AM, Kathiravan Thirumoorthy wrote:
>>>> Qualcomm's IPQ5210 SoC comes with a TLMM block, like all other platforms,
>>>> so add a driver for it.
>>>>
>>>> Signed-off-by: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
>>>> ---
>>> [...]
>>>
>>>> +static const char *const Led00_groups[] = {
>>> odd uppercase
>>
>> Yeah,  in HW document also only this name has the uppercase. So I just left it to align with the HW document. Do you prefer to change it to lower case to maintain consistency?
> Yes, please - I would assume the original author had made a typo and
> didn't really intend to have a single random occurrence of an uppercase
> letter

Ack.

>
>>
>>>> +    "gpio23",
>>>> +};
>>>> +
>>>> +static const char *const led01_groups[] = {
>>>> +    "gpio39",
>>>> +};
>>>> +
>>>> +static const char *const led02_groups[] = {
>>>> +    "gpio6",
>>>> +};
>>> What do these 'ledN[012]' functions represent? Are they muxes for
>>> getting activity/status signals for eth/wlan ports?
>>
>> Yes, that's right. These LED functions used for the eth/wlan status.
> Can we better group them, e.g. into threes in 'led[012]' functions?
> (or whichever way they're coupled?)

Ack.

>
> Konrad

  reply	other threads:[~2026-03-16 10:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11  9:45 [PATCH 0/9] Add minimal boot support for Qualcomm IPQ5210 Kathiravan Thirumoorthy
2026-03-11  9:45 ` [PATCH 1/9] dt-bindings: clock: add Qualcomm IPQ5210 GCC Kathiravan Thirumoorthy
2026-03-13 13:22   ` Krzysztof Kozlowski
2026-03-16  7:16     ` Kathiravan Thirumoorthy
2026-03-11  9:45 ` [PATCH 2/9] clk: qcom: add Global Clock controller (GCC) driver for IPQ5210 SoC Kathiravan Thirumoorthy
2026-03-11 14:50   ` Dmitry Baryshkov
2026-03-13  8:42     ` Kathiravan Thirumoorthy
2026-03-11  9:45 ` [PATCH 3/9] dt-bindings: pinctrl: qcom: add IPQ5210 pinctrl Kathiravan Thirumoorthy
2026-03-13 13:24   ` Krzysztof Kozlowski
2026-03-16  7:18     ` Kathiravan Thirumoorthy
2026-03-11  9:45 ` [PATCH 4/9] pinctrl: qcom: Introduce IPQ5210 TLMM driver Kathiravan Thirumoorthy
2026-03-11 14:45   ` Dmitry Baryshkov
2026-03-13 12:54   ` Konrad Dybcio
2026-03-16  8:58     ` Kathiravan Thirumoorthy
2026-03-16  9:46       ` Konrad Dybcio
2026-03-16 10:58         ` Kathiravan Thirumoorthy [this message]
2026-03-11  9:45 ` [PATCH 5/9] dt-bindings: qcom: add ipq5210 boards Kathiravan Thirumoorthy
2026-03-13 13:20   ` Krzysztof Kozlowski
2026-03-11  9:45 ` [PATCH 6/9] dt-bindings: mmc: sdhci-msm: add IPQ5210 compatible Kathiravan Thirumoorthy
2026-03-13 13:19   ` Krzysztof Kozlowski
2026-03-16 15:15   ` Ulf Hansson
2026-03-11  9:45 ` [PATCH 7/9] dt-bindings: firmware: qcom,scm: Document ipq5210 SCM Kathiravan Thirumoorthy
2026-03-13 13:19   ` Krzysztof Kozlowski
2026-03-11  9:45 ` [PATCH 8/9] arm64: dts: qcom: add IPQ5210 SoC and rdp504 board support Kathiravan Thirumoorthy
2026-03-13 12:48   ` Konrad Dybcio
2026-03-16  9:03     ` Kathiravan Thirumoorthy
2026-03-16  9:34       ` Konrad Dybcio
2026-03-22  5:31         ` Sumit Garg
2026-03-11  9:45 ` [PATCH 9/9] arm64: defconfig: enable IPQ5210 RDP504 base configs Kathiravan Thirumoorthy
2026-03-13 13:19   ` Krzysztof Kozlowski
2026-03-11 13:01 ` [PATCH 0/9] Add minimal boot support for Qualcomm IPQ5210 Linus Walleij
2026-03-13  6:55   ` Kathiravan Thirumoorthy
2026-03-13 13:25 ` Krzysztof Kozlowski
2026-03-16  7:27   ` Kathiravan Thirumoorthy

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=384f366f-b2b6-4bdc-a2a8-ba86714aa094@oss.qualcomm.com \
    --to=kathiravan.thirumoorthy@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux@gurudas.dev \
    --cc=mturquette@baylibre.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=robimarko@gmail.com \
    --cc=sboyd@kernel.org \
    --cc=ulf.hansson@linaro.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