Re: [REPOST PATCH v2] drivers/pinctrl: Add the concept of an "init" state

2015-10-20 Thread Doug Anderson
Hi, On Tue, Oct 20, 2015 at 7:46 PM, kbuild test robot wrote: > Hi Doug, > > [auto build test ERROR on pinctrl/for-next -- if it's inappropriate base, > please suggest rules for selecting the more suitable base] > > url: > https://github.com/0day-ci/linux/commits/Douglas-Anderson/drivers-pin

Re: [REPOST PATCH v2] drivers/pinctrl: Add the concept of an "init" state

2015-10-20 Thread kbuild test robot
Hi Doug, [auto build test ERROR on pinctrl/for-next -- if it's inappropriate base, please suggest rules for selecting the more suitable base] url: https://github.com/0day-ci/linux/commits/Douglas-Anderson/drivers-pinctrl-Add-the-concept-of-an-init-state/20151021-101131 config: i386-randconfi

[REPOST PATCH v2] drivers/pinctrl: Add the concept of an "init" state

2015-10-20 Thread Douglas Anderson
From: Doug Anderson For pinctrl the "default" state is applied to pins before the driver's probe function is called. This is normally a sensible thing to do, but in some cases can cause problems. That's because the pins will change state before the driver is given a chance to program how those