On Tue, Aug 23, 2016 at 11:39:48PM +0200, Wolfram Sang wrote:
> On Tue, Aug 23, 2016 at 11:28:59PM +0200, Jan Glauber wrote:
> > On Tue, Aug 23, 2016 at 10:57:25PM +0200, Wolfram Sang wrote:
> > > On Wed, Jun 15, 2016 at 03:51:30PM +0200, Jan Glauber wrote:
> > > > Add SMBUS alert interrupt support
On Tue, Aug 23, 2016 at 11:28:59PM +0200, Jan Glauber wrote:
> On Tue, Aug 23, 2016 at 10:57:25PM +0200, Wolfram Sang wrote:
> > On Wed, Jun 15, 2016 at 03:51:30PM +0200, Jan Glauber wrote:
> > > Add SMBUS alert interrupt support. For now only device tree is
> > > supported for specifying the alert
On Tue, Aug 23, 2016 at 10:57:25PM +0200, Wolfram Sang wrote:
> On Wed, Jun 15, 2016 at 03:51:30PM +0200, Jan Glauber wrote:
> > Add SMBUS alert interrupt support. For now only device tree is
> > supported for specifying the alert. In case of ACPI an error
> > is returned.
> >
> > Signed-off-by: J
On Wed, Jun 15, 2016 at 03:51:30PM +0200, Jan Glauber wrote:
> Add SMBUS alert interrupt support. For now only device tree is
> supported for specifying the alert. In case of ACPI an error
> is returned.
>
> Signed-off-by: Jan Glauber
What about 'select I2C_SMBUS' in Kconfig and skip all the ifd
Add SMBUS alert interrupt support. For now only device tree is
supported for specifying the alert. In case of ACPI an error
is returned.
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/i2c-cavium.h| 6
drivers/i2c/busses/i2c-thunderx-core.c | 51 ++
5 matches
Mail list logo