On Sunday, August 03, 2014 at 09:34:33 AM, Nikita Kiryanov wrote: > MXC SPI driver has a feature whereas a GPIO line can be used as a CS > signal. This is set up by joining the CS and GPIO values into a single > value using (cs | gpio << 8), and passing it off as a CS value. This > breaks the sf probe command, because it is no longer possible to invoke it > as sf probe <cs>. Instead, the user must use sf probe <cs | gpio << 8>. > > Fix this by introducing a new board function: board_spi_cs_gpio(). > When called, board_spi_cs_gpio() will return the gpio number for the > cs value it is given. > > Cc: Jagannadha Sutradharudu Teki <jagannadh.t...@gmail.com> > Cc: Eric Nelson <eric.nel...@boundarydevices.com> > Cc: Eric Benard <e...@eukrea.com> > Cc: Fabio Estevam <fabio.este...@freescale.com> > Cc: Tim Harvey <thar...@gateworks.com> > Cc: Stefano Babic <sba...@denx.de> > Cc: Tom Rini <tr...@ti.com> > Signed-off-by: Nikita Kiryanov <nik...@compulab.co.il>
Just curious, but is this fixing generic SF code or MXC SPI driver ? I'd think the later, but it's not obvious from neither the description nor the subject. I don't quite understand the problem that you're trying to fix either, what happened, did the user command interface change ? [...] Best regards, Marek Vasut _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
