From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Frank Li <Frank.li@nxp.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 10/10] arm64: dts: imx8mp-skov: increase I2C clock frequency for RTC
Date: Fri, 20 Dec 2024 10:12:49 +0100 [thread overview]
Message-ID: <2ae085fa-6f13-4eb7-88c1-e625309fc35e@pengutronix.de> (raw)
In-Reply-To: <Z2Rw8qnn9hULyh8l@lizhi-Precision-Tower-5810>
Hello Frank,
On 19.12.24 20:16, Frank Li wrote:
> On Thu, Dec 19, 2024 at 06:51:35PM +0100, Ahmad Fatoum wrote:
>> On 19.12.24 18:47, Frank Li wrote:
>>> On Thu, Dec 19, 2024 at 08:25:34AM +0100, Ahmad Fatoum wrote:
>>>> From: Oleksij Rempel <o.rempel@pengutronix.de>
>>>>
>>>> The NXP PCF85063TP RTC we use is capable of up to 400 kHz of SCL clock
>>>> frequency, so let's make use of this instead of the 100 kHz bus frequency
>>>> we are currently using.
>>>
>>> Increase I2C frequency to 400khz from 100kHz because NXP PCF85063TP RTC
>>> support it.
>>
>> Unlike your other suggestions, these is no information lost by rewriting
>> the commit message as you suggest. I don't mind, but must admit it feels
>> like bikeshedding. What is your concrete objection to my commit message?
>
> According to
> https://docs.kernel.org/process/submitting-patches.html
>
> Describe your changes in imperative mood, e.g. “make xyzzy do frotz”
> instead of “[This patch] makes xyzzy do frotz” or
> “[I] changed xyzzy to do frotz”, as if you are giving orders to the
> codebase to change its behaviour.
I have to disagree with your interpretation. The imperative mood is primarily
expected for commit message titles, but if you take a look at normal commit
message _bodies_ that make it into the kernel, you'll find that a whole lot
of them start off like I do: Describe the situation and then what's done about
it.
I personally find that this is often easier to follow than just having two
imperatives back-to-back.
I have just Cc'd you on an RFC patch to amend the documentation you linked
to reflect this. I am happy to continue the discussion over there:
https://lore.kernel.org/workflows/20241220-submitting-patches-imperative-v1-0-ee874c1859b3@pengutronix.de/T/#t
Thanks,
Ahmad
>
> Generally, avoid use
>
> "this patch ..."
> "let's ...."
> "we do ... for ... "
>
> Just simple said
>
> Do ... to ...
> Do ... because ...
>
> Frank
>
>>
>> Thanks,
>> Ahmad
>>
>>
>>>
>>> Frank
>>>
>>>>
>>>> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
>>>> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>>>> ---
>>>> arch/arm64/boot/dts/freescale/imx8mp-skov-reva.dtsi | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-skov-reva.dtsi b/arch/arm64/boot/dts/freescale/imx8mp-skov-reva.dtsi
>>>> index a683f46fcbab..ec7857db7bf0 100644
>>>> --- a/arch/arm64/boot/dts/freescale/imx8mp-skov-reva.dtsi
>>>> +++ b/arch/arm64/boot/dts/freescale/imx8mp-skov-reva.dtsi
>>>> @@ -333,7 +333,7 @@ reg_nvcc_sd2: LDO5 {
>>>> };
>>>>
>>>> &i2c3 {
>>>> - clock-frequency = <100000>;
>>>> + clock-frequency = <400000>;
>>>> pinctrl-names = "default";
>>>> pinctrl-0 = <&pinctrl_i2c3>;
>>>> status = "okay";
>>>>
>>>> --
>>>> 2.39.5
>>>>
>>>
>>
>>
>> --
>> Pengutronix e.K. | |
>> Steuerwalder Str. 21 | http://www.pengutronix.de/ |
>> 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
>> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-12-20 9:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 7:25 [PATCH 00/10] arm64: dts: imx8mp-skov: flesh out device trees Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 01/10] arm64: dts: imx8mp-skov: correct PMIC board limits Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 02/10] arm64: dts: imx8mp-skov: operate CPU at 850 mV by default Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 03/10] arm64: dts: imx8mp-skov: use I2C5 for DDC Ahmad Fatoum
2024-12-19 17:34 ` Frank Li
2024-12-19 17:43 ` Ahmad Fatoum
2024-12-19 19:27 ` Frank Li
2025-01-06 15:27 ` Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 04/10] arm64: dts: imx8mp-skov: describe HDMI display pipeline Ahmad Fatoum
2024-12-19 17:35 ` Frank Li
2024-12-19 17:40 ` Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 05/10] dt-bindings: display/lvds-codec: add ti,sn65lvds822 Ahmad Fatoum
2024-12-31 1:04 ` Rob Herring (Arm)
2024-12-19 7:25 ` [PATCH 06/10] arm64: dts: imx8mp-skov: describe LVDS display pipeline Ahmad Fatoum
2024-12-19 17:37 ` Frank Li
2024-12-19 17:45 ` Ahmad Fatoum
2024-12-19 19:24 ` Frank Li
2025-01-06 15:36 ` Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 07/10] arm64: dts: imx8mp-skov: configure uart1 for RS485 Ahmad Fatoum
2024-12-19 17:42 ` Frank Li
2024-12-19 17:47 ` Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 08/10] arm64: dts: imx8mp-skov: describe mains fail detection Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 09/10] arm64: dts: imx8mp-skov: fix phy-mode Ahmad Fatoum
2024-12-19 17:45 ` Frank Li
2024-12-19 17:49 ` Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 10/10] arm64: dts: imx8mp-skov: increase I2C clock frequency for RTC Ahmad Fatoum
2024-12-19 17:47 ` Frank Li
2024-12-19 17:51 ` Ahmad Fatoum
2024-12-19 19:16 ` Frank Li
2024-12-20 9:12 ` Ahmad Fatoum [this message]
2024-12-20 15:38 ` Frank Li
2025-01-06 15:59 ` Ahmad Fatoum
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=2ae085fa-6f13-4eb7-88c1-e625309fc35e@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=Frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).