ACPI
Matthew Garrett
mjg59 at srcf.ucam.org
Mon Nov 25 10:41:10 EST 2013
On Mon, Nov 25, 2013 at 11:33:56AM +0000, Grant Likely wrote:
> What I'm assuming here is that on ACPI the pinctrl setup and
> management would be performed by the platform in AML methods so that
> the kernel isn't aware of them at all. All it know is that it has a
> (for example) SPI bus and as far as it is concerned the pins are
> correctly attached when the SPI bus is active. My understanding is
> that historically this is how ACPI has been used.
Pretty much. In the past ACPI implementations handled GPIO by providing
methods that accessed hardware registers directly. I've seen DSDTs that
implement i2c entirely in ASL. It's *very* common for hwmon devices to
be hidden away behind some ACPI methods.
The obvious downside of this approach is that there's no real mechanism
for allowing a real driver to access the hardware at the same time as
the ACPI code, and as a consequence you're limited to whatever
functionality is provided by the ACPI code.
--
Matthew Garrett | mjg59 at srcf.ucam.org
More information about the linux-arm-kernel
mailing list