From: Feng Tang <feng.tang@intel.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Dirk Brandewie <dirk.brandewie@gmail.com>,
"spi-devel-general@lists.sourceforge.net"
<spi-devel-general@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mike Frysinger <vapier.adi@gmail.com>, <alek.du@intel.com>,
<alan@linux.intel.com>, <jean-hugues.deschenes@octasic.com>
Subject: Re: [PATCH v2] spi: reorganize drivers
Date: Tue, 7 Jun 2011 12:48:54 +0800 [thread overview]
Message-ID: <20110607124854.0e96813c@feng-i7> (raw)
In-Reply-To: <BANLkTim927Ld28JmVfALscThef02XQJDWw@mail.gmail.com>
Hi Grant,
On Tue, 7 Jun 2011 12:09:52 +0800
Grant Likely <grant.likely@secretlab.ca> wrote:
> On Mon, Jun 6, 2011 at 8:28 PM, Feng Tang <feng.tang@intel.com> wrote:
> > On Tue, 7 Jun 2011 00:49:20 +0800
> > Dirk Brandewie <dirk.brandewie@gmail.com> wrote:
> >
> >> On 06/06/2011 09:38 AM, Grant Likely wrote:
> >> > On Mon, Jun 6, 2011 at 10:31 AM, Mike
> >> > Frysinger<vapier.adi@gmail.com> wrote:
> >> >> On Mon, Jun 6, 2011 at 03:18, Grant Likely wrote:
> >> >>> Sort the SPI makefile and enforce the naming convention spi_*.c
> >> >>> for spi drivers.
> >> >>
> >> >> spi_topcliff_pch.c uses KBUILD_MODNAME with a few funcs, but
> >> >> perhaps those are only for /proc/ status tracking ? worth
> >> >> double checking ...
> >> >
> >> > I just talked with Dirk Brandewie, who has a major rewrite to the
> >> > topcliff spi driver. I'll let him comment on whether or not
> >> > changing KBUILD_MODNAME will cause any problems.
> >> >
> >>
> >> My changes are to the designware driver :-) I will get my patches
> >> re-based onto the spi-next branch and see if there any issues.
> >
> > If there is major rewrite to the dw_spi driver, please submit to
> > this list, as it is used by many devices out there and needs a
> > broad review
>
> Hmmm. Dirk, that could change things a bit. From our conversation
> today my understanding was that there weren't few if any users outside
> of your circle. If that isn't the case, then I'm going to be more
> cautious about merging the rewrite. Who are the people I should make
> sure there is feedback from when the patch gets posted?
I don't know all the devices and users, but here is what I know: I've tested
Max3110 spi-uart (in-tree), Option GTM501L high-speed 3G modem (out of tree),
ektf1236 spi touch screen (out of tree). Alek Du (Cced) should have tested
current dw_spi driver with some spi bluetooth device and modem device. Also
the original author fordw_spi_mmio.c Jean-Hugues Deschense should have some
experience too.
Thanks,
Feng
>
> g.
next prev parent reply other threads:[~2011-06-07 4:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 7:18 [PATCH v2] spi: reorganize drivers Grant Likely
2011-06-06 7:27 ` Wolfram Sang
2011-06-06 16:31 ` Mike Frysinger
2011-06-06 16:38 ` Grant Likely
2011-06-06 16:49 ` Dirk Brandewie
2011-06-06 16:52 ` Grant Likely
2011-06-07 4:32 ` Tomoya MORINAGA
2011-06-07 4:36 ` Mike Frysinger
2011-06-07 2:28 ` Feng Tang
2011-06-07 4:09 ` Grant Likely
2011-06-07 4:48 ` Feng Tang [this message]
2011-06-07 4:48 ` Mike Frysinger
2011-06-07 4:52 ` Du, Alek
2011-06-07 17:01 ` Grant Likely
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=20110607124854.0e96813c@feng-i7 \
--to=feng.tang@intel.com \
--cc=alan@linux.intel.com \
--cc=alek.du@intel.com \
--cc=dirk.brandewie@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=jean-hugues.deschenes@octasic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=vapier.adi@gmail.com \
/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