From: Wolfram Sang <wsa@kernel.org>
To: Codrin Ciubotariu <codrin.ciubotariu@microchip.com>,
Russell King <linux@armlinux.org.uk>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, robh+dt@kernel.org,
ludovic.desroches@microchip.com, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, kamel.bouhara@bootlin.com
Subject: Re: [RFC PATCH 1/4] dt-binding: i2c: add generic properties for GPIO bus recovery
Date: Fri, 24 Jul 2020 21:39:13 +0200 [thread overview]
Message-ID: <20200724193913.GD1227@ninjato> (raw)
In-Reply-To: <20200705211918.GB1055@kunai>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
On Sun, Jul 05, 2020 at 11:19:18PM +0200, Wolfram Sang wrote:
>
> > +- pinctrl
> > + add extra pinctrl to configure SCL/SDA pins to GPIO function for bus
> > + recovery, call it "gpio" or "recovery" state
>
> I think we should stick with "gpio" only. That is what at91 and imx have
> in their bindings. pxa uses "recovery" as a pinctrl state name but I
> can't find any further use or documentation of that. PXA is not fully
> converted to the best of my knowledge, so maybe it is no problem for PXA
> to switch to "gpio", too? We should ask Russell King (cced).
>
> Russell, do you object naming the pinctrl state for bus recovery in
> the pxa i2c driver from "recovery" to "gpio"?
No response, so far. I suggest now to support the "recovery" naming but
mark it as deprecated. Opinions?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-24 19:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 14:19 [RFC PATCH 0/4] i2c: core: add generic GPIO bus recovery Codrin Ciubotariu
2020-06-19 14:19 ` [RFC PATCH 1/4] dt-binding: i2c: add generic properties for " Codrin Ciubotariu
2020-07-05 21:19 ` Wolfram Sang
2020-07-24 19:39 ` Wolfram Sang [this message]
2020-07-24 20:52 ` Russell King - ARM Linux admin
2020-07-27 10:44 ` Codrin.Ciubotariu
2020-07-27 10:50 ` Russell King - ARM Linux admin
2020-07-30 9:00 ` Codrin.Ciubotariu
2020-08-03 14:16 ` Russell King - ARM Linux admin
2020-08-03 16:42 ` Codrin.Ciubotariu
2020-07-15 19:21 ` Rob Herring
2020-06-19 14:19 ` [RFC PATCH 2/4] i2c: core: add generic I2C GPIO recovery Codrin Ciubotariu
2020-08-02 16:54 ` Wolfram Sang
2020-08-03 13:27 ` Codrin.Ciubotariu
2020-08-03 16:49 ` wsa
2020-06-19 14:19 ` [RFC PATCH 3/4] i2c: core: treat EPROBE_DEFER when acquiring SCL/SDA GPIOs Codrin Ciubotariu
2020-08-02 17:05 ` Wolfram Sang
2020-08-03 15:33 ` Codrin.Ciubotariu
2020-08-03 16:59 ` wsa
2020-06-19 14:19 ` [RFC PATCH 4/4] i2c: at91: Move to generic GPIO bus recovery Codrin Ciubotariu
2020-08-02 17:08 ` Wolfram Sang
2020-08-03 15:42 ` Codrin.Ciubotariu
2020-08-03 16:59 ` wsa
2020-08-26 6:14 ` Wolfram Sang
2020-09-04 8:55 ` Codrin.Ciubotariu
2020-09-04 9:20 ` Wolfram Sang
2020-07-05 21:09 ` [RFC PATCH 0/4] i2c: core: add " Wolfram Sang
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=20200724193913.GD1227@ninjato \
--to=wsa@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=codrin.ciubotariu@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=kamel.bouhara@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).