On Thu, Jan 09, 2014 at 10:41:55AM +0100, Geert Uytterhoeven wrote: > Hi Simon, > > On Fri, Dec 27, 2013 at 3:16 AM, Simon Horman <[email protected]> wrote: > > On Tue, Dec 24, 2013 at 10:26:17AM +0100, Geert Uytterhoeven wrote: > >> On Tue, Dec 24, 2013 at 3:59 AM, Simon Horman <[email protected]> wrote: > >> > On Mon, Dec 23, 2013 at 07:34:24PM +0100, Geert Uytterhoeven wrote: > >> >> The overrun flag should be cleared in the SPI Status Register, not in > >> >> the > >> >> SPI Control Register, based on the SDK sample code. > >> >> > >> >> Signed-off-by: Geert Uytterhoeven <[email protected]> > >> > >> The issue is quite obvious: after clearing the bit, the new value should > >> be written back to the same register. > >> > >> However, the fix is not in a v3.10-rc6 version I saw, so this may matter > >> for LTSI. > > > > I believe that the LTSI-3.10 work from Renesas (so far mainly me) is > > independent of the sample code at the link above. So unless this fix ends > > up in v3.10 -stable, which should feed into LTSI-3.10, then it will need to > > be submitted to LTSI (probably be me or you) if we want it to be in LTSI. > > According to the documentation, this bit is valid only in SPI slave mode. > As Linux supports SPI master mode only, this looks like a purely cosmetical > issue to me, so it doesn't warrant applying to -stable or LTSI-3.10.
Thanks for the clarification. -- To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
