From: Ben Dooks <ben-linux@fluff.org>
To: JASWINDERSINGH BRAR <jassi.brar@samsung.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>,
SeungHyun Choi <sh428.choi@samsung.com>,
"graeme.gregory@wolfsonmicro.com"
<graeme.gregory@wolfsonmicro.com>,
"ben-linux@fluff.org" <ben-linux@fluff.org>
Subject: Re: Reforming s3c2443 ac97 driver
Date: Fri, 8 Jan 2010 05:53:14 +0000 [thread overview]
Message-ID: <20100108055314.GE24370@trinity.fluff.org> (raw)
In-Reply-To: <29946650.33531262928531169.JavaMail.weblogic@epml17>
On Fri, Jan 08, 2010 at 05:28:51AM +0000, JASWINDERSINGH BRAR wrote:
> Hi,
> Right now the S3C2443's AC97_ver2.0 controller driver isn't flexible enough
> to handle newer SoCs.
> In order to prepare ground for supporting 64xx and S5Pxxxx the extant driver
> needs to be reformed, and that is what i am planning to do next.
>
> I plan to do the following:-
> 1) User platform_driver structure to detect and manage AC97 controller
> platform devices.
> 2) Remove hardcoded parameters(DMA, IO address, IRQ etc) and pass via
> platform resources.
> 3) Initialize platform specific stuff by callback pointers to platform code(cfg_gpio)
>
> Objections, suggestions welcome.
None from here, although it isn't really my driver in the first place.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2010-01-08 5:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 5:28 Reforming s3c2443 ac97 driver JASWINDERSINGH BRAR
2010-01-08 5:53 ` Ben Dooks [this message]
2010-01-08 9:48 ` Mark Brown
2010-01-21 6:58 ` jassi brar
2010-01-21 10:03 ` Mark Brown
2010-01-21 10:37 ` Liam Girdwood
2010-01-21 11:22 ` jassi brar
2010-01-21 11:30 ` Mark Brown
2010-01-21 11:34 ` jassi brar
[not found] <0KWM003YNI0X6D@ms11.samsung.com>
2010-01-22 1:03 ` jassi brar
2010-01-22 1:04 ` Ben Dooks
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=20100108055314.GE24370@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=graeme.gregory@wolfsonmicro.com \
--cc=jassi.brar@samsung.com \
--cc=sh428.choi@samsung.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 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.