From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Wolfram Sang <wsa@the-dreams.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/3] i2c: designware: select gpio/default pin when prepare/unprepare recovery
Date: Tue, 18 Sep 2018 16:25:18 +0300 [thread overview]
Message-ID: <8160d36b-2fb5-c037-893c-c23568a9f6ac@linux.intel.com> (raw)
In-Reply-To: <20180917113418.16881f6c@xhacker.debian>
On 09/17/2018 06:34 AM, Jisheng Zhang wrote:
> + DT maintainers
>
> On Mon, 17 Sep 2018 11:29:49 +0800
> Jisheng Zhang <Jisheng.Zhang@synaptics.com> wrote:
>
>> On some platforms, the sda/scl pins are muxed with gpio functions, so
>> they could be used for recovery. Select the gpio/default pin function
>> when prepare/unprepare recovery.
>>
>> Signed-off-by: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
>> ---
>> drivers/i2c/busses/i2c-designware-core.h | 3 +++
>> drivers/i2c/busses/i2c-designware-master.c | 22 ++++++++++++++++++++++
>> 2 files changed, 25 insertions(+)
>>
Acked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
next prev parent reply other threads:[~2018-09-18 13:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 3:26 [PATCH v3 0/3] i2c: designware: select gpio/default pin when prepare/unprepare recovery Jisheng Zhang
2018-09-17 3:27 ` [PATCH v3 1/3] dt-bindings: i2c: designware: add optional gpio recovery properties Jisheng Zhang
2018-09-17 3:32 ` Jisheng Zhang
2018-09-17 3:28 ` [PATCH v3 2/3] dt-bindings: i2c: designware: add optional pinctrl for bus recovery Jisheng Zhang
2018-09-17 3:33 ` Jisheng Zhang
2018-09-17 3:29 ` [PATCH v3 3/3] i2c: designware: select gpio/default pin when prepare/unprepare recovery Jisheng Zhang
2018-09-17 3:34 ` Jisheng Zhang
2018-09-18 13:25 ` Jarkko Nikula [this message]
2018-09-17 3:31 ` [PATCH v3 0/3] " Jisheng Zhang
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=8160d36b-2fb5-c037-893c-c23568a9f6ac@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=Jisheng.Zhang@synaptics.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/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).