From: "Jan Lübbe" <jlu-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Gao Pandy <gaopan-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: "Uwe Kleine-König"
<u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org"
<wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
"linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Li Frank" <Frank.Li-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
"Duan Andy" <fugang.duan-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Subject: Re: [Patch v1] i2c: imx: implement bus recovery
Date: Thu, 16 Jul 2015 14:57:42 +0200 [thread overview]
Message-ID: <1437051462.3344.140.camel@pengutronix.de> (raw)
In-Reply-To: <CY1PR0301MB0858C32968C39EA0E60E2904CF9B0-YrwGdl+PljlUWoKpOwApjpwN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
On Di, 2015-07-14 at 08:12 +0000, Gao Pandy wrote:
> > > --- a/Documentation/devicetree/bindings/i2c/i2c-imx.txt
> > > +++ b/Documentation/devicetree/bindings/i2c/i2c-imx.txt
> > > @@ -14,6 +14,8 @@ Optional properties:
> > > The absence of the propoerty indicates the default frequency
> 100 kHz.
> > > - dmas: A list of two dma specifiers, one for each entry in
> dma-names.
> > > - dma-names: should contain "tx" and "rx".
> > > +- recover-scl: specify the gpio related to SCL pin
> > > +- recover-sda: specify the gpio related to SDA pin
> > I don't like the naming here. That the gpios are used for recovery
> isn't
> > a hardware description. What about "scl-gpio" and "sda-gpio"?
>
> Thanks. I will change it in the next version.
There is already a binding for i2c-gpio:
Documentation/devicetree/bindings/i2c/i2c-gpio.txt
We should be able to reuse those properties as-is, instead of defining
something for each i2c controller binding.
Regards,
Jan
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2015-07-16 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 2:04 [Patch v1] i2c: imx: implement bus recovery Gao Pan
[not found] ` <1436839486-11110-1-git-send-email-b54642-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-07-14 6:48 ` Uwe Kleine-König
[not found] ` <20150714064832.GY1426-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2015-07-14 8:12 ` Gao Pandy
[not found] ` <CY1PR0301MB0858C32968C39EA0E60E2904CF9B0-YrwGdl+PljlUWoKpOwApjpwN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2015-07-16 12:57 ` Jan Lübbe [this message]
[not found] ` <1437051462.3344.140.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2015-07-17 2:26 ` Gao Pandy
[not found] ` <CY1PR0301MB085871D1FF9A9CF52F452E99CF980-YrwGdl+PljlUWoKpOwApjpwN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2015-07-17 9:05 ` Jan Lübbe
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=1437051462.3344.140.camel@pengutronix.de \
--to=jlu-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=Frank.Li-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=fugang.duan-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=gaopan-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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).