On Wed, Jun 1, 2016 at 9:21 PM, Alexander Shiyan <shc_work@xxxxxxx> wrote: > Some PINs do not have a MUX register, it is not an error. > It is necessary to allow the continuation of the PINs configuration, > otherwise the whole PIN-group will be configured incorrectly. > > Signed-off-by: Alexander Shiyan <shc_work@xxxxxxx> No reply from the i.MX maintainers for a week but the issue seems serious so I have applied it for fixes and tagged for stable. 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] pinctrl: imx: Do not treat a PIN without MUX register as an error
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] pinctrl: imx: Do not treat a PIN without MUX register as an error
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Wed, 8 Jun 2016 09:52:32 +0200
- In-reply-to: <1464808913-7796-1-git-send-email-shc_work@mail.ru>
- References:
- [PATCH] pinctrl: imx: Do not treat a PIN without MUX register as an error
- From: Alexander Shiyan
- [PATCH] pinctrl: imx: Do not treat a PIN without MUX register as an error
- Prev by Date: Re: [PATCH] pinctrl: at91-pio4: fix non-exported functions
- Next by Date: Re: [PATCH v1 1/1] gpio: pca953x: enfore type for i2c_smbus_write_word_data()
- Previous by thread: [PATCH] pinctrl: imx: Do not treat a PIN without MUX register as an error
- Next by thread: [PATCH 27/32] gpio: Add support for the FXL6408 GPIO expander.
- Index(es):
 |