From: Linus Walleij <linus.walleij@linaro.org>
To: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"david.daney@cavium.com" <david.daney@cavium.com>,
"sathyanarayanan.kuppuswamy@linux.intel.com"
<sathyanarayanan.kuppuswamy@linux.intel.com>,
"sre@kernel.org" <sre@kernel.org>,
"ptyser@xes-inc.com" <ptyser@xes-inc.com>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"marek.behun@nic.cz" <marek.behun@nic.cz>,
"festevam@gmail.com" <festevam@gmail.com>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"marek.vasut+renesas@gmail.com" <marek.vasut+renesas@gmail.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"khilman@kernel.org" <khilman@kernel.org>,
"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
"jonathanh@nvidia.com" <jonathanh@nvidia.com>,
"bgolaszewski@baylibre.com" <bgolaszewski@baylibre.>
Subject: Re: [PATCH v2 0/2] Add definition for GPIO direction
Date: Thu, 7 Nov 2019 09:22:35 +0100 [thread overview]
Message-ID: <CACRpkdbaRsv+cKz7yxKxvs+99GRK50-d_kpKcdVn3NVV9Qr6Ng@mail.gmail.com> (raw)
In-Reply-To: <ddcd02cc6c709837a28cae2cbfa672c506927659.camel@fi.rohmeurope.com>
On Wed, Nov 6, 2019 at 1:25 PM Vaittinen, Matti
<Matti.Vaittinen@fi.rohmeurope.com> wrote:
> On Wed, 2019-11-06 at 13:08 +0100, Sebastian Reichel wrote:
> > On Wed, Nov 06, 2019 at 10:51:06AM +0200, Matti Vaittinen wrote:
> > > The patch series adds definitions for GPIO line directions.
> > >
> > > For occasional GPIO contributor like me it is always a pain to
> > > remember
> > > whether 1 or 0 was used for GPIO direction INPUT/OUTPUT.
> >
> > Maybe also update the GPIO drivers in pinctrl?
(...)
> Ouch. I didn't check from pinctrl but I see those should be converted
> as well. I'm a bit short on time right now so if anyone else is
> interested I won't mind :)
>
> Luckily the value for IN and OUT is not changed - only the defines were
> added - so all of the drivers do not need to be done at once. If no one
> else will take the pinctrl part then I can probably do pinctrl patches
> for v5.6 cycle.
No hurry with that. This is a good start, we don't have to fix
the whole world at once.
Let's look at this for v5.6.
Yours,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"david.daney@cavium.com" <david.daney@cavium.com>,
"sathyanarayanan.kuppuswamy@linux.intel.com"
<sathyanarayanan.kuppuswamy@linux.intel.com>,
"sre@kernel.org" <sre@kernel.org>,
"ptyser@xes-inc.com" <ptyser@xes-inc.com>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"marek.behun@nic.cz" <marek.behun@nic.cz>,
"festevam@gmail.com" <festevam@gmail.com>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"marek.vasut+renesas@gmail.com" <marek.vasut+renesas@gmail.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"khilman@kernel.org" <khilman@kernel.org>,
"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
"jonathanh@nvidia.com" <jonathanh@nvidia.com>,
"bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"bamv2005@gmail.com" <bamv2005@gmail.com>,
"joel@jms.id.au" <joel@jms.id.au>,
"u.kleine-koenig@pengutronix.de" <u.kleine-koenig@pengutronix.de>,
"bcm-kernel-feedback-list@broadcom.com"
<bcm-kernel-feedback-list@broadcom.com>,
"linux-imx@nxp.com" <linux-imx@nxp.com>,
"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>,
"grygorii.strashko@ti.com" <grygorii.strashko@ti.com>,
"ckeepax@opensource.cirrus.com" <ckeepax@opensource.cirrus.com>,
"alexandre.torgue@st.com" <alexandre.torgue@st.com>,
"mazziesaccount@gmail.com" <mazziesaccount@gmail.com>,
"rjui@broadcom.com" <rjui@broadcom.com>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"vilhelm.gray@gmail.com" <vilhelm.gray@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"rf@opensource.cirrus.com" <rf@opensource.cirrus.com>,
"ssantosh@kernel.org" <ssantosh@kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"sbranden@broadcom.com" <sbranden@broadcom.com>,
"yamada.masahiro@socionext.com" <yamada.masahiro@socionext.com>,
"andrew@aj.id.au" <andrew@aj.id.au>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"t.scherer@eckelmann.de" <t.scherer@eckelmann.de>,
"ludovic.desroches@microchip.com"
<ludovic.desroches@microchip.com>,
"mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>,
"patches@opensource.cirrus.com" <patches@opensource.cirrus.com>,
"info@metux.net" <info@metux.net>
Subject: Re: [alsa-devel] [PATCH v2 0/2] Add definition for GPIO direction
Date: Thu, 7 Nov 2019 09:22:35 +0100 [thread overview]
Message-ID: <CACRpkdbaRsv+cKz7yxKxvs+99GRK50-d_kpKcdVn3NVV9Qr6Ng@mail.gmail.com> (raw)
In-Reply-To: <ddcd02cc6c709837a28cae2cbfa672c506927659.camel@fi.rohmeurope.com>
On Wed, Nov 6, 2019 at 1:25 PM Vaittinen, Matti
<Matti.Vaittinen@fi.rohmeurope.com> wrote:
> On Wed, 2019-11-06 at 13:08 +0100, Sebastian Reichel wrote:
> > On Wed, Nov 06, 2019 at 10:51:06AM +0200, Matti Vaittinen wrote:
> > > The patch series adds definitions for GPIO line directions.
> > >
> > > For occasional GPIO contributor like me it is always a pain to
> > > remember
> > > whether 1 or 0 was used for GPIO direction INPUT/OUTPUT.
> >
> > Maybe also update the GPIO drivers in pinctrl?
(...)
> Ouch. I didn't check from pinctrl but I see those should be converted
> as well. I'm a bit short on time right now so if anyone else is
> interested I won't mind :)
>
> Luckily the value for IN and OUT is not changed - only the defines were
> added - so all of the drivers do not need to be done at once. If no one
> else will take the pinctrl part then I can probably do pinctrl patches
> for v5.6 cycle.
No hurry with that. This is a good start, we don't have to fix
the whole world at once.
Let's look at this for v5.6.
Yours,
Linus Walleij
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"david.daney@cavium.com" <david.daney@cavium.com>,
"sathyanarayanan.kuppuswamy@linux.intel.com"
<sathyanarayanan.kuppuswamy@linux.intel.com>,
"sre@kernel.org" <sre@kernel.org>,
"ptyser@xes-inc.com" <ptyser@xes-inc.com>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"marek.behun@nic.cz" <marek.behun@nic.cz>,
"festevam@gmail.com" <festevam@gmail.com>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"marek.vasut+renesas@gmail.com" <marek.vasut+renesas@gmail.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"khilman@kernel.org" <khilman@kernel.org>,
"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
"jonathanh@nvidia.com" <jonathanh@nvidia.com>,
"bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"bamv2005@gmail.com" <bamv2005@gmail.com>,
"joel@jms.id.au" <joel@jms.id.au>,
"u.kleine-koenig@pengutronix.de" <u.kleine-koenig@pengutronix.de>,
"bcm-kernel-feedback-list@broadcom.com"
<bcm-kernel-feedback-list@broadcom.com>,
"linux-imx@nxp.com" <linux-imx@nxp.com>,
"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>,
"grygorii.strashko@ti.com" <grygorii.strashko@ti.com>,
"ckeepax@opensource.cirrus.com" <ckeepax@opensource.cirrus.com>,
"alexandre.torgue@st.com" <alexandre.torgue@st.com>,
"mazziesaccount@gmail.com" <mazziesaccount@gmail.com>,
"rjui@broadcom.com" <rjui@broadcom.com>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"vilhelm.gray@gmail.com" <vilhelm.gray@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"rf@opensource.cirrus.com" <rf@opensource.cirrus.com>,
"ssantosh@kernel.org" <ssantosh@kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"sbranden@broadcom.com" <sbranden@broadcom.com>,
"yamada.masahiro@socionext.com" <yamada.masahiro@socionext.com>,
"andrew@aj.id.au" <andrew@aj.id.au>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"t.scherer@eckelmann.de" <t.scherer@eckelmann.de>,
"ludovic.desroches@microchip.com"
<ludovic.desroches@microchip.com>,
"mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>,
"patches@opensource.cirrus.com" <patches@opensource.cirrus.com>,
"info@metux.net" <info@metux.net>
Subject: Re: [PATCH v2 0/2] Add definition for GPIO direction
Date: Thu, 7 Nov 2019 09:22:35 +0100 [thread overview]
Message-ID: <CACRpkdbaRsv+cKz7yxKxvs+99GRK50-d_kpKcdVn3NVV9Qr6Ng@mail.gmail.com> (raw)
In-Reply-To: <ddcd02cc6c709837a28cae2cbfa672c506927659.camel@fi.rohmeurope.com>
On Wed, Nov 6, 2019 at 1:25 PM Vaittinen, Matti
<Matti.Vaittinen@fi.rohmeurope.com> wrote:
> On Wed, 2019-11-06 at 13:08 +0100, Sebastian Reichel wrote:
> > On Wed, Nov 06, 2019 at 10:51:06AM +0200, Matti Vaittinen wrote:
> > > The patch series adds definitions for GPIO line directions.
> > >
> > > For occasional GPIO contributor like me it is always a pain to
> > > remember
> > > whether 1 or 0 was used for GPIO direction INPUT/OUTPUT.
> >
> > Maybe also update the GPIO drivers in pinctrl?
(...)
> Ouch. I didn't check from pinctrl but I see those should be converted
> as well. I'm a bit short on time right now so if anyone else is
> interested I won't mind :)
>
> Luckily the value for IN and OUT is not changed - only the defines were
> added - so all of the drivers do not need to be done at once. If no one
> else will take the pinctrl part then I can probably do pinctrl patches
> for v5.6 cycle.
No hurry with that. This is a good start, we don't have to fix
the whole world at once.
Let's look at this for v5.6.
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-07 8:22 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 8:51 [PATCH v2 0/2] Add definition for GPIO direction Matti Vaittinen
2019-11-06 8:51 ` Matti Vaittinen
2019-11-06 8:51 ` [alsa-devel] " Matti Vaittinen
2019-11-06 8:51 ` [PATCH v2 1/2] gpio: " Matti Vaittinen
2019-11-06 8:51 ` Matti Vaittinen
2019-11-06 8:51 ` [alsa-devel] " Matti Vaittinen
2019-11-07 8:20 ` Linus Walleij
2019-11-07 8:20 ` Linus Walleij
2019-11-07 8:20 ` [alsa-devel] " Linus Walleij
2019-11-06 8:54 ` [PATCH v2 2/2] gpio: Use new GPIO_LINE_DIRECTION Matti Vaittinen
2019-11-06 8:54 ` Matti Vaittinen
2019-11-06 8:54 ` [alsa-devel] " Matti Vaittinen
2019-11-06 14:22 ` Andy Shevchenko
2019-11-06 14:22 ` Andy Shevchenko
2019-11-06 14:22 ` [alsa-devel] " Andy Shevchenko
2019-11-06 14:43 ` William Breathitt Gray
2019-11-06 14:43 ` William Breathitt Gray
2019-11-06 14:43 ` [alsa-devel] " William Breathitt Gray
2019-11-06 17:35 ` Kuppuswamy Sathyanarayanan
2019-11-06 17:35 ` Kuppuswamy Sathyanarayanan
2019-11-06 17:35 ` [alsa-devel] " Kuppuswamy Sathyanarayanan
2019-11-07 8:33 ` Linus Walleij
2019-11-06 12:08 ` [PATCH v2 0/2] Add definition for GPIO direction Sebastian Reichel
2019-11-06 12:08 ` Sebastian Reichel
2019-11-06 12:08 ` [alsa-devel] " Sebastian Reichel
2019-11-06 12:25 ` Vaittinen, Matti
2019-11-06 12:25 ` Vaittinen, Matti
2019-11-06 12:25 ` [alsa-devel] " Vaittinen, Matti
2019-11-06 14:24 ` andriy.shevchenko
2019-11-06 14:24 ` andriy.shevchenko
2019-11-06 14:24 ` [alsa-devel] " andriy.shevchenko
2019-11-07 8:26 ` Linus Walleij
2019-11-07 8:26 ` Linus Walleij
2019-11-07 8:32 ` Geert Uytterhoeven
2019-11-07 8:32 ` Geert Uytterhoeven
2019-11-07 8:52 ` Vaittinen, Matti
2019-11-07 8:52 ` Vaittinen, Matti
2019-11-07 12:08 ` Sebastian Reichel
2019-11-07 12:08 ` Sebastian Reichel
2019-11-08 7:46 ` Nandor Han
2019-11-08 7:46 ` Nandor Han
2019-11-07 8:52 ` andriy.shevchenko
2019-11-07 8:52 ` andriy.shevchenko
2019-11-07 8:22 ` Linus Walleij [this message]
2019-11-07 8:22 ` Linus Walleij
2019-11-07 8:22 ` [alsa-devel] " Linus Walleij
2019-11-06 14:39 ` William Breathitt Gray
2019-11-06 14:39 ` William Breathitt Gray
2019-11-06 14:39 ` [alsa-devel] " William Breathitt Gray
2019-11-06 17:28 ` Vaittinen, Matti
2019-11-06 17:28 ` Vaittinen, Matti
2019-11-06 17:28 ` [alsa-devel] " Vaittinen, Matti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACRpkdbaRsv+cKz7yxKxvs+99GRK50-d_kpKcdVn3NVV9Qr6Ng@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=Matti.Vaittinen@fi.rohmeurope.com \
--cc=alsa-devel@alsa-project.org \
--cc=bgolaszewski@baylibre. \
--cc=david.daney@cavium.com \
--cc=f.fainelli@gmail.com \
--cc=festevam@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=khilman@kernel.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marek.behun@nic.cz \
--cc=marek.vasut+renesas@gmail.com \
--cc=michal.simek@xilinx.com \
--cc=ptyser@xes-inc.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=sre@kernel.org \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.