On Thu, Jan 26, 2017 at 2:17 PM, Alexander Stein <alexander.stein@xxxxxxxxxxxxxxxxxxxxx> wrote: > Apparently each GPIO pad's register are 16 bytes, so multiply the pad_map > by that. The same is done in byt_gpio_reg the only other place where > pad_map is used. > > Signed-off-by: Alexander Stein <alexander.stein@xxxxxxxxxxxxxxxxxxxxx> Patch applied. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/1] pinctrl: baytrail: Fix debugfs offset output
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH 1/1] pinctrl: baytrail: Fix debugfs offset output
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Thu, 26 Jan 2017 16:44:41 +0100
- In-reply-to: <20170126131754.29630-1-alexander.stein@systec-electronic.com>
- References: <20170126131754.29630-1-alexander.stein@systec-electronic.com>
- References:
- [PATCH 1/1] pinctrl: baytrail: Fix debugfs offset output
- From: Alexander Stein
- [PATCH 1/1] pinctrl: baytrail: Fix debugfs offset output
- Prev by Date: Re: [PATCH v3 REBASED 11/13] pinctrl: samsung: Move retention control from mach-exynos to the pinctrl driver
- Next by Date: Re: [PATCH v3 REBASED 13/13] pinctrl: samsung: Replace syscore ops with standard platform device pm_ops
- Previous by thread: [PATCH 1/1] pinctrl: baytrail: Fix debugfs offset output
- Next by thread: Suspicious debounce handling code in pintctrl-baytrail
- Index(es):
 |