On Mon, Jul 09, 2012 at 11:24:45AM +0800, Lan Tianyu wrote:
> I think we can add new interface to get acpi specific resources. e.g
> struct acpi_resource pnp_get_acpi_resource(...). When the pnp acpi devices
> were initialized, put those acpi specific resources into a new resource list
> pnpdev->ac
gt; w.s...@pengutronix.de; l...@kernel.org; linux-a...@vger.kernel.org; linux-
>> i...@vger.kernel.org; linux-kernel@vger.kernel.org; jkos...@suse.cz;
>> cha...@enac.fr; jj_d...@emc.com.tw; bhelg...@google.com; abe...@mit.edu
>> Subject: Re: Fwd: Hid over I2C and ACPI interaction
>>
&g
.@mit.edu
>Subject: Re: Fwd: Hid over I2C and ACPI interaction
>
>On 2012年07月06日 13:52, Mika Westerberg wrote:
>> On Thu, Jul 05, 2012 at 03:01:57PM +0800, Zhang Rui wrote:
>>> +Note that although these are ACPI devices, we prefer to use PnP drivers
>>> for them,
>&
On 2012年07月06日 13:52, Mika Westerberg wrote:
On Thu, Jul 05, 2012 at 03:01:57PM +0800, Zhang Rui wrote:
+Note that although these are ACPI devices, we prefer to use PnP drivers
for them,
+this is because:
+1. all the non-ACPI-predefined Devices are exported as PnP devices as
well
+2. PnP bus is
On 四, 2012-07-05 at 10:44 +0200, Benjamin Tissoires wrote:
> Hi,
>
> Many thanks for these information. It seems like I was on the right
> track, but I didn't saw the hidden part of the iceberg.
yep.
> I've already written the i2c slave part (and the acpi handling to get
> the HID register by us
5 matches
Mail list logo
