From: Kevin Hilman <khilman@deeprootsystems.com>
To: Hemanth V <hemanthv@ti.com>
Cc: linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
David Brownell <david-b@pacbell.net>
Subject: Re: [PATCH 1/2] McSPI Slave and DMA,FIFO support
Date: Thu, 11 Jun 2009 07:47:40 -0700 [thread overview]
Message-ID: <87k53isu7n.fsf@deeprootsystems.com> (raw)
In-Reply-To: <002701c9eaa1$13f13960$LocalHost@wipultra793> (Hemanth V.'s message of "Thu\, 11 Jun 2009 19\:59\:46 +0530")
"Hemanth V" <hemanthv@ti.com> writes:
> ----- Original Message -----
> From: "Hemanth V" <hemanthv@ti.com>
> To: "Tony Lindgren" <tony@atomide.com>
> Cc: <linux-omap@vger.kernel.org>
> Sent: Friday, June 05, 2009 3:28 PM
> Subject: Re: [PATCH 1/2] McSPI Slave and DMA,FIFO support
>
>
>> ----- Original Message -----
>> From: "Tony Lindgren" <tony@atomide.com>
>> To: "Hemanth V" <hemanthv@ti.com>
>> Cc: <linux-omap@vger.kernel.org>
>> Sent: Tuesday, June 02, 2009 11:36 PM
>> Subject: Re: [PATCH 1/2] McSPI Slave and DMA,FIFO support
>>
>>
>>> Hi,
>>>
>>> Sorry for the delay in replying, few comments below.
>>>
>>> * Hemanth V <hemanthv@ti.com> [090519 22:57]:
>>>> This patch adds support for McSPI slave and FIFO. DMA and FIFO
>>>> could be enabled together for better throughput. Platform config
>>>> parameters have been added to enable these features on any particular
>>>> McSPI controller.
>>>>
>>>> FIFO can be enabled by defining fifo_depth parameter. fifo_depth needs
>>>> to be a multiple of buffer size that is used for read/write.
>>>>
>>>> These features are useful when you have high throughput devices
>>>> like WLAN or Modem connected over SPI.
>>>>
>>>> Signed-off-by: Hemanth V <hemanthv@ti.com>
>>>> arch/arm/mach-omap2/devices.c | 5
>>>> arch/arm/plat-omap/include/mach/mcspi.h | 16 +
>>>> drivers/spi/omap2_mcspi.c | 343
>>>> ++++++++++++++++++++++++++++----
>>>> 3 files changed, 325 insertions(+), 39 deletions(-)
>>>
>>> As this is mostly drivers/spi/omap2_mcspi.c, this patch should get
>>> merged via:
>>>
>>> $ grep -A7 "SPI SUBSYSTEM" MAINTAINERS
>>> SPI SUBSYSTEM
>>> P: David Brownell
>>> M: dbrownell@users.sourceforge.net
>>> L: spi-devel-general@lists.sourceforge.net
>>> S: Maintained
>>> F: Documentation/spi/
>>> F: drivers/spi/
>>> F: include/linux/spi/
>>>
>>> Please keep linux-omap list Cc'd too so everybody can follow
>>> the progress.
>>
>> Tony, is this list active. The archives seem to be flooded with spam
>> mails
>>
>> http://sourceforge.net/mailarchive/forum.php?forum_name=spi-devel-general
>>
>>>
>
> Kevin, Can u suggest what is to be done in this situation. spi-devel
> list doesnot seem
> to be active and Tony is not willing to merge this patch. Should I
> send this to LKML
First, you haven't addressed any of the comments made on the list
about your series.
Tony isn't merging this patch because most of it should go via the SPI
subsystem.
A Santosh suggested, you need to break this up into parts that are
OMAP specific (arch/arm/*) and parts that go via the SPI subsystem
(drivers/spi/*.) If doing this breaks your series, then fix it
because if it breaks compile this way, then upstream maintainers will
surely hit the same errors and complain.
David Brownell is the SPI maintainer. I suggest you send to him,
CC'ing linux-omap.
Kevin
next prev parent reply other threads:[~2009-06-11 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 5:56 [PATCH 1/2] McSPI Slave and DMA,FIFO support Hemanth V
2009-05-20 6:04 ` Shilimkar, Santosh
2009-05-20 6:06 ` Hemanth V
2009-05-26 13:48 ` Hemanth V
2009-06-02 18:06 ` Tony Lindgren
2009-06-05 9:58 ` Hemanth V
2009-06-11 14:29 ` Hemanth V
2009-06-11 14:47 ` Kevin Hilman [this message]
2009-06-11 15:44 ` Hemanth V
2009-06-11 16:29 ` Kevin Hilman
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=87k53isu7n.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=david-b@pacbell.net \
--cc=hemanthv@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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