On Tue, Feb 24, 2015 at 10:27:05PM +0100, Antonio Ospite wrote:
> On Mon, 23 Feb 2015 15:52:45 +0200
> Mika Westerberg wrote:
>
> > The HID over I2C specification allows to have the interrupt for a HID
> > device to be GPIO instead of directly connected to the IO-APIC.
> >
> > Add support for
On Tue, Feb 24, 2015 at 10:27:05PM +0100, Antonio Ospite wrote:
On Mon, 23 Feb 2015 15:52:45 +0200
Mika Westerberg mika.westerb...@linux.intel.com wrote:
The HID over I2C specification allows to have the interrupt for a HID
device to be GPIO instead of directly connected to the IO-APIC.
On Mon, 23 Feb 2015 15:52:45 +0200
Mika Westerberg wrote:
> The HID over I2C specification allows to have the interrupt for a HID
> device to be GPIO instead of directly connected to the IO-APIC.
>
> Add support for this so that when the driver does not find proper interrupt
> number from the
On Mon, 23 Feb 2015, Mika Westerberg wrote:
> The HID over I2C specification allows to have the interrupt for a HID
> device to be GPIO instead of directly connected to the IO-APIC.
>
> Add support for this so that when the driver does not find proper interrupt
> number from the I2C client
On Mon, 23 Feb 2015 15:52:45 +0200
Mika Westerberg mika.westerb...@linux.intel.com wrote:
The HID over I2C specification allows to have the interrupt for a HID
device to be GPIO instead of directly connected to the IO-APIC.
Add support for this so that when the driver does not find proper
On Mon, 23 Feb 2015, Mika Westerberg wrote:
The HID over I2C specification allows to have the interrupt for a HID
device to be GPIO instead of directly connected to the IO-APIC.
Add support for this so that when the driver does not find proper interrupt
number from the I2C client structure
On Mon, Feb 23, 2015 at 10:35:02AM -0500, Benjamin Tissoires wrote:
> On Feb 23 2015 or thereabouts, Mika Westerberg wrote:
> > The HID over I2C specification allows to have the interrupt for a HID
> > device to be GPIO instead of directly connected to the IO-APIC.
> >
> > Add support for this so
On Feb 23 2015 or thereabouts, Mika Westerberg wrote:
> The HID over I2C specification allows to have the interrupt for a HID
> device to be GPIO instead of directly connected to the IO-APIC.
>
> Add support for this so that when the driver does not find proper interrupt
> number from the I2C
The HID over I2C specification allows to have the interrupt for a HID
device to be GPIO instead of directly connected to the IO-APIC.
Add support for this so that when the driver does not find proper interrupt
number from the I2C client structure we check if it has ACPI GpioInt()
resource listed
The HID over I2C specification allows to have the interrupt for a HID
device to be GPIO instead of directly connected to the IO-APIC.
Add support for this so that when the driver does not find proper interrupt
number from the I2C client structure we check if it has ACPI GpioInt()
resource listed
On Feb 23 2015 or thereabouts, Mika Westerberg wrote:
The HID over I2C specification allows to have the interrupt for a HID
device to be GPIO instead of directly connected to the IO-APIC.
Add support for this so that when the driver does not find proper interrupt
number from the I2C client
On Mon, Feb 23, 2015 at 10:35:02AM -0500, Benjamin Tissoires wrote:
On Feb 23 2015 or thereabouts, Mika Westerberg wrote:
The HID over I2C specification allows to have the interrupt for a HID
device to be GPIO instead of directly connected to the IO-APIC.
Add support for this so that
12 matches
Mail list logo