On Tue, Nov 8, 2016 at 6:20 PM, Chris Brandt <Chris.Brandt@xxxxxxxxxxx> wrote: > However.... > > On 11/8/2016, Arnd Bergmann wrote: >> This simplifies it again by keeping the two separate, which then ends up >> avoiding that warning. > > I agree with Arnd's method of NOT adding a new "rspi_pio_transfer_in_or_our" > function and instead just doing it in the existing qspi_transfer_ functions. > > Side note: The RSPI in the RZ/A1 devices also have FIFOs which can be used > to reduce the number of interrupts in pio transfers, so maybe someday I'll > make a similar change for non-qspi devices as well. At which point we probably want to extract the functionality into two separate functions again, instead of inlining into qspi_transfer_{in,out}()... Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html