Messages in this thread | | | From | "Opensource [Anthony Olech]" <> | Subject | RE: [NEW DRIVER V4 0/7] DA9058 PMIC - please comment on this new driver | Date | Tue, 16 Apr 2013 09:18:41 +0000 |
| |
> -----Original Message----- > From: Dmitry Torokhov [mailto:dmitry.torokhov@gmail.com] > Sent: 12 April 2013 19:07 > To: Opensource [Anthony Olech] > Cc: LKML; Alessandro Zummo > Subject: Re: [NEW DRIVER V4 0/7] DA9058 PMIC - please comment on this new driver > On Friday, April 12, 2013 02:05:29 PM Anthony Olech wrote: > > This is submission attempt number 4 to have this driver included in > > the linux kernel source tree. This is the driver for the Dialog DA9058. > > The DA9058 is a low power Power Management Integrated Circuit with > > extra functionality. It is a Multi Function Device controlled only > > from an I2C bus whose components can raise an interrupt request on a single IRQ line. > > The driver for the DA9058 consists of a core (i2c) device driver that > > instantiates the individual component device drivers for: > > adc - 5 ADC channels > > gpio - 2 available pins > > onkey - 1 device > > > This is almost exact copy of da9052_onkey, can they be merged together? > > Dmitry
Hi Dmitry,
it does look like the ONKEY component driver of the Dialog DA9058 PMIC is functionally similar to other onkey drivers. Specifically those drivers that have to poll for ONKEY de-assertion.
The reason why they are separate is that they are probed with different data structures and they use a different wrapper to access the "regmap" API. However, that is not a blocking issue, but it would mean re-writing the core MFD component of all the affected drivers. Maybe the way forward is:
Is it possible to provide some "core" ONKEY API or functionality to handle the commonality in a similar fashion to the regulator core as done by Mark Brown?
Tony Olech
| |