From: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
To: "'Kumar Gala'" <galak@kernel.crashing.org>
Cc: 'linuxppc-dev Development' <linuxppc-dev@ozlabs.org>,
spi-devel-general@lists.sourceforge.net
Subject: RE: [PATCH] Adapt spi_mpc83xx SPI driver for 832x
Date: Wed, 13 Dec 2006 16:36:00 +0100 [thread overview]
Message-ID: <032a01c71ecc$659ae480$020120ac@Jocke> (raw)
In-Reply-To: <5CD24382-201C-4B60-B410-3746A032415A@kernel.crashing.org>
> -----Original Message-----
> From: Kumar Gala [mailto:galak@kernel.crashing.org]
> Sent: den 13 december 2006 15:46
> To: joakim.tjernlund@transmode.se
> Cc: linuxppc-dev Development; spi-devel-general@lists.sourceforge.net
> Subject: Re: [PATCH] Adapt spi_mpc83xx SPI driver for 832x
>
>
> On Dec 13, 2006, at 3:22 AM, Joakim Tjernlund wrote:
>
> > The MPC 832x has a different SPI controller i/f, probably due to
> > its QUICC engine support. This patch adapts the spi_mpx83xx
> driver to
> > be usable on QE based 83xx cpus.
> >
> > Jocke
>
> One problem I have with this patch is the fact that it assumes the
> current driver for (mpc834x) and your mods to support mpc832x/QE are
> mutually exclusive.
I don't see that as a problem ATM. If that is added it should be optional.
>
> We need to handle the case of having driver support for both the QE
> and MPC834x style in the same kernel.
Adding that will double the number RX_BUF/TX_BUF functions from 6 to 12
(possibly this can be reduced by adding more logic to the tx_buf/rx_buf functions)
not to mention what will happen when support for reversed bit order is added.
I would argue that the kernel lacks the possibility to remove complexity
I don't need. Example in this driver is that there is no way to remove
support for 16 and 32 bit SPI character sizes. The same goes for a lot of
the probing code in fsl-soc.c.
It would be nice if a board port could add a custom header file that
gets included by all .c automatically. Then one could add knobs
(read #defines) there to futher tune such things as SPI char size.
That way one don't have add Kconfig entries for all those small
tuning knobs.
Jocke
next prev parent reply other threads:[~2006-12-13 15:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 9:22 [PATCH] Adapt spi_mpc83xx SPI driver for 832x Joakim Tjernlund
2006-12-13 9:44 ` Vitaly Wool
2006-12-13 9:53 ` Li Yang-r58472
2006-12-13 14:46 ` Kumar Gala
2006-12-13 15:36 ` Joakim Tjernlund [this message]
2006-12-13 20:31 ` [spi-devel-general] " David Brownell
2006-12-14 0:13 ` Joakim Tjernlund
2006-12-14 5:54 ` Kumar Gala
2006-12-14 10:02 ` Joakim Tjernlund
2006-12-14 19:59 ` Reeve Yang
2006-12-14 20:12 ` Ben Warren
2006-12-14 20:39 ` Reeve Yang
2006-12-14 21:30 ` Ben Warren
2006-12-23 1:09 ` David Brownell
2006-12-26 16:31 ` Kumar Gala
2007-02-17 2:17 ` David Brownell
2007-02-17 9:14 ` Joakim Tjernlund
2006-12-23 0:57 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2006-12-13 9:59 Joakim Tjernlund
2006-12-13 10:05 Joakim Tjernlund
2006-12-13 10:45 ` Vitaly Wool
2006-12-13 12:22 Joakim Tjernlund
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='032a01c71ecc$659ae480$020120ac@Jocke' \
--to=joakim.tjernlund@transmode.se \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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).