From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] ARM: MX3: add SPI devices for mx31lite
Date: Thu, 19 Nov 2009 10:24:55 +0100 [thread overview]
Message-ID: <20091119092455.GF29442@buzzloop.caiaq.de> (raw)
In-Reply-To: <20091119083825.GO30179@pengutronix.de>
On Thu, Nov 19, 2009 at 09:38:25AM +0100, Sascha Hauer wrote:
> On Wed, Nov 18, 2009 at 04:42:56PM +0100, Daniel Mack wrote:
> > On Wed, Nov 18, 2009 at 04:37:08PM +0100, Sascha Hauer wrote:
> > > On Wed, Nov 18, 2009 at 02:41:40PM +0100, Daniel Mack wrote:
> > > > /*
> > > > + * SPI
> > > > + *
> > > > + * The MX13783 is hard-wired on the module, hence the corresponding
> > > > + * bus is registered here and not in the board code, in contrast to
> > > > + * the other SPI bus.
> > > > + */
> > >
> > >
> > > The mc13783 bus is registered in the -db file, and not here. I think you
> > > mixed something up here.
> >
> > Hmm, no, that actually correct. The problem is that all devices on the
> > SPI bus have to be registered in one block via spi_register_board_info,
>
> Looking at the SPI code I see no reason why it shouldn't be possible to call
> spi_register_board_info multiple times.
Hmm ok, I didn't know that. I changed that and rebased the patches on
top of this. I'll resend the whole series later.
Thanks,
Daniel
prev parent reply other threads:[~2009-11-19 9:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 13:41 [PATCH 1/5] ARN: MX3: modularize 'mx31lite' code Daniel Mack
2009-11-18 13:41 ` [PATCH 2/5] ARM: MX3: add MMC/SDHC support to mx31lite-db.c Daniel Mack
2009-11-18 13:41 ` [PATCH 3/5] ARM: MX3: add SPI devices for mx31lite Daniel Mack
2009-11-18 13:41 ` [PATCH 4/5] ARM: MX3: add USB functions for mx31litekit Daniel Mack
2009-11-18 13:41 ` [PATCH 5/5] ARM: MX3: add support for GPIO LEDs on litekit db Daniel Mack
2009-11-18 15:37 ` [PATCH 3/5] ARM: MX3: add SPI devices for mx31lite Sascha Hauer
2009-11-18 15:42 ` Daniel Mack
2009-11-19 8:38 ` Sascha Hauer
2009-11-19 9:24 ` Daniel Mack [this message]
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=20091119092455.GF29442@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--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).