From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Ryan Mallon <ryan@bluewatersys.com>
Cc: Julia Lawall <julia@diku.dk>, Vasiliy Kulikov <segooon@gmail.com>,
kernel-janitors@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Andrew Victor <linux@maxim.org.za>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] arch/arm/mach-at91/clock.c: Add missing IS_ERR test
Date: Mon, 24 Jan 2011 23:23:02 +0000 [thread overview]
Message-ID: <20110124232302.GQ24104@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4D3DF46A.1030009@bluewatersys.com>
On Tue, Jan 25, 2011 at 10:51:38AM +1300, Ryan Mallon wrote:
> You could, but it would not be helpful. Clock associations are used so
> that _different_ devices can have the same function and map to the
> correct clock. This is used when there are multiple instances of a
> single peripheral. For example, the uart clocks work like this:
>
> at91_clock_associate("usart1_clk", &pdev->dev, "usart");
>
> so then you can do this in a driver:
>
> uart_clk = clk_get(&pdev->dev, "usart");
>
> Rather than:
>
> uart_clk = clk_get(NULL, "usart1_clk");
>
> The former will find the correct uart clock for the device. Because each
> uart is a separate device the correct clock will be selected for each uart.
>
> My point was that there should be no overlap between clk->name and
> clk->function otherwise clk_get will not be able to return the correct
> clock.
It would be nice if AT91 could switch over to using clkdev at some
point, which greatly helps with associating struct clk's with their
device/function names - and reduces the amount of "different" code.
You can then use clk_add_alias() to create aliases of an existing
clock.
Looking at your clk_get(), I think one way to do this would be, in
clk_register():
struct clk_lookup *cl;
/* create function-only entry */
cl = clkdev_alloc(clk, clk->name, NULL);
if (!cl)
return -ENOMEM;
clkdev_add(cl);
/* not sure if you need this? */
if (clk->dev && clk->function) {
cl = clkdev_alloc(clk, clk->function, "%s", dev_name(clk->dev));
if (!cl)
return -ENOMEM;
clkdev_add(cl);
}
at91_clock_associate() becomes:
err = clk_add_alias(func, dev_name(dev), id, NULL);
return err;
Although maybe in the long run see about removing at91_clock_associate()
entirely as its just a wrapper.
The only requirement there is that 'dev' in each case is a registered
device, otherwise dev_name() won't work.
You can then use the generic clk_get()/clk_put() which clkdev provides.
next prev parent reply other threads:[~2011-01-24 23:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 19:55 [PATCH 0/4] " Julia Lawall
2011-01-24 19:55 ` [PATCH 1/4] fs/btrfs/inode.c: " Julia Lawall
2011-01-24 19:55 ` [PATCH 2/4] arch/arm/mach-at91/clock.c: " Julia Lawall
2011-01-24 19:56 ` Ryan Mallon
2011-01-24 20:00 ` Julia Lawall
2011-01-24 20:05 ` Vasiliy Kulikov
2011-01-24 20:09 ` Julia Lawall
2011-01-24 20:14 ` Vasiliy Kulikov
2011-01-25 10:33 ` walter harms
2011-01-25 10:43 ` Russell King - ARM Linux
2011-01-25 11:12 ` walter harms
2011-01-25 11:17 ` Russell King - ARM Linux
2011-01-25 11:18 ` Julia Lawall
2011-01-25 11:26 ` Russell King - ARM Linux
2011-01-25 11:31 ` Julia Lawall
2011-01-24 20:11 ` Ryan Mallon
2011-01-24 20:28 ` Julia Lawall
2011-01-24 20:38 ` Ryan Mallon
2011-01-24 21:01 ` Julia Lawall
2011-01-24 21:06 ` Ryan Mallon
2011-01-24 21:31 ` Julia Lawall
2011-01-24 21:51 ` Ryan Mallon
2011-01-24 23:23 ` Russell King - ARM Linux [this message]
2011-01-25 1:44 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-25 6:12 ` Julia Lawall
2011-01-25 17:23 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-24 19:55 ` [PATCH 3/4] drivers/video/bf537-lq035.c: " Julia Lawall
2011-01-24 20:43 ` Mike Frysinger
2011-01-25 6:12 ` Paul Mundt
2011-01-25 8:36 ` Hennerich, Michael
2011-01-24 19:55 ` [PATCH 4/4] arch/arm/mach-omap2/smartreflex.c: " Julia Lawall
2011-01-24 21:24 ` Kevin Hilman
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=20110124232302.GQ24104@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
--cc=ryan@bluewatersys.com \
--cc=segooon@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®