On Wed, Sep 03, 2014 at 04:39:48PM +0300, Octavian Purdila wrote: > On Tue, Sep 2, 2014 at 6:23 PM, Johan Hovold <johan@xxxxxxxxxx> wrote: > > That should be possible using the regmap bus read and write operations. > > I took a closer look on the regmap bus read/write operations and I > think they are not fit for what we need in the driver. The driver uses > a request/response model which, IMHO, does not fit well with a > register read/write API. Yes, maybe we can emulate it, but why do > that? > > >> (Also creating a regmap class for a particular device seems over > >> engineering since nobody else is going to use it) > > > > Possibly, but it would allow subdrivers to be implemented using a > > standard interface and also provide register caching for free. > > Using a standard interface is nice, but I think that using the right > interface type is more important. This hardware does not use registers > but a messages to communicate with the OS. You might be right, and as I mentioned, I haven't looked that closely at the protocol yet. I'll take a look at your updated I/O interface and how you use it. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html