From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Phil Reid <preid@electromag.com.au>, Tim Sander <tim@krieglstein.org>
Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c-designware: add i2c gpio recovery option
Date: Thu, 11 May 2017 17:02:56 +0300 [thread overview]
Message-ID: <1494511376.6967.13.camel@linux.intel.com> (raw)
In-Reply-To: <1494510791.6967.9.camel@linux.intel.com>
On Thu, 2017-05-11 at 16:53 +0300, Andy Shevchenko wrote:
> On Thu, 2017-05-11 at 09:24 +0800, Phil Reid wrote:
> I have briefly looked at the current code.
> So, my suggestion is to switch to gpio descriptors in current code and
> then rebase your stuff on top.
For better transition it might be worth to create gpiod_ support in
parallel with existing and convert existing clients case-by-case if
needed, while discourage people to use gpio_ API.
> I wouldn't encourage people to continue using legacy GPIO API.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-05-11 14:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 15:43 RFC: i2c designware gpio recovery Tim Sander
2017-04-28 16:14 ` Tim Sander
2017-05-01 1:57 ` Phil Reid
2017-05-01 13:31 ` Tim Sander
2017-05-03 1:30 ` Phil Reid
2017-05-03 19:04 ` Tim Sander
2017-05-10 7:12 ` Phil Reid
2017-05-10 11:57 ` [PATCH] i2c-designware: add i2c gpio recovery option Tim Sander
2017-05-10 13:13 ` Andy Shevchenko
2017-05-11 1:24 ` Phil Reid
2017-05-11 13:53 ` Andy Shevchenko
2017-05-11 14:02 ` Andy Shevchenko [this message]
2017-05-12 1:49 ` Phil Reid
2017-05-12 10:17 ` Andy Shevchenko
2017-05-01 2:15 ` RFC: i2c designware gpio recovery Phil Reid
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=1494511376.6967.13.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=preid@electromag.com.au \
--cc=tim@krieglstein.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).