From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 02/10] S3C64XX I2S: declared i2s_v4
Date: Wed, 16 Sep 2009 01:12:20 +0100 [thread overview]
Message-ID: <20090916001220.GC24720@trinity.fluff.org> (raw)
In-Reply-To: <1253008954-10473-1-git-send-email-jassi.brar@samsung.com>
On Tue, Sep 15, 2009 at 07:02:34PM +0900, Jassi wrote:
> For now, I2S-v4 is simply enumerated as third I2S controller of S3C6410
> rather than a special device.
> Also, Declared I2S-v4 device for SMDK6410.
>
> Signed-Off-by: Jassi <jassi.brar@samsung.com>
> ---
> arch/arm/mach-s3c6410/mach-smdk6410.c | 1 +
> arch/arm/plat-s3c/dev-audio.c | 6 ++++--
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-s3c6410/mach-smdk6410.c b/arch/arm/mach-s3c6410/mach-smdk6410.c
> index bc9a7de..108ba37 100644
> --- a/arch/arm/mach-s3c6410/mach-smdk6410.c
> +++ b/arch/arm/mach-s3c6410/mach-smdk6410.c
> @@ -181,6 +181,7 @@ static struct platform_device *smdk6410_devices[] __initdata = {
> #endif
> &s3c_device_i2c0,
> &s3c_device_i2c1,
> + &s3c64xx_device_iisv4,
> &s3c_device_fb,
> &s3c_device_usb,
> &s3c_device_usb_hsotg,
> diff --git a/arch/arm/plat-s3c/dev-audio.c b/arch/arm/plat-s3c/dev-audio.c
> index 1322beb..28c030c 100644
> --- a/arch/arm/plat-s3c/dev-audio.c
> +++ b/arch/arm/plat-s3c/dev-audio.c
> @@ -51,6 +51,7 @@ struct platform_device s3c64xx_device_iis1 = {
> };
> EXPORT_SYMBOL(s3c64xx_device_iis1);
>
> +#ifdef CONFIG_CPU_S3C6410
> static struct resource s3c64xx_iisv4_resource[] = {
> [0] = {
> .start = S3C64XX_PA_IISV4,
> @@ -60,9 +61,10 @@ static struct resource s3c64xx_iisv4_resource[] = {
> };
>
> struct platform_device s3c64xx_device_iisv4 = {
> - .name = "s3c64xx-iis-v4",
> - .id = -1,
> + .name = "s3c64xx-iis",
> + .id = 2,
I'd like to see how much different the two drivers are, and whether they
need to be seperated into their own modules.
Changing the name to s3c64xx-iis means that the module auto-load may end
up loading the wrong module. Holding off on this change until we se what
needs to be done for this block.
> .num_resources = ARRAY_SIZE(s3c64xx_iisv4_resource),
> .resource = s3c64xx_iisv4_resource,
> };
> EXPORT_SYMBOL(s3c64xx_device_iisv4);
> +#endif
> --
> 1.6.2.5
>
--
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2009-09-16 0:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 10:02 [PATCH 02/10] S3C64XX I2S: declared i2s_v4 Jassi
2009-09-16 0:12 ` Ben Dooks [this message]
2009-09-16 0:56 ` jassi brar
2009-09-16 10:22 ` Mark Brown
2009-09-16 18:49 ` 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=20090916001220.GC24720@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.