From: David Brownell <david-b@pacbell.net>
To: Mark Brown <broonie@sirena.org.uk>
Cc: "Stanley.Miao" <stanley.miao@windriver.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Jarkko Nikula <jarkko.nikula@nokia.com>
Subject: Re: [PATCH] OMAP general SOC driver.
Date: Wed, 26 Nov 2008 14:03:18 -0800 [thread overview]
Message-ID: <200811261403.18464.david-b@pacbell.net> (raw)
In-Reply-To: <20081126211614.GA6514@sirena.org.uk>
On Wednesday 26 November 2008, Mark Brown wrote:
> > I wonder if
> > it shouldn't suffice just to provide a mask of capabilities
> > that are wired up on a given board.
>
> It's possible - if the differences can be handled by marking some pins
> as connected or disconnected and possible specifying a different system
> clock rate to the chip then that approach was what I was expecting.
> If there is more substantial differences such as having the clocking
> arranged differently then separate drivers start to make more sense.
OK, from my non-expert perspective it sounds eminently do-able.
By someone else. :)
next prev parent reply other threads:[~2008-11-26 22:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 10:47 [PATCH] OMAP general SOC driver Stanley.Miao
2008-11-26 11:08 ` Mark Brown
2008-11-26 11:40 ` Jarkko Nikula
2008-11-26 18:34 ` David Brownell
2008-11-26 20:07 ` Mark Brown
2008-11-26 20:20 ` Koen Kooi
2008-11-27 5:01 ` Arun KS
[not found] ` <6ed0b2680811270242i1b857f13i9494826f6089bf15@mail.gmail.com>
2008-11-27 12:36 ` Mark Brown
2008-11-26 20:33 ` David Brownell
2008-11-26 21:16 ` Mark Brown
2008-11-26 22:03 ` David Brownell [this message]
2008-11-27 12:39 ` stanley.miao
2008-11-26 20:44 ` David Brownell
2008-11-26 21:22 ` Mark Brown
2008-11-26 17:24 ` Steve Sakoman
2008-11-26 17:29 ` [alsa-devel] " Mark Brown
2008-11-26 15:53 ` 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=200811261403.18464.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@sirena.org.uk \
--cc=jarkko.nikula@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=stanley.miao@windriver.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.