From: "Padmanabhan Rajanbabu" <p.rajanbabu@samsung.com>
To: "'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<alim.akhtar@samsung.com>, <chanho61.park@samsung.com>,
<linus.walleij@linaro.org>, <pankaj.dubey@samsung.com>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-samsung-soc@vger.kernel.org>
Subject: RE: [PATCH] arm64: dts: fix drive strength macros as per FSD HW UM
Date: Tue, 11 Oct 2022 10:22:59 +0530 [thread overview]
Message-ID: <000001d8dd2d$57d6a060$0783e120$@samsung.com> (raw)
In-Reply-To: <ebf9e667-6b08-4a04-2241-04295cc28058@linaro.org>
> -----Original Message-----
> From: Krzysztof Kozlowski [mailto:krzysztof.kozlowski@linaro.org]
> Sent: 10 October 2022 06:54 PM
> To: Padmanabhan Rajanbabu <p.rajanbabu@samsung.com>;
> robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org;
> alim.akhtar@samsung.com; chanho61.park@samsung.com;
> linus.walleij@linaro.org; pankaj.dubey@samsung.com
> Cc: devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; linux-
> samsung-soc@vger.kernel.org
> Subject: Re: [PATCH] arm64: dts: fix drive strength macros as per FSD HW UM
>
> On 10/10/2022 08:04, Padmanabhan Rajanbabu wrote:
> > In FSD pinctrl implementation, the pinctrl driver is using drive
> > strength MACROs, which are deviating from the actual values specified
> > in FSD HW UM
>
> But you are changing DTS, not pinctrl driver. The message is a bit confusing.
Sorry about the commit description. I'll update it to reflect the right context.
>
> Add full stop to the sentence.
okay
>
> >
> > This patch adds the right pinctrl drive strength values for FSD SoC.
> > This
>
> Do not use "This commit/patch".
> https://protect2.fireeye.com/v1/url?k=7c0c10dd-239729b8-7c0d9b92-
> 000babff32e3-25043687ce355c88&q=1&e=110f55cc-c214-4bfd-b74b-
> 928d7f2efcbc&u=https%3A%2F%2Felixir.bootlin.com%2Flinux%2Fv5.17.1%2F
> source%2FDocumentation%2Fprocess%2Fsubmitting-patches.rst%23L95
Okay.
>
> > patch also ensures that the peripherals are using right drive strength
> > MACROs in-order to function as expected
>
> Full stop
Okay.
>
> Which commit introduced it? Add a Fixes tag.
I'll add the fixes tag.
>
>
> >
> > Signed-off-by: Padmanabhan Rajanbabu <p.rajanbabu@samsung.com>
> > ---
> > arch/arm64/boot/dts/tesla/fsd-pinctrl.dtsi | 34 +++++++++++-----------
> > arch/arm64/boot/dts/tesla/fsd-pinctrl.h | 6 ++--
> > 2 files changed, 20 insertions(+), 20 deletions(-)
> >
> > diff --git a/arch/arm64/boot/dts/tesla/fsd-pinctrl.dtsi
> > b/arch/arm64/boot/dts/tesla/fsd-pinctrl.dtsi
> > index d0abb9aa0e9e..e3852c946352 100644
> > --- a/arch/arm64/boot/dts/tesla/fsd-pinctrl.dtsi
> > +++ b/arch/arm64/boot/dts/tesla/fsd-pinctrl.dtsi
> > @@ -55,14 +55,14 @@
> > samsung,pins = "gpf5-0";
> > samsung,pin-function = <FSD_PIN_FUNC_2>;
> > samsung,pin-pud = <FSD_PIN_PULL_NONE>;
> > - samsung,pin-drv = <FSD_PIN_DRV_LV2>;
> > + samsung,pin-drv = <FSD_PIN_DRV_LV4>;
>
> Are you sure? The original commit used here value of "2", your change also
> set value of "2", so what deviates from actual values?
The intention of the patch is to change the value of MACROs as well as name of the MACROs
according to the FSD HW user manual.
>
> You need to describe better the problem.
In the next version, I'll update the problem description in a much better way.
>
> Best regards,
> Krzysztof
Thanks for quick review.
Regards,
Padmanabhan R.
next prev parent reply other threads:[~2022-10-11 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221010123120epcas5p3ba947a3a982bc6a78310472c2a65ebfe@epcas5p3.samsung.com>
2022-10-10 12:04 ` [PATCH] arm64: dts: fix drive strength macros as per FSD HW UM Padmanabhan Rajanbabu
2022-10-10 13:24 ` Krzysztof Kozlowski
2022-10-11 4:52 ` Padmanabhan Rajanbabu [this message]
2022-10-11 5:23 ` Alim Akhtar
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='000001d8dd2d$57d6a060$0783e120$@samsung.com' \
--to=p.rajanbabu@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=chanho61.park@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=pankaj.dubey@samsung.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;
as well as URLs for NNTP newsgroup(s).