Re: [PATCH v1 1/1] gpio: Support interrupts in gpio-mlxbf2.c

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> We cannot really pass it through the ACPI table because the ACPI
> table is common to all BlueField-2 boards.  And each board may have
> a different GPIO pin associated with a particular function. This is
> why we use ACPI properties instead of GpioInt(). So that the
> bootloader can change the GPIO pin value based on the board id
> detected at boot time.

That sounds very broken.

ACPI describes the hardware. If the hardware is different, you need
different ACPI. And i assume the ACPI spec says GpioInt() is the
correct way to do this, and does not say you can hack around
limitations of your bootloader using properties?

	    Andrew



[Index of Archives]     [Linux SPI]     [Linux Kernel]     [Linux ARM (vger)]     [Linux ARM MSM]     [Linux Omap]     [Linux Arm]     [Linux Tegra]     [Fedora ARM]     [Linux for Samsung SOC]     [eCos]     [Linux Fastboot]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [Linux MIPS]     [Yosemite Campsites]

  Powered by Linux