From: Nikunj Kela <quic_nkela@quicinc.com>
To: <lee@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel@quicinc.com>,
<quic_psodagud@quicinc.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Shazad Hussain <quic_shazhuss@quicinc.com>
Subject: Re: [PATCH v3] dt-bindings: mfd: qcom,tcsr: document support for SA8255p
Date: Mon, 16 Sep 2024 07:25:46 -0700 [thread overview]
Message-ID: <edb25f16-aa9a-4d44-9eb5-63f509f80fde@quicinc.com> (raw)
In-Reply-To: <20240905194741.3803345-1-quic_nkela@quicinc.com>
Gentle ping...
On 9/5/2024 12:47 PM, Nikunj Kela wrote:
> Add compatible for tcsr representing support on SA8255p SoC.
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Shazad Hussain <quic_shazhuss@quicinc.com>
> Signed-off-by: Nikunj Kela <quic_nkela@quicinc.com>
> ---
>
> Changes in v3:
> - Removed the patch from original series[1]
>
> Changes in v2:
> - Added Reviewed-by tag
>
> [1]: https://lore.kernel.org/all/20240903220240.2594102-1-quic_nkela@quicinc.com/
> ---
> Documentation/devicetree/bindings/mfd/qcom,tcsr.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/qcom,tcsr.yaml b/Documentation/devicetree/bindings/mfd/qcom,tcsr.yaml
> index c6bd14ec5aa0..88f804bd7581 100644
> --- a/Documentation/devicetree/bindings/mfd/qcom,tcsr.yaml
> +++ b/Documentation/devicetree/bindings/mfd/qcom,tcsr.yaml
> @@ -21,6 +21,7 @@ properties:
> - qcom,msm8998-tcsr
> - qcom,qcm2290-tcsr
> - qcom,qcs404-tcsr
> + - qcom,sa8255p-tcsr
> - qcom,sc7180-tcsr
> - qcom,sc7280-tcsr
> - qcom,sc8280xp-tcsr
next prev parent reply other threads:[~2024-09-16 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 19:47 Nikunj Kela
2024-09-16 14:25 ` Nikunj Kela [this message]
2024-09-17 8:01 ` Lee Jones
2024-10-02 14:07 ` Lee Jones
2024-10-02 15:24 ` (subset) " Lee Jones
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=edb25f16-aa9a-4d44-9eb5-63f509f80fde@quicinc.com \
--to=quic_nkela@quicinc.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_psodagud@quicinc.com \
--cc=quic_shazhuss@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®