[PATCH v7 3/3] [POWERPC] MPC832x_RDB: update dts to use SPI1in QE, register mmc_spi stub
vitb at kernel.crashing.org
Wed Sep 5 06:15:51 EST 2007
On Tue, 4 Sep 2007 13:20:28 -0500
Scott Wood wrote:
> > > _and system GPIOs_ :-)
> > Yup, firmware should set up gpios, to make initial kernel boot.
> No, it should set all pins and similar setup-once type initialization
> that is board-specific rather than device-specific -- there's no
> reason for the kernel to need to care about that sort of thing.
> > After that, kernel can and should manage GPIOs. Few examples.
> > Say units (like USB or SPI) can work in very different modes. And
> > it's okay if user want to change device mode in the runtime.
> This is a special case that warrants kernel involvement. It should
> not be used as justification for the bootloader leaving pins
> unconfigured in the majority of cases where it does not make sense to
> change them at runtime.
This argue is useless: both opinions have same weight. Firmware is able to provide meaningful default gpio setup, and nobody
will object. The point is, that blindly assume all the low-level stuff is fine, you are able only in case you've developed respective bits in the firmware.
More usual case is additional overhead of checking if the firmware not attempting to do something not really wanted, so we'll
always have a tradeoff.
More information about the Linuxppc-dev