From: Tony Lindgren <tony@atomide.com>
To: Greg Knight <g.knight@symetrica.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Patch to parameterize DMA_MIN_BYTES for omap2-mcspi
Date: Wed, 18 Mar 2015 13:31:01 -0700 [thread overview]
Message-ID: <20150318203100.GV31346@atomide.com> (raw)
In-Reply-To: <1426707461.13824.2.camel@symus-gk-mint>
Hi Greg,
* Greg Knight <g.knight@symetrica.com> [150318 12:38]:
> Hi, linux-omap,
>
> I've attached a patch which adds a device-tree field "ti,dma-min-bytes"
> which replaces the macro DMA_MIN_BYTES. Adjusting this field addresses
> issues we've had where, in our particular use case, the usleep() in the
> SPI worker thread eats a full 20% of our CPU (AM3359).
>
> I opted to implement it as a device-tree parameter and keep the original
> value (160) as the default, in order to avoid impacting anyone else.
>
> The patch is attached. Patches 1-2 are an unrelated McASP change (see my
> other message).
>
> What is the process for getting this upstreamed?
Well I suggest you run get_maintainer.pl on your patches to figure
out who to send them to for review. For example this one:
$ scripts/get_maintainer.pl -f drivers/spi/spi-omap2-mcspi.c
Mark Brown <broonie@kernel.org> (maintainer:SPI SUBSYSTEM)
linux-spi@vger.kernel.org (open list:SPI SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)
Also you might want to run scripts/checkpatch.pl --strict on them
to sort out any formatting issues etc.
And if it's omap related patch, please cc also the linux-omap
mailing list too.
That's pretty much all that's needed, then just update the patches
baded on people's comments :) Good idea to fix up these issues
in the upstream kernel.
Regards,
Tony
next prev parent reply other threads:[~2015-03-18 20:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 19:37 Patch to parameterize DMA_MIN_BYTES for omap2-mcspi Greg Knight
2015-03-18 20:31 ` Tony Lindgren [this message]
[not found] ` <CAAQQ3umQu=Zh6MC=uXTxzbXGgm48KY6KQTPo4=f=0cVy+FFv-Q@mail.gmail.com>
2015-03-18 22:01 ` Tony Lindgren
2015-03-18 22:04 ` Greg Knight
-- strict thread matches above, loose matches on Subject: below --
2015-03-19 5:05 Greg Knight
2015-03-19 9:47 ` Mark Brown
2015-03-19 12:34 ` Peter Ujfalusi
2015-03-19 13:16 ` Greg Knight
[not found] ` <CAAQQ3un3k-0nY8xaOXKbmCznOk69ZEhbWLd5ZZV1_=rQLOyspg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-19 14:03 ` Mark Brown
2015-03-19 16:23 ` Peter Ujfalusi
[not found] ` <550AF7F6.7080200-l0cyMroinI0@public.gmane.org>
2015-03-19 17:28 ` Greg Knight
2015-03-19 18:51 ` Mark Brown
2015-03-20 13:10 ` Peter Ujfalusi
[not found] ` <550C1C2C.5080204-l0cyMroinI0@public.gmane.org>
2015-03-22 16:31 ` Mark Brown
2015-03-20 12:58 ` Peter Ujfalusi
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=20150318203100.GV31346@atomide.com \
--to=tony@atomide.com \
--cc=g.knight@symetrica.com \
--cc=linux-omap@vger.kernel.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).