From: "Masayuki Ohtake" <masa-korg@dsn.okisemi.com>
To: "Grant Likely" <grant.likely@secretlab.ca>,
"Thomas Gleixner" <tglx@linutronix.de>
Cc: <meego-dev@meego.com>, "LKML" <linux-kernel@vger.kernel.org>,
"David Brownell" <dbrownell@users.sourceforge.net>,
<qi.wang@intel.com>, <yong.y.wang@intel.com>,
<andrew.chih.howe.khor@intel.com>, <arjan@linux.intel.com>,
<gregkh@suse.de>, "Tomoya MORINAGA" <morinaga526@dsn.okisemi.com>,
"David Woodhouse" <dwmw2@infradead.org>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_SPI driver to 2.6.35
Date: Mon, 30 Aug 2010 16:28:41 +0900 [thread overview]
Message-ID: <001401cb4814$fb4bdd70$66f8800a@maildom.okisemi.com> (raw)
In-Reply-To: AANLkTimsPE2dpVdTNZXR-Yx0fX93Wk_vQDpFJc4xSaTX@mail.gmail.com
----- Original Message -----
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Thomas Gleixner" <tglx@linutronix.de>
Cc: "Masayuki Ohtak" <masa-korg@dsn.okisemi.com>; <meego-dev@meego.com>; "LKML" <linux-kernel@vger.kernel.org>; "David
Brownell" <dbrownell@users.sourceforge.net>; <qi.wang@intel.com>; <yong.y.wang@intel.com>;
<andrew.chih.howe.khor@intel.com>; <arjan@linux.intel.com>; <gregkh@suse.de>; "Tomoya MORINAGA"
<morinaga526@dsn.okisemi.com>; "David Woodhouse" <dwmw2@infradead.org>; "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Sent: Saturday, August 28, 2010 4:20 AM
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_SPI driver to 2.6.35
> On Fri, Aug 27, 2010 at 12:53 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> > B1;2401;0cOn Fri, 27 Aug 2010, Grant Likely wrote:
> >> [cc'ing Thomas Gleixner and David Woodhouse since this driver needs to
> >> get some data about the platform (to know what spi_devices are
> >> present) and I don't know how that is handled for x86 SoCs.]
> >
> > The best way to do all this platform specific configuration is to use
> > device tree. I really don't want to have x86/mach-xyz/board[A-Z]
> > horror, which is unavoidable when we don't get a sensible way to
> > configure the boards.
>
> I knew you were going to say that! :-)
>
> Ohtak-san, for this patch I'd like you to drop the separate driver
> that only registers the spi_devices and just submit the core driver.
Sorry, I can't follow your discussion by lack of SPI knowledge.
Which the above mean that "spi_register_board_info" moves to our spi_pch or
delete for our driver ?
> (You can of course keep the spi_device registration in your own tree
> for debug purposes). I'll expect that the device will get
> instantiated using a device tree to determine which spi_devices are
> present. The parsing of spi device tree data will be moving into the
> core spi subsystem code in the next merge window most likely, so it
> can all be handled transparently.
>
> > SFI was meant to provide a lightweight ACPI, but
> > now that device tree is generic and more platforms are using it, I
> > really want to standartize on that and forget SFI.
> >
> > That makes even more sense, as all these AMBA peripherals which are
> > duct-taped to a x86 core can be found in other SoCs with different
> > cores as well.
>
> Indeed. BTW, Ohtak-san, is this spi bus device something brand new,
> or is it derived from an existing spi device?
Yes, Intel Topcliff is new concept device.
Thanks, Ohtake(OKISEMI)
next prev parent reply other threads:[~2010-08-30 7:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C77BD91.9070302@dsn.okisemi.com>
2010-08-27 18:33 ` [MeeGo-Dev][PATCH] Topcliff: Update PCH_SPI driver to 2.6.35 Grant Likely
2010-08-27 18:53 ` Thomas Gleixner
2010-08-27 18:54 ` Arjan van de Ven
2010-08-27 19:06 ` Thomas Gleixner
2010-08-27 19:20 ` Grant Likely
2010-08-30 7:28 ` Masayuki Ohtake [this message]
2010-08-30 12:44 ` Thomas Gleixner
2010-08-31 1:05 ` Masayuki Ohtake
2010-08-31 5:51 ` Grant Likely
2010-08-31 6:24 ` Masayuki Ohtake
2010-08-30 18:23 ` Grant Likely
2010-08-31 1:45 ` Masayuki Ohtake
2010-08-31 6:03 ` Grant Likely
2010-08-31 6:47 ` Masayuki Ohtake
2010-08-31 6:53 ` Grant Likely
2010-08-31 6:57 ` Masayuki Ohtake
2010-08-31 12:09 ` Masayuki Ohtake
2010-09-06 11:09 Masayuki Ohtak
2010-09-10 6:03 ` Grant Likely
[not found] <4C80E2D5.1020104@dsn.okisemi.com>
2010-09-03 14:46 ` Grant Likely
2010-09-03 17:50 ` Linus Walleij
2010-09-03 17:57 ` Grant Likely
2010-09-06 6:19 ` Masayuki Ohtake
2010-09-08 19:40 ` Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2010-09-03 5:50 Masayuki Ohtake
2010-09-09 20:58 ` Linus Walleij
2010-09-10 0:27 ` Masayuki Ohtake
2010-09-10 1:30 ` Joe Perches
2010-09-10 1:41 ` Grant Likely
2010-09-10 2:05 ` Grant Likely
2010-09-10 4:55 ` Grant Likely
2010-09-14 2:52 ` Tomoya MORINAGA
2010-09-14 2:56 ` Grant Likely
[not found] <4C6131C2.4080101@dsn.okisemi.com>
2010-08-10 17:10 ` Greg KH
2010-08-11 1:25 ` Wang, Qi
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='001401cb4814$fb4bdd70$66f8800a@maildom.okisemi.com' \
--to=masa-korg@dsn.okisemi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrew.chih.howe.khor@intel.com \
--cc=arjan@linux.intel.com \
--cc=dbrownell@users.sourceforge.net \
--cc=dwmw2@infradead.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=meego-dev@meego.com \
--cc=morinaga526@dsn.okisemi.com \
--cc=qi.wang@intel.com \
--cc=tglx@linutronix.de \
--cc=yong.y.wang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox