From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] SPI S3C64XX: Header for passing platform data
Date: Wed, 9 Dec 2009 12:16:43 +0000 [thread overview]
Message-ID: <20091209121643.GD9018@sirena.org.uk> (raw)
In-Reply-To: <1b68c6790912081750r7a68f019w39a5170c9796e7b9@mail.gmail.com>
On Wed, Dec 09, 2009 at 10:50:16AM +0900, jassi brar wrote:
> Second - SPI source clocks specific, which SoCs differ by name and number.
> Maybe this could go into plat-<soc>/include with the name
> <soc>-spi.h
With device based lookup (which Ben mentioned he was working on) this
mapping should get handled entirely within the CPU clock tree
definition and be invisible to the driver.
next prev parent reply other threads:[~2009-12-09 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 6:48 [PATCH 3/5] SPI S3C64XX: Header for passing platform data Jassi Brar
2009-12-03 22:06 ` Ben Dooks
2009-12-04 11:06 ` jassi brar
2009-12-07 14:41 ` Ben Dooks
2009-12-09 1:50 ` jassi brar
2009-12-09 12:16 ` Mark Brown [this message]
2009-12-09 12:31 ` jassi brar
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=20091209121643.GD9018@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--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).