From: Vignesh Raghavendra <vigneshr@ti.com>
To: Bhavya Kapoor <b-kapoor@ti.com>, <devicetree@vger.kernel.org>,
<robh+dt@kernel.org>
Cc: <nm@ti.com>, <kristo@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7 0/2] arm64: dts: ti: k3-j721s2: Add support for ADC nodes
Date: Fri, 17 Mar 2023 09:43:20 +0530 [thread overview]
Message-ID: <5835c3ba-7d69-e9d9-b6bb-9fd7637e85fa@ti.com> (raw)
In-Reply-To: <20230316095146.498999-1-b-kapoor@ti.com>
On 16/03/23 15:21, Bhavya Kapoor wrote:
> J721s2 has two instances of 8 channel ADCs in MCU domain. Add support
> for both ADC nodes in dtsi file. Add pinmux information for both
> instances of ADC in board dts file.
>
> Changelog v6->v7:
> - Created 2 commits for k3-j721s2-mcu-wakeup.dtsi and
> k3-j721s2-common-proc-board.dts instead of a single commit
>
> Bhavya Kapoor (2):
> arm64: dts: ti: k3-j721s2-mcu-wakeup: Add support for ADC nodes
> arm64: dts: ti: k3-j721s2-common-proc-board: Add pinmux information
> for ADC
>
> .../dts/ti/k3-j721s2-common-proc-board.dts | 44 +++++++++++++++++++
> .../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 40 +++++++++++++++++
> 2 files changed, 84 insertions(+)
>
LGTM
Reviewed-by: Vignesh Raghavendra <vigneshr@ti.com>
--
Regards
Vignesh
next prev parent reply other threads:[~2023-03-17 4:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 9:51 Bhavya Kapoor
2023-03-16 9:51 ` [PATCH v7 1/2] arm64: dts: ti: k3-j721s2-mcu-wakeup: " Bhavya Kapoor
2023-03-16 9:51 ` [PATCH v7 2/2] arm64: dts: ti: k3-j721s2-common-proc-board: Add pinmux information for ADC Bhavya Kapoor
2023-03-16 10:47 ` [PATCH v7 0/2] arm64: dts: ti: k3-j721s2: Add support for ADC nodes Bhavya Kapoor
2023-03-17 4:13 ` Vignesh Raghavendra [this message]
2023-03-20 22:57 ` Nishanth Menon
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=5835c3ba-7d69-e9d9-b6bb-9fd7637e85fa@ti.com \
--to=vigneshr@ti.com \
--cc=b-kapoor@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@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®