From: "Oskar Schirmer" <oskar-fYPSZ7JpQqsAvxtiuMwx3w@public.gmane.org>
To: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-xtensa-PjhNF2WwrV/0Sa2dR60CXw@public.gmane.org,
Chris Zankel <chris-YvXeqwSYzG2sTnJN9+BGXg@public.gmane.org>,
Max Filippov <jcmvbkbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: i2c: removal of s6000 driver
Date: 23 May 2014 13:17:22 +0000 [thread overview]
Message-ID: <20140523131722.GA28143@curry> (raw)
In-Reply-To: <20140521113029.GT2708@katana>
Hi Wolfram,
On Wed, May 21, 2014 at 13:30:29 +0200, Wolfram Sang wrote:
> I recently discovered that the I2C core of the S6000 is basically a
> Designware IP core. For the latter we have a frequently used and updated
> i2c driver while the S6000 driver seems to bitrot. My wish is to remove
> the s6000 driver in favor of the DesignWare one. My question is if there
> is someone who could test such a change on real hardware?
> Grepping through sources, it looks to me like the only candidate in
> mainline is the s6105, yet its defconfig doesn't even have I2C
> activated? Can we remove this driver right away? Am I missing something?
Removing drivers without a replacement tested and running
doesn't make much sense, except one chooses to drop support
for the whole S6 thing right away. Which I don't support.
best regards,
Oskar
next prev parent reply other threads:[~2014-05-23 13:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 11:30 i2c: removal of s6000 driver Wolfram Sang
2014-05-23 13:17 ` Oskar Schirmer [this message]
2014-05-23 13:57 ` Max Filippov
2014-05-23 17:33 ` czankel
[not found] ` <537F8652.1090807-YvXeqwSYzG2sTnJN9+BGXg@public.gmane.org>
2014-05-24 15:47 ` Oskar Schirmer
2014-05-27 22:35 ` Daniel Glöckner
[not found] ` <20140527223557.GA9594-G/SgeDpXzeDLoDKTGw+V6w@public.gmane.org>
2014-06-09 22:06 ` Wolfram Sang
2014-06-11 8:51 ` Daniel Glöckner
2014-07-28 14:43 ` Daniel Glöckner
[not found] ` <20140728144330.GA31207-QdrG9jWwCLEAvxtiuMwx3w@public.gmane.org>
2014-08-09 14:07 ` Wolfram Sang
2014-05-24 10:21 ` 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=20140523131722.GA28143@curry \
--to=oskar-fypsz7jpqqsavxtiumwx3w@public.gmane.org \
--cc=chris-YvXeqwSYzG2sTnJN9+BGXg@public.gmane.org \
--cc=jcmvbkbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-xtensa-PjhNF2WwrV/0Sa2dR60CXw@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).