From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: chanho61.park@samsung.com, pankaj.dubey@samsung.com,
alim.akhtar@samsung.com, linus.walleij@linaro.org,
robh+dt@kernel.org,
Padmanabhan Rajanbabu <p.rajanbabu@samsung.com>,
krzysztof.kozlowski+dt@linaro.org
Cc: devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] arm64: dts: fix drive strength macros and values for FSD Platform
Date: Tue, 18 Oct 2022 09:25:07 -0400 [thread overview]
Message-ID: <81220c13-56e3-eda5-8b60-68b0f7a1feee@linaro.org> (raw)
In-Reply-To: <166609930553.9199.13331632528050957780.b4-ty@linaro.org>
On 18/10/2022 09:21, Krzysztof Kozlowski wrote:
> On Thu, 13 Oct 2022 16:10:20 +0530, Padmanabhan Rajanbabu wrote:
>> With reference to FSD SoC HW UM, there are some deviations in the
>> drive strength macros names and macro values. Also the IPs are not
>> using the default drive strength values as recommended by HW UM.
>>
>> FSD SoC pinctrl has following four levels of drive-strength and their
>> corresponding values:
>> Level-1 <-> 0
>> Level-2 <-> 1
>> Level-4 <-> 2
>> Level-6 <-> 3
>>
>> [...]
>
> Applied, thanks!
>
> [1/4] arm64: dts: fix drive strength macros as per FSD HW UM
> https://git.kernel.org/krzk/linux/c/3a27bce7e13e3b5368377c9a518927e197a4afb1
> [2/4] arm64: dts: fix HSI2C drive strength values as per FSD HW UM
> https://git.kernel.org/krzk/linux/c/bb997d949e5a835f626facfd67b1768fd4492398
Fixed subject and squashed last two commits into this one.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-10-18 13:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221013110708epcas5p3c54c22bbc77175eb2a26dc9fd43814d5@epcas5p3.samsung.com>
2022-10-13 10:40 ` [PATCH v3 0/4] arm64: dts: fix drive strength macros and values for FSD Platform Padmanabhan Rajanbabu
[not found] ` <CGME20221013110721epcas5p44cc7dcc5ac2ab8eaf6c472cc87dea06f@epcas5p4.samsung.com>
2022-10-13 10:40 ` [PATCH v3 1/4] arm64: dts: fix drive strength macros as per FSD HW UM Padmanabhan Rajanbabu
2022-10-14 1:38 ` Alim Akhtar
[not found] ` <CGME20221013110725epcas5p1411c422eb2c29494fd5c1e66e09564c5@epcas5p1.samsung.com>
2022-10-13 10:40 ` [PATCH v3 2/4] arm64: dts: fix HSI2C drive strength values " Padmanabhan Rajanbabu
2022-10-14 1:39 ` Alim Akhtar
[not found] ` <CGME20221013110728epcas5p22fb8b83f6cfb4b6a035a9fbb5a38546f@epcas5p2.samsung.com>
2022-10-13 10:40 ` [PATCH v3 3/4] arm64: dts: fix UART " Padmanabhan Rajanbabu
2022-10-14 1:41 ` Alim Akhtar
[not found] ` <CGME20221013110733epcas5p36e0104bfa4da37159da77f9231ff6e2c@epcas5p3.samsung.com>
2022-10-13 10:40 ` [PATCH v3 4/4] arm64: dts: fix SPI " Padmanabhan Rajanbabu
2022-10-14 1:41 ` Alim Akhtar
2022-10-18 13:21 ` [PATCH v3 0/4] arm64: dts: fix drive strength macros and values for FSD Platform Krzysztof Kozlowski
2022-10-18 13:21 ` Krzysztof Kozlowski
2022-10-18 13:25 ` Krzysztof Kozlowski [this message]
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=81220c13-56e3-eda5-8b60-68b0f7a1feee@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=chanho61.park@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=p.rajanbabu@samsung.com \
--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).