From: Anson Huang <anson.huang@nxp.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"angus@akkea.ca" <angus@akkea.ca>, Abel Vesa <abel.vesa@nxp.com>,
"ccaione@baylibre.com" <ccaione@baylibre.com>,
"andrew.smirnov@gmail.com" <andrew.smirnov@gmail.com>,
"festevam@gmail.com" <festevam@gmail.com>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"agx@sigxcpu.org" <agx@sigxcpu.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"l.stach@pengutronix.de" <l.stach@pengutronix.de>
Subject: RE: [PATCH 1/3] clocksource/drivers/sysctr: Add an optional property
Date: Sun, 23 Jun 2019 11:31:12 +0000 [thread overview]
Message-ID: <DB3PR0402MB3916B3B871FDEA9BFC960C67F5E10@DB3PR0402MB3916.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1906231232520.32342@nanos.tec.linutronix.de>
Hi, Thomas
Thanks for the useful comment, I will resend the patch with improvement.
Anson.
> -----Original Message-----
> From: Thomas Gleixner <tglx@linutronix.de>
> Sent: Sunday, June 23, 2019 6:47 PM
> To: Anson Huang <anson.huang@nxp.com>
> Cc: daniel.lezcano@linaro.org; robh+dt@kernel.org; mark.rutland@arm.com;
> shawnguo@kernel.org; s.hauer@pengutronix.de; kernel@pengutronix.de;
> festevam@gmail.com; l.stach@pengutronix.de; Abel Vesa
> <abel.vesa@nxp.com>; ccaione@baylibre.com; angus@akkea.ca;
> andrew.smirnov@gmail.com; agx@sigxcpu.org; linux-
> kernel@vger.kernel.org; devicetree@vger.kernel.org; linux-arm-
> kernel@lists.infradead.org; dl-linux-imx <linux-imx@nxp.com>
> Subject: Re: [PATCH 1/3] clocksource/drivers/sysctr: Add an optional
> property
>
> Anson,
>
> On Fri, 21 Jun 2019, Anson.Huang@nxp.com wrote:
>
> > Subject : [PATCH 1/3] clocksource/drivers/sysctr: Add an optional
> > property
>
> That subject line is not really informative. From Documentation:
>
> The ``summary phrase`` in the email's Subject should concisely
> describe the patch which that email contains.
>
> That means that it should tell which property it adds so it's immediately clear
> what this is about. Something like:
>
> Subject: clocksource/drivers/sysctr: Add optional clock-frequency property
>
> Hmm?
>
> > From: Anson Huang <Anson.Huang@nxp.com>
> >
> > This patch adds an optional property "clock-frequency" to pass
>
> Please read Documentation/process/submitting-patches.rst and search for
> 'This patch'
>
> > the system counter frequency value to kernel system counter driver and
> > indicate the driver to skip of_clk operations, this is to support
> > those platforms using platform driver model for clock driver.
>
> That sentence does not parse. Please structure your changelog in the
> following order:
>
> 1) Context or problem
>
> 2) Detailed analysis (if applicable and necessary)
>
> 3) Short description of the solution (the rest is obvious from the patch
> itself).
>
> So something like this (assumed I decoded the above correctly):
>
> Systems which use the system counter with the platform driver model
> require the clock frequency to be supplied via device tree.
>
> This is necessary as in the platform driver model the of_clk operations
> do not work correctly because LENGHTY EXPLANATION WHY ...
>
> Add the optinal clock-frequency to the device tree bindings of the NXP
> system counter so the frequency can be handed in and the of_clk
> operations can be skipped.
>
> The important part is the missing LENGTHY EXPLANATION WHY. I can't fill
> that in because you did not provide that information.
>
> Thanks,
>
> tglx
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-23 11:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 8:28 [PATCH 1/3] clocksource/drivers/sysctr: Add an optional property Anson.Huang
2019-06-21 8:28 ` [PATCH 2/3] clocksource: imx-sysctr: Add of_clk skip option Anson.Huang
2019-06-21 8:28 ` [PATCH 3/3] arm64: dts: imx8mq: Add system counter node Anson.Huang
2019-06-22 14:16 ` Martin Kepplinger
2019-06-23 11:20 ` Martin Kepplinger
2019-06-23 11:30 ` Anson Huang
2019-06-23 11:24 ` Anson Huang
2019-06-23 10:46 ` [PATCH 1/3] clocksource/drivers/sysctr: Add an optional property Thomas Gleixner
2019-06-23 11:31 ` Anson Huang [this message]
2019-06-23 11:34 ` Thomas Gleixner
2019-06-23 12:05 ` Anson Huang
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=DB3PR0402MB3916B3B871FDEA9BFC960C67F5E10@DB3PR0402MB3916.eurprd04.prod.outlook.com \
--to=anson.huang@nxp.com \
--cc=abel.vesa@nxp.com \
--cc=agx@sigxcpu.org \
--cc=andrew.smirnov@gmail.com \
--cc=angus@akkea.ca \
--cc=ccaione@baylibre.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tglx@linutronix.de \
/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).