From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jingyi Wang <jingyi.wang@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
aiqun.yu@oss.qualcomm.com, tingwei.zhang@oss.qualcomm.com,
trilok.soni@oss.qualcomm.com, yijie.yang@oss.qualcomm.com
Subject: Re: [PATCH 1/2] dt-bindings: pinctrl: describe Kaanapali TLMM
Date: Thu, 9 Oct 2025 19:39:54 +0900 [thread overview]
Message-ID: <2acd8a45-cb92-42ad-83e6-1fb990d254d6@kernel.org> (raw)
In-Reply-To: <20250924-knp-tlmm-v1-1-acabb59ae48c@oss.qualcomm.com>
On 25/09/2025 08:16, Jingyi Wang wrote:
> The Top Level Mode Multiplexer (TLMM) in the Kaanapali SoC provide GPIO and
> pinctrl functionality for UFS, SDC and 217 GPIO pins.
>
> Add a DeviceTree binding to describe the Kaanapali TLMM block.
>
> Signed-off-by: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
> ---
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-09 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 23:16 [PATCH 0/2] pinctrl: qcom: Introduce Pinctrl for Kaanapali Jingyi Wang
2025-09-24 23:16 ` [PATCH 1/2] dt-bindings: pinctrl: describe Kaanapali TLMM Jingyi Wang
2025-09-25 14:08 ` Bjorn Andersson
2025-10-09 10:39 ` Krzysztof Kozlowski [this message]
2025-09-24 23:16 ` [PATCH 2/2] pinctrl: qcom: add the tlmm driver for Kaanapali platforms Jingyi Wang
2025-09-25 12:43 ` Konrad Dybcio
2025-09-25 14:09 ` Bjorn Andersson
2025-10-03 10:54 ` Bartosz Golaszewski
2025-10-13 10:26 ` [PATCH 0/2] pinctrl: qcom: Introduce Pinctrl for Kaanapali Linus Walleij
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=2acd8a45-cb92-42ad-83e6-1fb990d254d6@kernel.org \
--to=krzk@kernel.org \
--cc=aiqun.yu@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jingyi.wang@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tingwei.zhang@oss.qualcomm.com \
--cc=trilok.soni@oss.qualcomm.com \
--cc=yijie.yang@oss.qualcomm.com \
/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;
as well as URLs for NNTP newsgroup(s).