From: Daniel Mack <daniel@caiaq.de>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: "Éric Piel" <eric.piel@tremplin-utc.net>, linux-kernel@vger.kernel.org
Subject: Re: lis3's ACPI dependency
Date: Mon, 2 Mar 2009 01:50:24 +0100 [thread overview]
Message-ID: <20090302005024.GA3223@buzzloop.caiaq.de> (raw)
In-Reply-To: <49AAE73D.1010707@gmail.com>
On Sun, Mar 01, 2009 at 01:51:25PM -0600, Robert Hancock wrote:
>> are there any plans to free the lis3 driver from its ACPI dependency?
>> In fact, this device is I2C/SPI connected which the ACPI layer seems to
>> hide from the driver, but to use it on embedded devices, the bus drivers
>> must be used directly and the dependeny seems entirely unnecessary
>> anyway.
>
> If ACPI AML code attempts to access the device (which it obviously does,
> since we're presumably using the same code to access it), then we
> cannot be accessing it directly at the same time, otherwise the two will
> stomp on each other.
It's not about accessing the same device in more than one way one one
particular platform but about keeping the driver abstract enough so it
can be hooked up to different bus types. At the moment, it isn't
completely seperated from ACPI, that's why I'm asking.
Daniel
prev parent reply other threads:[~2009-03-02 0:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 13:29 lis3's ACPI dependency Daniel Mack
2009-03-01 18:28 ` Éric Piel
2009-03-02 0:55 ` Daniel Mack
2009-03-02 10:17 ` Éric Piel
2009-03-02 14:31 ` Daniel Mack
2009-03-02 14:31 ` Daniel Mack
2009-03-02 14:31 ` [PATCH 3/5] lis3: reorder functions to make forward decl obsolete Daniel Mack
2009-03-02 14:31 ` [PATCH 4/5] lis3: solve dependency between core and ACPI Daniel Mack
2009-03-02 14:31 ` [PATCH 5/5] lis3: SPI transport layer Daniel Mack
2009-03-02 15:11 ` Pavel Machek
2009-03-03 19:59 ` Éric Piel
2009-03-02 15:10 ` [PATCH 4/5] lis3: solve dependency between core and ACPI Pavel Machek
2009-03-03 19:54 ` Éric Piel
2009-03-04 1:43 ` Daniel Mack
2009-03-16 19:09 ` Daniel Mack
2009-03-16 21:30 ` Pavel Machek
2009-03-04 1:44 ` [PATCH 3/5] lis3: reorder functions to make forward decl obsolete Daniel Mack
2009-03-04 1:44 ` [PATCH 4/5] lis3: solve dependency between core and ACPI Daniel Mack
2009-03-04 1:44 ` [PATCH 5/5] lis3: SPI transport layer Daniel Mack
2009-03-22 23:31 ` Éric Piel
2009-03-23 15:41 ` Daniel Mack
2009-03-22 23:25 ` [PATCH 4/5] lis3: solve dependency between core and ACPI Éric Piel
2009-03-22 23:42 ` Daniel Mack
2009-03-22 23:51 ` [PATCH 1/3] lis3: reorder functions to make forward decl obsolete Daniel Mack
2009-03-22 23:51 ` [PATCH 2/3] lis3: solve dependency between core and ACPI Daniel Mack
2009-03-22 23:51 ` [PATCH 3/3] lis3: SPI transport layer Daniel Mack
2009-03-23 15:48 ` Éric Piel
2016-08-10 10:31 ` Geert Uytterhoeven
2009-03-23 15:48 ` [PATCH 2/3] lis3: solve dependency between core and ACPI Éric Piel
2009-03-23 15:48 ` [PATCH 1/3] lis3: reorder functions to make forward decl obsolete Éric Piel
2009-03-02 14:57 ` [PATCH 3/5] " Pavel Machek
2009-03-02 14:36 ` lis3's ACPI dependency Daniel Mack
2009-03-02 14:40 ` Éric Piel
2009-03-01 19:51 ` Robert Hancock
2009-03-02 0:50 ` Daniel Mack [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090302005024.GA3223@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=eric.piel@tremplin-utc.net \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox