From: Wolfram Sang <wsa@the-dreams.de>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Chris Paterson <Chris.Paterson2@renesas.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH 0/2] Use demuxer for i2c1 and i2c5
Date: Mon, 22 Jan 2018 13:22:04 +0100 [thread overview]
Message-ID: <20180122122204.n25jf2rtaoxmi2yq@katana> (raw)
In-Reply-To: <KL1PR06MB170270EA30591C7636941361B8EC0@KL1PR06MB1702.apcprd06.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
> How do i2c-bus gets details of gpio lines associated with i2c bus for bus recovery?
As you can see in the code, you don't need GPIOs if you can control SDA
and SCL directly. The I2C IP can do this.
> On top of renesas-dev branch, I am using the below i2c-rcar driver related patches.
>
> https://www.mail-archive.com/linux-renesas-soc@vger.kernel.org/msg22278.html
Those should be enough. They are not?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-22 12:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 11:29 [PATCH 0/2] Use demuxer for i2c1 and i2c5 Biju Das
2018-01-22 11:29 ` [PATCH vY 1/2] ARM: dts: iwg22d-sodimm-dbhd-ca: use demuxer for I2C1 Biju Das
2018-01-22 11:29 ` [PATCH vY 2/2] ARM: dts: iwg22d-sodimm: use demuxer for I2C5 Biju Das
2018-01-22 11:40 ` [PATCH 0/2] Use demuxer for i2c1 and i2c5 Wolfram Sang
2018-01-22 11:55 ` Biju Das
2018-01-22 12:22 ` Wolfram Sang [this message]
2018-01-22 14:03 ` Biju Das
2018-01-22 14:08 ` Wolfram Sang
2018-01-23 13:39 ` Biju Das
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=20180122122204.n25jf2rtaoxmi2yq@katana \
--to=wsa@the-dreams.de \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.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).