On 01/27, Mika Westerberg wrote:
>On Fri, Jan 27, 2017 at 07:51:03PM +0800, kbuild test robot wrote:
>> Hi Mika,
>>
>> [auto build test ERROR on pinctrl/for-next]
>> [also build test ERROR on v4.10-rc5 next-20170125]
>> [if your patch is applied to the wrong git tree, please drop us a note to
>>
On Mon, Jan 30, 2017 at 03:03:32PM +0100, Linus Walleij wrote:
> On Fri, Jan 27, 2017 at 11:07 AM, Mika Westerberg
> wrote:
>
> > The next generation Intel GPIO hardware has two additional registers
> > PADCFG2 and PADCFG3. The latter is marked as reserved but the former
> > includes configuratio
On Fri, Jan 27, 2017 at 11:07 AM, Mika Westerberg
wrote:
> The next generation Intel GPIO hardware has two additional registers
> PADCFG2 and PADCFG3. The latter is marked as reserved but the former
> includes configuration for per-pad hardware debouncer.
>
> This patch adds support for that in t
On Fri, Jan 27, 2017 at 07:51:03PM +0800, kbuild test robot wrote:
> Hi Mika,
>
> [auto build test ERROR on pinctrl/for-next]
> [also build test ERROR on v4.10-rc5 next-20170125]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
>
Hi Mika,
[auto build test ERROR on pinctrl/for-next]
[also build test ERROR on v4.10-rc5 next-20170125]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Mika-Westerberg/pinctrl-intel-Add-support-f
The next generation Intel GPIO hardware has two additional registers
PADCFG2 and PADCFG3. The latter is marked as reserved but the former
includes configuration for per-pad hardware debouncer.
This patch adds support for that in the Intel pinctrl core driver. Since
these are additional features on
6 matches
Mail list logo
