From: "J.D. Schroeder" <Linux.HWI@garmin.com>
To: Tero Kristo <t-kristo@ti.com>,
linux-kernel@vger.kernel.org, bcousson@baylibre.com,
tony@atomide.com, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, linux@arm.linux.org.uk,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: jay.schroeder@garmin.com
Subject: Re: [PATCH v2 2/3] ARM: DRA7x: dts: Update the OSC_32K_CLK frequency
Date: Tue, 3 May 2016 08:31:11 -0500 [thread overview]
Message-ID: <5728A81F.4050906@garmin.com> (raw)
In-Reply-To: <57285E66.2000708@ti.com>
On 05/03/2016 03:16 AM, Tero Kristo wrote:
> On 02/05/16 20:12, J.D. Schroeder wrote:
>> From: "J.D. Schroeder" <jay.schroeder@garmin.com>
>>
>> This commit updates the OSC_32K_CLK (secure_32k_clk_src_ck) frequency
>> from the precise 32kHz frequency (i.e., 32.768 kHz) to a more
>> accurate frequency of ~34.6 kHz. Actual measured frequencies of the
>> clock vary from processor to processor anywhere from 34.4 kHz up to
>> 34.8 kHz. Note that the ~34 kHz frequency clock is generated
>> internally by the processor, not an input to the processor. This
>> change makes it more clear that the consumer of the
>> secure_32k_clk_src_ck will not get a precise 32.768 kHz frequency
>> output.
>>
>> Signed-off-by: J.D. Schroeder <jay.schroeder@garmin.com>
>> Reviewed-by: Trenton Andres <trenton.andres@garmin.com>
>> ---
>> arch/arm/boot/dts/dra7xx-clocks.dtsi | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/boot/dts/dra7xx-clocks.dtsi
>> b/arch/arm/boot/dts/dra7xx-clocks.dtsi
>> index 3f0c61d..f7ec976 100644
>> --- a/arch/arm/boot/dts/dra7xx-clocks.dtsi
>> +++ b/arch/arm/boot/dts/dra7xx-clocks.dtsi
>> @@ -95,7 +95,7 @@
>> secure_32k_clk_src_ck: secure_32k_clk_src_ck {
>> #clock-cells = <0>;
>> compatible = "fixed-clock";
>> - clock-frequency = <32768>;
>> + clock-frequency = <34600>; /* approximate frequency */
>> };
>>
>> sys_clk32_crystal_ck: sys_clk32_crystal_ck {
>>
>
> I still don't agree with this patch. The actual frequency can drift much more,
> you are just seeing this number at your setup.
Yes, it can drift significantly from processor to processor. Do you agree that
this frequency is closer to what can be expected than 32768 Hz?
Like I said, I would have renamed the clock also but I opted to go the less
obtrusive route while still helping others that might think they can
reasonably use this clock in their design as a 32768 Hz clock source. Perhaps
my comment and selection of the approximate frequency is not the best (I'm
open for suggestions). However, I do think this change is an improvement and
clarifying change to what is currently present in the clock description.
-JD
WARNING: multiple messages have this Message-ID (diff)
From: Linux.HWI@garmin.com (J.D. Schroeder)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] ARM: DRA7x: dts: Update the OSC_32K_CLK frequency
Date: Tue, 3 May 2016 08:31:11 -0500 [thread overview]
Message-ID: <5728A81F.4050906@garmin.com> (raw)
In-Reply-To: <57285E66.2000708@ti.com>
On 05/03/2016 03:16 AM, Tero Kristo wrote:
> On 02/05/16 20:12, J.D. Schroeder wrote:
>> From: "J.D. Schroeder" <jay.schroeder@garmin.com>
>>
>> This commit updates the OSC_32K_CLK (secure_32k_clk_src_ck) frequency
>> from the precise 32kHz frequency (i.e., 32.768 kHz) to a more
>> accurate frequency of ~34.6 kHz. Actual measured frequencies of the
>> clock vary from processor to processor anywhere from 34.4 kHz up to
>> 34.8 kHz. Note that the ~34 kHz frequency clock is generated
>> internally by the processor, not an input to the processor. This
>> change makes it more clear that the consumer of the
>> secure_32k_clk_src_ck will not get a precise 32.768 kHz frequency
>> output.
>>
>> Signed-off-by: J.D. Schroeder <jay.schroeder@garmin.com>
>> Reviewed-by: Trenton Andres <trenton.andres@garmin.com>
>> ---
>> arch/arm/boot/dts/dra7xx-clocks.dtsi | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/boot/dts/dra7xx-clocks.dtsi
>> b/arch/arm/boot/dts/dra7xx-clocks.dtsi
>> index 3f0c61d..f7ec976 100644
>> --- a/arch/arm/boot/dts/dra7xx-clocks.dtsi
>> +++ b/arch/arm/boot/dts/dra7xx-clocks.dtsi
>> @@ -95,7 +95,7 @@
>> secure_32k_clk_src_ck: secure_32k_clk_src_ck {
>> #clock-cells = <0>;
>> compatible = "fixed-clock";
>> - clock-frequency = <32768>;
>> + clock-frequency = <34600>; /* approximate frequency */
>> };
>>
>> sys_clk32_crystal_ck: sys_clk32_crystal_ck {
>>
>
> I still don't agree with this patch. The actual frequency can drift much more,
> you are just seeing this number at your setup.
Yes, it can drift significantly from processor to processor. Do you agree that
this frequency is closer to what can be expected than 32768 Hz?
Like I said, I would have renamed the clock also but I opted to go the less
obtrusive route while still helping others that might think they can
reasonably use this clock in their design as a 32768 Hz clock source. Perhaps
my comment and selection of the approximate frequency is not the best (I'm
open for suggestions). However, I do think this change is an improvement and
clarifying change to what is currently present in the clock description.
-JD
WARNING: multiple messages have this Message-ID (diff)
From: "J.D. Schroeder" <Linux.HWI@garmin.com>
To: Tero Kristo <t-kristo@ti.com>, <linux-kernel@vger.kernel.org>,
<bcousson@baylibre.com>, <tony@atomide.com>, <robh+dt@kernel.org>,
<pawel.moll@arm.com>, <mark.rutland@arm.com>,
<ijc+devicetree@hellion.org.uk>, <galak@codeaurora.org>,
<linux@arm.linux.org.uk>, <linux-omap@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: <jay.schroeder@garmin.com>
Subject: Re: [PATCH v2 2/3] ARM: DRA7x: dts: Update the OSC_32K_CLK frequency
Date: Tue, 3 May 2016 08:31:11 -0500 [thread overview]
Message-ID: <5728A81F.4050906@garmin.com> (raw)
In-Reply-To: <57285E66.2000708@ti.com>
On 05/03/2016 03:16 AM, Tero Kristo wrote:
> On 02/05/16 20:12, J.D. Schroeder wrote:
>> From: "J.D. Schroeder" <jay.schroeder@garmin.com>
>>
>> This commit updates the OSC_32K_CLK (secure_32k_clk_src_ck) frequency
>> from the precise 32kHz frequency (i.e., 32.768 kHz) to a more
>> accurate frequency of ~34.6 kHz. Actual measured frequencies of the
>> clock vary from processor to processor anywhere from 34.4 kHz up to
>> 34.8 kHz. Note that the ~34 kHz frequency clock is generated
>> internally by the processor, not an input to the processor. This
>> change makes it more clear that the consumer of the
>> secure_32k_clk_src_ck will not get a precise 32.768 kHz frequency
>> output.
>>
>> Signed-off-by: J.D. Schroeder <jay.schroeder@garmin.com>
>> Reviewed-by: Trenton Andres <trenton.andres@garmin.com>
>> ---
>> arch/arm/boot/dts/dra7xx-clocks.dtsi | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/boot/dts/dra7xx-clocks.dtsi
>> b/arch/arm/boot/dts/dra7xx-clocks.dtsi
>> index 3f0c61d..f7ec976 100644
>> --- a/arch/arm/boot/dts/dra7xx-clocks.dtsi
>> +++ b/arch/arm/boot/dts/dra7xx-clocks.dtsi
>> @@ -95,7 +95,7 @@
>> secure_32k_clk_src_ck: secure_32k_clk_src_ck {
>> #clock-cells = <0>;
>> compatible = "fixed-clock";
>> - clock-frequency = <32768>;
>> + clock-frequency = <34600>; /* approximate frequency */
>> };
>>
>> sys_clk32_crystal_ck: sys_clk32_crystal_ck {
>>
>
> I still don't agree with this patch. The actual frequency can drift much more,
> you are just seeing this number at your setup.
Yes, it can drift significantly from processor to processor. Do you agree that
this frequency is closer to what can be expected than 32768 Hz?
Like I said, I would have renamed the clock also but I opted to go the less
obtrusive route while still helping others that might think they can
reasonably use this clock in their design as a 32768 Hz clock source. Perhaps
my comment and selection of the approximate frequency is not the best (I'm
open for suggestions). However, I do think this change is an improvement and
clarifying change to what is currently present in the clock description.
-JD
next prev parent reply other threads:[~2016-05-03 13:31 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 17:54 [PATCH 0/3] AM57/DRA7 Clock Tree DTSI Fix-ups J.D. Schroeder
2016-04-26 17:54 ` J.D. Schroeder
2016-04-26 17:54 ` J.D. Schroeder
2016-04-26 17:54 ` [PATCH 1/3] DRA7: Fix clock data for gmac_gmii_ref_clk_div J.D. Schroeder
2016-04-26 17:54 ` J.D. Schroeder
2016-04-26 17:54 ` J.D. Schroeder
2016-04-27 11:21 ` Tero Kristo
2016-04-27 11:21 ` Tero Kristo
2016-04-27 11:21 ` Tero Kristo
2016-04-27 16:36 ` Tony Lindgren
2016-04-27 16:36 ` Tony Lindgren
[not found] ` <20160427163640.GZ5995-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2016-04-27 17:16 ` Tony Lindgren
2016-04-27 17:16 ` Tony Lindgren
2016-04-27 17:16 ` Tony Lindgren
2016-05-02 17:12 ` [PATCH v2 0/3] AM57/DRA7 Clock Tree DTSI Fix-ups J.D. Schroeder
2016-05-02 17:12 ` J.D. Schroeder
2016-05-02 17:12 ` J.D. Schroeder
2016-05-02 17:12 ` [PATCH v2 1/3] DRA7: Fix clock data for gmac_gmii_ref_clk_div J.D. Schroeder
2016-05-02 17:12 ` J.D. Schroeder
2016-05-02 17:12 ` J.D. Schroeder
2016-05-02 17:12 ` [PATCH v2 2/3] ARM: DRA7x: dts: Update the OSC_32K_CLK frequency J.D. Schroeder
2016-05-02 17:12 ` J.D. Schroeder
2016-05-02 17:12 ` J.D. Schroeder
2016-05-03 8:16 ` Tero Kristo
2016-05-03 8:16 ` Tero Kristo
2016-05-03 8:16 ` Tero Kristo
2016-05-03 13:31 ` J.D. Schroeder [this message]
2016-05-03 13:31 ` J.D. Schroeder
2016-05-03 13:31 ` J.D. Schroeder
2016-05-03 16:43 ` Tony Lindgren
2016-05-03 16:43 ` Tony Lindgren
[not found] ` <20160503164323.GN5995-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2016-05-03 17:32 ` Tero Kristo
2016-05-03 17:32 ` Tero Kristo
2016-05-03 17:32 ` Tero Kristo
[not found] ` <5728E0BC.3080509-l0cyMroinI0@public.gmane.org>
2016-05-03 17:49 ` J.D. Schroeder
2016-05-03 17:49 ` J.D. Schroeder
2016-05-03 17:49 ` J.D. Schroeder
[not found] ` <5728E495.4010502-UF6BFNFdnjXQT0dZR+AlfA@public.gmane.org>
2016-05-03 18:08 ` Tony Lindgren
2016-05-03 18:08 ` Tony Lindgren
2016-05-03 18:08 ` Tony Lindgren
2016-05-03 18:08 ` Tero Kristo
2016-05-03 18:08 ` Tero Kristo
2016-05-03 18:08 ` Tero Kristo
2016-05-03 23:17 ` Nishanth Menon
2016-05-03 23:17 ` Nishanth Menon
2016-05-03 23:17 ` Nishanth Menon
2016-05-04 14:09 ` Matthijs van Duin
2016-05-04 14:09 ` Matthijs van Duin
2016-05-04 14:09 ` Matthijs van Duin
[not found] ` <1462209123-7332-1-git-send-email-Linux.HWI-UF6BFNFdnjXQT0dZR+AlfA@public.gmane.org>
2016-05-02 17:12 ` [PATCH v2 3/3] ARM: dts: dra7: fix clock node definition to avoid build warning J.D. Schroeder
2016-05-02 17:12 ` J.D. Schroeder
2016-05-02 17:12 ` J.D. Schroeder
2016-05-03 4:20 ` [PATCH v2 0/3] AM57/DRA7 Clock Tree DTSI Fix-ups Lokesh Vutla
2016-05-03 4:20 ` Lokesh Vutla
2016-05-03 4:20 ` Lokesh Vutla
2016-04-26 17:54 ` [PATCH 2/3] ARM: DRA7x: dts: Fix the 32kHz clock calculation J.D. Schroeder
2016-04-26 17:54 ` J.D. Schroeder
2016-04-26 17:54 ` J.D. Schroeder
2016-04-27 11:40 ` Tero Kristo
2016-04-27 11:40 ` Tero Kristo
2016-04-27 11:40 ` Tero Kristo
[not found] ` <5720A51E.2000900-l0cyMroinI0@public.gmane.org>
2016-04-27 14:06 ` J.D. Schroeder
2016-04-27 14:06 ` J.D. Schroeder
2016-04-27 14:06 ` J.D. Schroeder
[not found] ` <5720C77A.3020708-UF6BFNFdnjXQT0dZR+AlfA@public.gmane.org>
2016-04-27 19:47 ` Tero Kristo
2016-04-27 19:47 ` Tero Kristo
2016-04-27 19:47 ` Tero Kristo
2016-04-27 20:13 ` J.D. Schroeder
2016-04-27 20:13 ` J.D. Schroeder
2016-04-27 20:13 ` J.D. Schroeder
2016-04-26 17:54 ` [PATCH 3/3] ARM: DRA7x: dts: Update the OSC_32K_CLK frequency J.D. Schroeder
2016-04-26 17:54 ` J.D. Schroeder
2016-04-26 17:54 ` J.D. Schroeder
2016-04-27 11:49 ` Tero Kristo
2016-04-27 11:49 ` Tero Kristo
2016-04-27 11:49 ` Tero Kristo
[not found] ` <5720A73B.6050408-l0cyMroinI0@public.gmane.org>
2016-04-27 14:20 ` J.D. Schroeder
2016-04-27 14:20 ` J.D. Schroeder
2016-04-27 14:20 ` J.D. Schroeder
[not found] ` <1461693269-19436-1-git-send-email-Linux.HWI-UF6BFNFdnjXQT0dZR+AlfA@public.gmane.org>
2016-04-26 18:13 ` [PATCH 0/3] AM57/DRA7 Clock Tree DTSI Fix-ups Tony Lindgren
2016-04-26 18:13 ` Tony Lindgren
2016-04-26 18:13 ` Tony Lindgren
2016-04-26 19:18 ` J.D. Schroeder
2016-04-26 19:18 ` J.D. Schroeder
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=5728A81F.4050906@garmin.com \
--to=linux.hwi@garmin.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jay.schroeder@garmin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.