>> Maybe the same idea can be applied to the cpp definitions GPIOD_OUT_LOW >> and GPIOD_OUT_HIGH. I'd say it was quite bad idea to introduce ACTIVE_LOW thing while still same "high" / "low" names all over the API. Now this is causing confusion in every other use case. The only way to clean up this mess now without breaking things is to rename everything, and deprecate all currently-exisitng identifiers containing "high" and "low" substrings. -- 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: [RFC PATCH] gpio: use "output-active" and "output-inactive" for gpio-hogs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [RFC PATCH] gpio: use "output-active" and "output-inactive" for gpio-hogs
- From: Nikita Yushchenko <nikita.yoush@xxxxxxxxxxxxxxxxxx>
- Date: Fri, 9 Jun 2017 10:10:15 +0300
- In-reply-to: <20170608223346.unfwdh32v3kt2y52@rob-hp-laptop>
- References: <20170604101049.4592-1-uwe@kleine-koenig.org> <20170608223346.unfwdh32v3kt2y52@rob-hp-laptop>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
- References:
- [RFC PATCH] gpio: use "output-active" and "output-inactive" for gpio-hogs
- From: Uwe Kleine-König
- Re: [RFC PATCH] gpio: use "output-active" and "output-inactive" for gpio-hogs
- From: Rob Herring
- [RFC PATCH] gpio: use "output-active" and "output-inactive" for gpio-hogs
- Prev by Date: [REGRESSION next] gpio-keys broken with commit 2233bf7a92e7 ("gpio: mvebu: switch to regmap for register access")
- Next by Date: Re: [PATCH v5 01/11] serial: exar: Leave MPIOs as output for Commtech adapters
- Previous by thread: Re: [RFC PATCH] gpio: use "output-active" and "output-inactive" for gpio-hogs
- Next by thread: Re: [RFC PATCH] gpio: use "output-active" and "output-inactive" for gpio-hogs
- Index(es):
 |