From: "Haavard Skinnemoen" <haavard.skinnemoen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [RFC/PATCH] SPI API improvements
Date: Sun, 11 May 2008 22:56:55 +0200 [thread overview]
Message-ID: <48275D97.7020204@atmel.com> (raw)
In-Reply-To: <200805091722.41084.vapier@gentoo.org>
Mike Frysinger wrote:
> On Friday 09 May 2008, Haavard Skinnemoen wrote:
>> This patch hasn't been tested on all the boards involved, so there are
>> probably a few issues. For now, I'd like some comments on the new
>> interface -- if it looks good, we should spend some additional effort
>> to validate that it doesn't introduce any breakage. I could use some
>> help with this.
>
> just a quick glance, but do we care about U-Boot being a SPI slave ? i only
> noticed this as i was working on the Blackfin I2C driver recently and
> realized that the I2C framework has defines for U-Boot to act as a slave.
> not that the Blackfin driver even has any of the slave stuff implemented, i
> just noticed it ;).
I can't see much reason to add support for U-Boot acting as a SPI slave,
and these patches certainly doesn't attempt to make that happen. If
you're thinking of the new "struct spi_slave", that's a reference to the
SPI slave we're talking to, i.e. whatever sits at the other end of the
SPI bus.
If someone else wants support for slave-mode SPI, maybe we should add
it, but that should be an entirely separate set of patches.
Haavard
next prev parent reply other threads:[~2008-05-11 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 15:21 [U-Boot-Users] [RFC/PATCH] SPI API improvements Haavard Skinnemoen
2008-05-09 15:21 ` [U-Boot-Users] [RFC/PATCH] atmel_spi: Driver for the Atmel SPI controller Haavard Skinnemoen
2008-05-09 21:22 ` [U-Boot-Users] [RFC/PATCH] SPI API improvements Mike Frysinger
2008-05-11 20:56 ` Haavard Skinnemoen [this message]
2008-05-11 21:57 ` Mike Frysinger
2008-05-13 11:20 ` Guennadi Liakhovetski
2008-05-13 13:50 ` Haavard Skinnemoen
2008-05-13 15:06 ` Guennadi Liakhovetski
2008-05-13 16:00 ` Haavard Skinnemoen
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=48275D97.7020204@atmel.com \
--to=haavard.skinnemoen@atmel.com \
--cc=u-boot@lists.denx.de \
/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