[Potential Spoof] Increase ARCH_NR_GPIO for ARCH_ASPEED?

[Andrew Jeffery]

On Fri, 15 Feb 2019, at 11:36, Tao Ren wrote:
> On 2/14/19 3:16 PM, Tao Ren wrote:
> > Hi,
> > 
> > I got following error while booting up openbmc linux 4.18 on Facebook YAMP BMC (ast2500 based), and it's because total 594 GPIO pins are provided by aspeed soc and i/o expanders on YAMP board:
> > 
> > gpiochip_find_base: cannot find free range
> > gpiochip_add_data_with_key: GPIOs 0..15 (pca9555) failed to register
> > 
> > I'm wondering if it's good idea to increase ARCH_NR_GPIO default value to the "next level" (1024) for ARCH_ASPEED? If not, any other suggestions for this problem?

I don't know that there's much other choice, but beware that changing
the value will impact userspace if you're using the sysfs interface (which
you  ideally you shouldn't be, as it's deprecated), as the base addresses
of the gpiochips will change.

Andrew