mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Carlo Caione <carlo.caione@gmail.com>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH 4/5] BCM2835: add support (arch)
Date: Thu, 18 Oct 2012 00:27:14 +0200	[thread overview]
Message-ID: <7273C8F9-F3BD-4606-8C35-B370AA04C98C@gmail.com> (raw)
In-Reply-To: <20121016212416.GC27665@pengutronix.de>


On Oct 16, 2012, at 11:24 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:

> On Tue, Oct 16, 2012 at 08:04:44PM +0200, Carlo Caione wrote:
>> +
>> +static struct clk ref_3_clk = {
>> +	.rate = 3 * 1000 * 1000,
>> +};
>> +
>> +static struct clk ref_1_clk = {
>> +	.rate = 1 * 1000 * 1000,
>> +};
> 
> Add a 'select COMMON_CLK' to your Kconfig and do a:
> 
> 	clk_dummy = clk_fixed("dummy", 0);
> 	clk_ref_3 = clk_fixed("ref3", 3 * 1000 * 1000);
> 	clk_ref_1 = clk_fixed("ref1", 1 * 1000 * 1000);
> 
> Then you can drop your clk code and get a clk_dump command
> which you can use to see what clocks you have.

RFC

ok I ask here before submitting the whole set because I'm not sure if this is a convenient solution.
I'm not sure if you are suggesting to have two different clock definition one for clk_fixed and the other one for clkdev,
so I was thinking something like:

enum brcm_clks {
	dummy, clk_ref_3, clk_ref_1, clks_max
};

static struct clk *clks[clks_max];

int brmc_clk_create(struct clk *clk, const char *con_id, const char *dev_id)
{
	struct clk_lookup *clkdev;

	clkdev = clkdev_alloc(clk, con_id, dev_id);
	if (!clkdev)
		return -ENOMEM;
	clkdev_add(clkdev);
	return 0;
}

static int bcm2835_clk_init(void)
{
	int ret; 

	clks[dummy] = clk_fixed("dummy", 0);
	ret = brmc_clk_create(clks[dummy], "apb_pclk", NULL);
	if (ret)
		goto clk_err;

	clks[clk_ref_3] = clk_fixed("ref3", 3 * 1000 * 1000);
	ret = brmc_clk_create(clks[clk_ref_3], NULL, "uart0-pl0110");
	if (ret)
		goto clk_err;

	clks[clk_ref_1] = clk_fixed("ref1", 1 * 1000 * 1000);
	ret = brmc_clk_create(clks[clk_ref_1], NULL, "bcm2835-cs");
	if (ret)
		goto clk_err;

	return 0;

clk_err:
	return ret;

}
postcore_initcall(bcm2835_clk_init);

Any comment on this solution?

--
Carlo Caione
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2012-10-17 22:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 18:04 [PATCH 0/5] BCM2835/Raspberry-Pi support Carlo Caione
2012-10-16 18:04 ` [PATCH 1/5] BCM2835: add clocksource driver Carlo Caione
2012-10-16 18:04 ` [PATCH 2/5] BCM2835: add gpio driver Carlo Caione
2012-10-16 21:09   ` Sascha Hauer
2012-10-16 18:04 ` [PATCH 3/5] ARM1176: add support Carlo Caione
2012-10-16 18:04 ` [PATCH 4/5] BCM2835: add support (arch) Carlo Caione
2012-10-16 21:24   ` Sascha Hauer
2012-10-17  6:51     ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-17  7:01       ` Sascha Hauer
2012-10-17  7:25         ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-17  8:31           ` Carlo Caione
2012-10-17 21:00             ` Sascha Hauer
2012-10-17 22:27     ` Carlo Caione [this message]
2012-10-18  7:02       ` Sascha Hauer
2012-10-16 18:04 ` [PATCH 5/5] Raspberry-Pi: add support (board) Carlo Caione
  -- strict thread matches above, loose matches on Subject: below --
2012-10-18 19:42 [PATCH 0/5] BCM2835/Raspberry-Pi support Carlo Caione
2012-10-18 19:42 ` [PATCH 4/5] BCM2835: add support (arch) Carlo Caione
2012-10-13 14:00 [PATCH 0/5] BCM2835/Raspberry-Pi support Carlo Caione
2012-10-13 14:00 ` [PATCH 4/5] BCM2835: add support (arch) Carlo Caione
2012-10-13 11:22 [PATCH 0/5] BCM2835/Raspberry-Pi Carlo Caione
2012-10-13 11:23 ` [PATCH 4/5] BCM2835: add support (arch) Carlo Caione

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=7273C8F9-F3BD-4606-8C35-B370AA04C98C@gmail.com \
    --to=carlo.caione@gmail.com \
    --cc=barebox@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