Hi Kumar,
I'm using the 3.0.3 kernel on an MPC8308 and utilizing the spi_fsl_spi
driver to talk with an Cypress NvRAM device. I've gotten that working
now, but I've come across something I don't understand in the driver and
I'm not sure if it's just me or if there's a bug. My issue relates to
Norbert,
>
> ok, then I don't know.
>
> I doubt this is a spidev or FSP SPI driver problem though.
>
> Questions like:
>
> Could it be a HW problem ?
> Is the correct SPI mode used ?
> Does it work in u-boot ?
>
> Come to mind in a situation like this.
>
Thanks for the suggestions. I final
Hi Bruce,
On 01/25/12 20:49, bruce_leon...@selinc.com wrote:
.
.
.
Thanks for the reply. Yes I did find spidev_fdx.c and in fact copied it
for my tests. I still see SPICLK active only during the time the 8308 is
sending data (read cmd + address). Nothing happens with the clock after
that whe
Hi Norbert,
> >
> > So the question is, how do I use spidev (or any other means) to get
the
> > 8308 SPI controller to keep SPICLK active so that the output data from
the
> > NvRAM gets clocked out to the 8308?
> >
>
> Did you see Documentation/spi/spidev_fdx.c:do_msg ?
> it perform a full-dupl
On 01/25/12 01:11, bruce_leon...@selinc.com wrote:
Good afternoon,
I'm using the 3.0.3 kernel running on an MPC8308 and am trying to
interface to a Cypress CY14B256Q2A non-volatile RAM via SPI. I've got the
SPI infrastructure, the Freescale SPI driver (drivers/spi/spi_fsl_spi.c),
and spidev bui
Good afternoon,
I'm using the 3.0.3 kernel running on an MPC8308 and am trying to
interface to a Cypress CY14B256Q2A non-volatile RAM via SPI. I've got the
SPI infrastructure, the Freescale SPI driver (drivers/spi/spi_fsl_spi.c),
and spidev built into the kernel and everything on the user spac
