On Thu, Feb 06, 2014 at 00:54:11AM +, Guenter Roeck wrote:
Adam,
You don't really explain what the problem actually is. Can you elaborate ?
Sorry, yes. For the conflicting device Ids, both the PMIC and the CODEC used
the same I2C Id string, which meant if you tried to intiate both
On 02/06/2014 03:46 AM, Opensource [Adam Thomson] wrote:
On Thu, Feb 06, 2014 at 00:54:11AM +, Guenter Roeck wrote:
Adam,
You don't really explain what the problem actually is. Can you elaborate ?
Sorry, yes. For the conflicting device Ids, both the PMIC and the CODEC used
the same I2C
On Thu, Feb 06, 2014 at 13:23:47PM +, Guenter Roeck wrote:
What I could've done is use platform_get_irq_byname() and avoided using
regmap_irq_get_virq() as I would already have the correct VIRQ to pass to
request_threaded_irq(), but I figured that using regmap_irq_get_virq() made
more
This patch series provides the following updates for DA9055 drivers:
- Fixes an issue with da9055 driver initialisation (conflicting device ids) of
PMIC (MFD) and CODEC drivers.
- Add initial DT support for DA9055 related drivers, including binding
documentation.
- Remove conflicting use
On Wed, Feb 05, 2014 at 05:48:28PM +, Adam Thomson wrote:
This patch series provides the following updates for DA9055 drivers:
- Fixes an issue with da9055 driver initialisation (conflicting device ids)
of
PMIC (MFD) and CODEC drivers.
- Add initial DT support for DA9055 related
