linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier.adi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Feng Tang <feng.tang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	alek.du-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	Dirk Brandewie
	<dirk.brandewie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
	<spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	alan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org
Subject: Re: [PATCH v2] spi: reorganize drivers
Date: Tue, 7 Jun 2011 00:48:49 -0400	[thread overview]
Message-ID: <BANLkTimOnT-McWYp9ym6nZSPsDWQVKCUBQ@mail.gmail.com> (raw)
In-Reply-To: <20110607124854.0e96813c@feng-i7>

On Tue, Jun 7, 2011 at 00:48, Feng Tang wrote:
> On Tue, 7 Jun 2011 12:09:52 +0800 Grant Likely wrote:
>> On Mon, Jun 6, 2011 at 8:28 PM, Feng Tang wrote:
>> > On Tue, 7 Jun 2011 00:49:20 +0800 Dirk Brandewie wrote:
>> >> 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.

sounds like if there are multiple CPUs with this IP being added to
them, then perhaps a top level MAINTAINERS entry should be added so
interested parties can easily be located ... or listing in the
drivers/spi/Kconfig under the designware entry ... or a listing in the
designware spi driver itself ...
-mike

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
spi-devel-general mailing list
spi-devel-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/spi-devel-general

  reply	other threads:[~2011-06-07  4:48 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
     [not found]           ` <BANLkTim927Ld28JmVfALscThef02XQJDWw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-07  4:48             ` Feng Tang
2011-06-07  4:48               ` Mike Frysinger [this message]
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=BANLkTimOnT-McWYp9ym6nZSPsDWQVKCUBQ@mail.gmail.com \
    --to=vapier.adi-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=alan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
    --cc=alek.du-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=dirk.brandewie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=feng.tang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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).