From: "Steven A. Falco" <sfalco@harris.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Stefan Roese <sr@denx.de>
Subject: Re: Subject: [PATCH v7] spi: Add PPC4xx SPI driver
Date: Fri, 26 Jun 2009 12:17:34 -0400 [thread overview]
Message-ID: <4A44F49E.3030003@harris.com> (raw)
In-Reply-To: <200906252104.46189.david-b@pacbell.net>
David Brownell wrote:
> On Thursday 25 June 2009, Steven A. Falco wrote:
>> + if (spi->mode & ~MODEBITS) {
>> + dev_dbg(&spi->dev, "setup: unsupported mode bits %x\n",
>> + spi->mode & ~MODEBITS);
>> + return -EINVAL;
>> + }
>
> This wasn't tested against 2.6.30-rc1 was it?
>
I tested against Ben's "next" branch, plus your fix for bitbang_work.
But the new version I'll post is tested against Linus' master branch
(2.6.31-rc1) to take advantage of your mode_bits addition. If you need
this driver to be based on something else, please say so.
> See the recent fixup patch I sent. There's a spi_master->modebits
> mask that should have been initialized, and which eliminates the
> need for tests like that ...
>
Done.
>> + dev_dbg(&spi->dev, "%s: mode %d, %u bpw, %d hz\n",
>> + __func__, spi->mode, spi->bits_per_word,
>> + spi->max_speed_hz);
>> +
>
> ... also the SPI core now provides a *standard* format debug
> message for that stuff. It also handles one more thing, which
> I expect to see fixed in a v8 of this patch ... :)
Ok - I removed that dev_dbg(). Also, I noticed that spi_setup sets
bits_per_word to 8, so I've removed that as well. Did I pass your
test? :-)
Version 8 will follow shortly. BTW, this driver is dependent on your
bitbang_work fix. Not sure if that means it should be added via your
tree. But since we are in an rc phase, I'm guessing this won't merge
until 2.6.32, by which time your fix should be in the mainline.
Steve
prev parent reply other threads:[~2009-06-26 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 19:12 Subject: [PATCH v7] spi: Add PPC4xx SPI driver Steven A. Falco
2009-06-26 4:04 ` David Brownell
2009-06-26 16:17 ` Steven A. Falco [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=4A44F49E.3030003@harris.com \
--to=sfalco@harris.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@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;
as well as URLs for NNTP newsgroup(s).