Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1431267 > unrolled thread
| Started by | Alexandre Belloni <alexandre.belloni@free-electrons.com> |
|---|---|
| First post | 2016-06-26 02:50 +0200 |
| Last post | 2016-06-26 17:00 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v3 5/8] rtc: ac100: Add clk output support Alexandre Belloni <alexandre.belloni@free-electrons.com> - 2016-06-26 02:50 +0200
Re: [PATCH v3 5/8] rtc: ac100: Add clk output support Chen-Yu Tsai <wens@csie.org> - 2016-06-26 17:00 +0200
| From | Alexandre Belloni <alexandre.belloni@free-electrons.com> |
|---|---|
| Date | 2016-06-26 02:50 +0200 |
| Subject | Re: [PATCH v3 5/8] rtc: ac100: Add clk output support |
| Message-ID | <rO6qR-4cI-3@gated-at.bofh.it> |
On 20/06/2016 at 10:52:15 +0800, Chen-Yu Tsai wrote :
> +struct ac100_clk32k {
> + struct clk_hw hw;
> + struct regmap *regmap;
> + u8 offset;
> +};
> +
> +#define to_ac100_clk32k(_hw) container_of(_hw, struct ac100_clk32k, hw)
> +
> +#define AC100_RTC_32K_NAME "ac100-rtc-32k"
> +#define AC100_RTC_32K_RATE 32768
> +#define AC100_ADDA_4M_NAME "ac100-adda-4M"
> +#define AC100_ADDA_4M_RATE 4000000
> +#define AC100_CLK32K_NUM 3
> +
> +static const char * const ac100_clk32k_names[] = {
> + "ac100-clk32k-ap",
> + "ac100-clk32k-bb",
> + "ac100-clk32k-md",
> +};
> +
Well, naming things is hard but I don't feel ac100_clk32k and
ac100-clk32k are good prefixes for those clocks as they are actually
dividing a 32KHz or 4MHz clock (one configuration out of 128 is 32KHz).
Else, I don't have any objection.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[toc] | [next] | [standalone]
| From | Chen-Yu Tsai <wens@csie.org> |
|---|---|
| Date | 2016-06-26 17:00 +0200 |
| Message-ID | <rOjHr-4cP-5@gated-at.bofh.it> |
| In reply to | #1431267 |
On Sun, Jun 26, 2016 at 8:45 AM, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
> On 20/06/2016 at 10:52:15 +0800, Chen-Yu Tsai wrote :
>> +struct ac100_clk32k {
>> + struct clk_hw hw;
>> + struct regmap *regmap;
>> + u8 offset;
>> +};
>> +
>> +#define to_ac100_clk32k(_hw) container_of(_hw, struct ac100_clk32k, hw)
>> +
>> +#define AC100_RTC_32K_NAME "ac100-rtc-32k"
>> +#define AC100_RTC_32K_RATE 32768
>> +#define AC100_ADDA_4M_NAME "ac100-adda-4M"
>> +#define AC100_ADDA_4M_RATE 4000000
>> +#define AC100_CLK32K_NUM 3
>> +
>> +static const char * const ac100_clk32k_names[] = {
>> + "ac100-clk32k-ap",
>> + "ac100-clk32k-bb",
>> + "ac100-clk32k-md",
>> +};
>> +
>
> Well, naming things is hard but I don't feel ac100_clk32k and
> ac100-clk32k are good prefixes for those clocks as they are actually
> dividing a 32KHz or 4MHz clock (one configuration out of 128 is 32KHz).
I agree it's a bit misleading. There are 2 names used throughout the
datasheet: 1) CKOn_RTC for the pin names, and 2) CLK32Kxx for the
register names and block diagram.
I'll switch to the pin names, since this is probably what is shown on
board schematics.
> Else, I don't have any objection.
Thanks!
ChenYu
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web