On 29/09/12 21:57, Jean-Christophe PLAGNIOL-VILLARD wrote: >> Problem here is that it's only an intermediate format since hardware >> often needs special preparation of the data. >> >> But will evaluate what makes most sense. > the key point here is to avoid to manipualte data each time we call > gpio_block_set > > hardware specific will have to be handle at driver level
Understand, thanks! I'm just trying to prevent overly complex API because: * In our discussed scheme, the driver still needs to convert the data bits * In practice, the block gpio API is especially useful for use on single gpio_chips (only there, a real simultaneous i/o is possible anyway) * Wouldn't introduce this kind of optimization in lack of measurable improvement * The actual i/o data bits still need handling, generating a bit CPU load anyway. Trying to provide as simple API as possible. Roland -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
