From: Tony Lindgren <tony@atomide.com>
To: Hugo Vincent <hugo.vincent@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP3 Overo: add EXPORT_SYMBOLs for Overo ASoC audio to be built as a module.
Date: Tue, 2 Jun 2009 10:35:43 -0700 [thread overview]
Message-ID: <20090602173543.GE27332@atomide.com> (raw)
In-Reply-To: <5a7b8b7b0906011802y4abc5ba6m8813d6884825e805@mail.gmail.com>
* Hugo Vincent <hugo.vincent@gmail.com> [090601 18:03]:
> I'm pretty new to kernel development, so I don't know any potential
> problems with doing this, but without this, audio/ASoC support must be
> built into the kernel (modpost fails when trying to build as modules),
> whereas with this patch, it can be built and used as a module.
>
> Comments?
To me it looks like we should rather fix sound/soc/omap/omap-mcbsp.c
to use the clock framework rather than access omap_ctrl_read/write
directly.
Tony
> diff --git a/arch/arm/mach-omap2/control.c b/arch/arm/mach-omap2/control.c
> index 5f3aad9..aa3d123 100644
> --- a/arch/arm/mach-omap2/control.c
> +++ b/arch/arm/mach-omap2/control.c
> @@ -46,6 +46,7 @@ u32 omap_ctrl_readl(u16 offset)
> {
> return __raw_readl(OMAP_CTRL_REGADDR(offset));
> }
> +EXPORT_SYMBOL(omap_ctrl_readl);
>
> void omap_ctrl_writeb(u8 val, u16 offset)
> {
> @@ -61,4 +62,5 @@ void omap_ctrl_writel(u32 val, u16 offset)
> {
> __raw_writel(val, OMAP_CTRL_REGADDR(offset));
> }
> +EXPORT_SYMBOL(omap_ctrl_writel);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-02 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 1:02 [PATCH] OMAP3 Overo: add EXPORT_SYMBOLs for Overo ASoC audio to be built as a module Hugo Vincent
2009-06-02 17:35 ` Tony Lindgren [this message]
2009-06-03 13:20 ` Jarkko Nikula
2009-06-03 16:31 ` Tony Lindgren
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=20090602173543.GE27332@atomide.com \
--to=tony@atomide.com \
--cc=hugo.vincent@gmail.com \
--cc=linux-omap@vger.kernel.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.