From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bhavya Kapoor <b-kapoor@ti.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
kristo@kernel.org, nm@ti.com
Subject: Re: [EXTERNAL] Re: [PATCH] arm64: dts: ti: k3-j721s2: Add support for ADC nodes
Date: Wed, 21 Dec 2022 08:54:49 +0100 [thread overview]
Message-ID: <79ffe459-3827-ea67-e854-8eef3d9b630b@linaro.org> (raw)
In-Reply-To: <a4d11974-eb97-bfa2-790f-3016950ea961@ti.com>
On 21/12/2022 06:42, Bhavya Kapoor wrote:
>
> On 20/12/22 16:20, Krzysztof Kozlowski wrote:
>> On 20/12/2022 11:12, Bhavya Kapoor wrote:
>>> J721s2 has two instances of 8 channel ADCs in MCU domain. Add DT nodes
>>> for 8 channel ADCs for J721s2 SoC.
>>>
>>> Signed-off-by: Bhavya Kapoor <b-kapoor@ti.com>
>>> ---
>>> .../dts/ti/k3-j721s2-common-proc-board.dts | 14 +++++++
>>> .../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 42 ++++++++++++++++++-
>>> 2 files changed, 55 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dts b/arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dts
>>> index a7aa6cf08acd..67593aa69327 100644
>>> --- a/arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dts
>>> +++ b/arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dts
>>> @@ -309,3 +309,17 @@ &mcu_mcan1 {
>>> pinctrl-0 = <&mcu_mcan1_pins_default>;
>>> phys = <&transceiver2>;
>>> };
>>> +
>>> +&tscadc0 {
>>> + status = "okay";
>>> + adc {
>>> + ti,adc-channels = <0 1 2 3 4 5 6 7>;
>>> + };
>>> +};
>>> +
>>> +&tscadc1 {
>>> + status = "okay";
>>> + adc {
>>> + ti,adc-channels = <0 1 2 3 4 5 6 7>;
>>> + };
>>> +};
>>> \ No newline at end of file
>> This is a friendly reminder during the review process.
>>
>> It seems my previous comments were not fully addressed. Maybe my
>> feedback got lost between the quotes, maybe you just forgot to apply it.
>> Please go back to the previous discussion and either implement all
>> requested changes or keep discussing them.
>>
>> Thank you.
>>
>> Best regards,
>> Krzysztof
>
> Hi , I thought i did addressed the feedback since tscadc is just a
> wrapper node.
>
> The actual adc node is inside of tscadc node.
Read the feedback, from all emails.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-12-21 7:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 10:12 Bhavya Kapoor
2022-12-20 10:50 ` Krzysztof Kozlowski
2022-12-21 5:42 ` [EXTERNAL] " Bhavya Kapoor
2022-12-21 7:54 ` Krzysztof Kozlowski [this message]
2022-12-22 10:39 ` Bhavya Kapoor
2022-12-22 10:46 ` Krzysztof Kozlowski
2022-12-22 11:53 ` Bhavya Kapoor
2022-12-22 11:58 ` Krzysztof Kozlowski
2022-12-22 12:00 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2022-11-08 7:32 Bhavya Kapoor
2022-11-08 18:18 ` Krzysztof Kozlowski
2022-11-09 6:43 ` [EXTERNAL] " Bhavya Kapoor
2022-11-08 7:32 Bhavya Kapoor
2022-11-08 18:18 ` Krzysztof Kozlowski
2022-11-09 6:47 ` [EXTERNAL] " Bhavya Kapoor
2022-12-20 9:56 ` Bhavya Kapoor
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=79ffe459-3827-ea67-e854-8eef3d9b630b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--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®