All of lore.kernel.org
 help / color / mirror / Atom feed
* Questions in spi_mpc83xx.c
@ 2009-07-09 18:16 Mark Bishop
       [not found] ` <20090709141648.ws3ak25ewwogwsc0-2+Z7l/WXEz7k1uMJSBkQmQ@public.gmane.org>
  0 siblings, 1 reply; 4+ messages in thread
From: Mark Bishop @ 2009-07-09 18:16 UTC (permalink / raw)
  To: spi-devel-general; +Cc: linuxppc-dev

I haven't seen this before - the '##' in the function name.  This is ANCII C?

#define MPC83XX_SPI_TX_BUF(type)				\
u32 mpc83xx_spi_tx_buf_##type(struct mpc83xx_spi *mpc83xx_spi)	\
{								\
	u32 data;						\
....


Also, I have a SPI chip here that will drive MISO high when it is  
ready to accept more data.  It acts like a hardware handshake.  I was  
thinking about making changes to the controller source (spi_mpc83xx.c,  
in my case) to support this.

This is the only SPI chip contained on this system so I am not worried  
about affecting other SPI devices hooked to the controller.

What are people's opinion on this as far as right place to implement,  
and I could use a push as to where in the controller to make mods if  
appropriate.

And if it isn't obvious already I am still learning a bit as to how  
the SPI sub-system is organized.   I have taken apart the  
documentation in the kernel Documentation/spi directory and am reading  
all the code in drivers/spi.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2009-07-09 19:34 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-09 18:16 Questions in spi_mpc83xx.c Mark Bishop
     [not found] ` <20090709141648.ws3ak25ewwogwsc0-2+Z7l/WXEz7k1uMJSBkQmQ@public.gmane.org>
2009-07-09 18:38   ` Baruch Siach
2009-07-09 18:38     ` [spi-devel-general] " Baruch Siach
2009-07-09 19:29     ` Mark Bishop

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.