From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/7] S3C64XX: Declare IISv4 PCLK for S3C6410
Date: Tue, 1 Dec 2009 21:42:01 +0000 [thread overview]
Message-ID: <20091201214201.GP4808@trinity.fluff.org> (raw)
In-Reply-To: <1259340239-12067-4-git-send-email-broonie@opensource.wolfsonmicro.com>
On Fri, Nov 27, 2009 at 04:43:56PM +0000, Mark Brown wrote:
> From: Jassi <jassi.brar@samsung.com>
>
> [Updated the device ID to -1 since there's only one IISv4 device but the
> S3C clock API tries to match based on the ID of the requesting device
> (and not the name) -- broonie.]
I had a quick look at the other clock changes and there are a couple
of questions that have come up:
1) If changing the .id field of the iisv4 device really a good idea,
especially if there might be more than one of them in the future?
2) The clock name for the current audio bus clock for the iisv4 unit
is wrong as we're using it for both the iis and iisv4 blocks. It
might be worth renaming the clock for the iisv4 audio bus before
looking at changing the usage of the clock support (once the current
changes have been sorted)
As such is the #ifdef of the clock code when the S3C6410 support
really necesary?
> Signed-Off-by: Jassi <jassi.brar@samsung.com>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> arch/arm/plat-s3c64xx/clock.c | 8 ++++++++
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/plat-s3c64xx/clock.c b/arch/arm/plat-s3c64xx/clock.c
> index 7a36e89..2f1548e 100644
> --- a/arch/arm/plat-s3c64xx/clock.c
> +++ b/arch/arm/plat-s3c64xx/clock.c
> @@ -129,6 +129,14 @@ static struct clk init_clocks_disable[] = {
> .enable = s3c64xx_pclk_ctrl,
> .ctrlbit = S3C_CLKCON_PCLK_IIS1,
> }, {
> +#ifdef CONFIG_CPU_S3C6410
> + .name = "iis",
> + .id = -1, /* There's only one IISv4 port */
> + .parent = &clk_p,
> + .enable = s3c64xx_pclk_ctrl,
> + .ctrlbit = S3C6410_CLKCON_PCLK_IIS2,
> + }, {
> +#endif
> .name = "spi",
> .id = 0,
> .parent = &clk_p,
> --
> 1.6.5.3
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2009-12-01 21:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 16:43 [PATCH 0/7] S3C64XX IISv4 support Mark Brown
2009-11-27 16:43 ` [PATCH 1/7] S3C64XX: Staticise platform data for PCM devices Mark Brown
2009-11-28 1:40 ` jassi brar
2009-12-01 18:08 ` Ben Dooks
2009-12-02 0:22 ` jassi brar
2009-12-03 22:01 ` Ben Dooks
2009-12-03 22:57 ` Mark Brown
2009-11-27 16:43 ` [PATCH 2/7] S3C6410: Correct names of IISv4 data output pin definitions Mark Brown
2009-12-01 18:16 ` Ben Dooks
2009-11-27 16:43 ` [PATCH 3/7] S3C64XX: Add support for CLK_SRC2 configured clocks Mark Brown
2009-11-28 1:46 ` jassi brar
2009-12-01 18:17 ` Ben Dooks
2009-11-27 16:43 ` [PATCH 4/7] S3C64XX: Declare IISv4 PCLK for S3C6410 Mark Brown
2009-12-01 21:42 ` Ben Dooks [this message]
2009-12-02 0:50 ` jassi brar
2009-12-02 12:10 ` Mark Brown
2009-12-04 13:17 ` jassi brar
2009-12-02 11:20 ` Mark Brown
2009-11-27 16:43 ` [PATCH 5/7] S3C6410: Define CLK_AUDIO2 for IISv4 block Mark Brown
2009-11-27 16:43 ` [PATCH 6/7] S3C6410: Use platform data to supply pin configuration for IISv4 Mark Brown
2009-11-28 1:31 ` jassi brar
2009-12-01 18:24 ` Ben Dooks
2009-11-27 16:43 ` [PATCH 7/7] SMDK6410: Register IISv4 device Mark Brown
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=20091201214201.GP4808@trinity.fluff.org \
--to=ben-linux@fluff.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).