On Mon, Aug 12, 2019 at 07:14:01PM +0300, Andy Shevchenko wrote: > Some firmwares would like to protect pads from being modified by OS > and at the same time provide them to OS as a resource. So, the driver > in such circumstances may request pad and may not change its state. > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> > Reviewed-by: Linus Walleij <linus.walleij@xxxxxxxxxx> Acked-by: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
Re: [PATCH v3] pinctrl: intel: Allow to request locked pads
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH v3] pinctrl: intel: Allow to request locked pads
- From: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
- Date: Mon, 12 Aug 2019 20:53:00 +0300
- In-reply-to: <20190812161401.87589-1-andriy.shevchenko@linux.intel.com>
- Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
- References: <20190812161401.87589-1-andriy.shevchenko@linux.intel.com>
- User-agent: Mutt/1.12.1 (2019-06-15)
- References:
- [PATCH v3] pinctrl: intel: Allow to request locked pads
- From: Andy Shevchenko
- [PATCH v3] pinctrl: intel: Allow to request locked pads
- Prev by Date: Re: [PATCH] gpio: merrifield: Pass irqchip when adding gpiochip
- Next by Date: Re: [PATCH] pinctrl: intel: baytrail: Pass irqchip when adding gpiochip
- Previous by thread: [PATCH v3] pinctrl: intel: Allow to request locked pads
- Next by thread: [PATCH v2] gpiolib: Take MUX usage into account
- Index(es):
 |