From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/6] ARM: at91: add TCB registers definitions
Date: Thu, 28 Jun 2018 17:15:39 +0200 [thread overview]
Message-ID: <1bc64ccb-1e22-364c-e08c-fa86692783ff@linaro.org> (raw)
In-Reply-To: <20180619211929.22908-2-alexandre.belloni@bootlin.com>
On 19/06/2018 23:19, Alexandre Belloni wrote:
> Add registers and bits definitions for the timer counter blocks found on
> Atmel ARM SoCs.
>
> Tested-by: Alexander Dahl <ada@thorsis.com>
> Tested-by: Andras Szemzo <szemzo.andras@gmail.com>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> ---
> include/soc/at91/atmel_tcb.h | 216 +++++++++++++++++++++++++++++++++++
Is the header necessary ? Can it be moved in the .c ?
> 1 file changed, 216 insertions(+)
> create mode 100644 include/soc/at91/atmel_tcb.h
>
> diff --git a/include/soc/at91/atmel_tcb.h b/include/soc/at91/atmel_tcb.h
> new file mode 100644
> index 000000000000..3ed66031fc76
> --- /dev/null
[ ... ]
> +static inline struct clk *tcb_clk_get(struct device_node *node, int channel)
> +{
> + struct clk *clk;
> + char clk_name[] = "t0_clk";
> +
> + clk_name[1] += channel;
clever :)
> + clk = of_clk_get_by_name(node->parent, clk_name);
> + if (!IS_ERR(clk))
> + return clk;
> +
> + return of_clk_get_by_name(node->parent, "t0_clk");
Why do you want to return clk from t0_clk if another channel is
requested ? This is prone to error.
I would clarify that at the caller level, if tcb_clk_get fails then try
with channel zero.
> +}
> +
> +static inline int tcb_irq_get(struct device_node *node, int channel)
no inline
> +{
> + int irq;
> +
> + irq = of_irq_get(node->parent, channel);
> + if (irq > 0)
> + return irq;
> +
> + return of_irq_get(node->parent, 0);
Same comment than above.
> +}
> +
> +static const u8 atmel_tc_divisors[5] = { 2, 8, 32, 128, 0, };
> +
> +struct atmel_tcb_info {
> + int bits;
> +};
> +
> +static const struct atmel_tcb_info atmel_tcb_infos[] = {
> + { .bits = 16 },
> + { .bits = 32 },
> +};
Structuring the code with structure is a good practice. However, this is
too much :)
> +static const struct of_device_id atmel_tcb_dt_ids[] = {
> + {
> + .compatible = "atmel,at91rm9200-tcb",
> + .data = &atmel_tcb_infos[0],
.data = (void *)16;
> + }, {
> + .compatible = "atmel,at91sam9x5-tcb",
> + .data = &atmel_tcb_infos[1],
> + }, {
> + /* sentinel */
> + }
> +};
> +
> +#endif /* __SOC_ATMEL_TCB_H */
>
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2018-06-28 15:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 21:19 [PATCH v5 0/6] clocksource: rework Atmel TCB timer driver Alexandre Belloni
2018-06-19 21:19 ` [PATCH v5 1/6] ARM: at91: add TCB registers definitions Alexandre Belloni
2018-06-28 15:15 ` Daniel Lezcano [this message]
2018-06-28 18:34 ` Alexandre Belloni
2018-06-28 19:55 ` Daniel Lezcano
2018-06-19 21:19 ` [PATCH v5 2/6] clocksource/drivers: Add a new driver for the Atmel ARM TC blocks Alexandre Belloni
2018-06-20 9:03 ` Thomas Gleixner
2018-06-20 9:46 ` Alexandre Belloni
2018-06-20 10:07 ` Thomas Gleixner
2018-06-20 10:32 ` Alexandre Belloni
2018-06-20 10:58 ` Thomas Gleixner
2018-06-20 11:18 ` Alexandre Belloni
2018-06-20 11:55 ` Thomas Gleixner
2018-06-28 16:24 ` Daniel Lezcano
2018-07-06 15:18 ` Alexandre Belloni
2018-06-19 21:19 ` [PATCH v5 3/6] clocksource/drivers: atmel-pit: make option silent Alexandre Belloni
2018-06-19 21:19 ` [PATCH v5 4/6] ARM: at91: Implement clocksource selection Alexandre Belloni
2018-06-19 21:19 ` [PATCH v5 5/6] ARM: configs: at91: use new TCB timer driver Alexandre Belloni
2018-06-19 21:19 ` [PATCH v5 6/6] ARM: configs: at91: unselect PIT Alexandre Belloni
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=1bc64ccb-1e22-364c-e08c-fa86692783ff@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).