On Tue, Jan 10, 2017 at 3:31 PM, Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx> wrote: > PADCFGLOCK (and PADCFGLOCK_TX) offset in Broxton actually starts at 0x060 > and not 0x090 as used in the driver. Fix it to use the correct offset. > > Signed-off-by: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx> > Reviewed-by: Andy Shevchenko <andy.shevchenko@xxxxxxxxx> This patch applied for fixes. 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 v2 1/6] pinctrl: broxton: Use correct PADCFGLOCK offset
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH v2 1/6] pinctrl: broxton: Use correct PADCFGLOCK offset
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Wed, 11 Jan 2017 13:47:41 +0100
- In-reply-to: <20170110143201.53539-2-mika.westerberg@linux.intel.com>
- References: <20170110143201.53539-1-mika.westerberg@linux.intel.com> <20170110143201.53539-2-mika.westerberg@linux.intel.com>
- References:
- [PATCH v2 0/6] pinctrl: Fixes and updates to Intel drivers
- From: Mika Westerberg
- [PATCH v2 1/6] pinctrl: broxton: Use correct PADCFGLOCK offset
- From: Mika Westerberg
- [PATCH v2 0/6] pinctrl: Fixes and updates to Intel drivers
- Prev by Date: [PATCH] gpio: provide lockdep keys for nested/unnested irqchips
- Next by Date: Re: [PATCH v1 1/1] pinctrl: intel: Set pin direction properly
- Previous by thread: [PATCH v2 1/6] pinctrl: broxton: Use correct PADCFGLOCK offset
- Next by thread: [PATCH v2 1/1] pinctrl: baytrail: Rectify debounce support
- Index(es):
 |