From: Chanho Min <chanho.min@lge.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Cox <alan@linux.intel.com>,
linux-kernel@vger.kernel.org, Pawel Moll <pawel.moll@arm.com>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v2] ARM: PL011: Add support for Rx DMA buffer polling
Date: Wed, 30 Jan 2013 09:53:03 +0900 [thread overview]
Message-ID: <CAOAMb1Bf-kB1=HkgMd_w-5v6Wh0XVX4knotiOu5CLKqQg+3X9g@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdZw_Bvz86PeNyoSjFR=O0_KkM6uJBYZ-ZhVy_g0SKun7w@mail.gmail.com>
> Then it can use DMA polling post-wakeup?
Yes, It will be switched back to DMA polling on UART IRQ.
> What do you mean by "user" here? Userspace? Or
> "platform data parameter"?
platform data parameter
> Not platform I think. Per usecase.
> Are you not actually thinking about things like the above?
> These are usecase requirements, not platform requirements.
I mean that:
Platform knows the requirement of it's ports (It can be usecase above)
and can set the poll rate with platform data parameter. Some port is
enough to do with slow poll rate, some need fast poll rate for the fast
response. Of course some port don't need rx dma and polling, in this case
we can set the poll rate to 0. If we fix the poll rate to the scale
of baud rate, we don't have such flexibility.
Anyway I just want to know we still need auto scale of poll rate.
If this become clear, I will prepare v3 of this patch.
Thanks
Chanho
next prev parent reply other threads:[~2013-01-30 0:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 8:15 [PATCH v2] ARM: PL011: Add support for Rx DMA buffer polling Chanho Min
2013-01-28 8:28 ` Linus Walleij
2013-01-29 2:41 ` Chanho Min
2013-01-29 10:57 ` Linus Walleij
2013-01-30 0:53 ` Chanho Min [this message]
2013-01-30 2:53 ` Chanho Min
2013-01-31 20:33 ` Linus Walleij
[not found] <50efad8d.84fc440a.589e.ffff9546SMTPIN_ADDED_BROKEN@mx.google.com>
2013-01-11 18:34 ` [PATCH] " Linus Walleij
[not found] ` <50f107aa.894e420a.596a.ffffe3f6SMTPIN_ADDED_BROKEN@mx.google.com>
2013-01-14 0:04 ` Linus Walleij
2013-01-14 0:26 ` Russell King - ARM Linux
2013-01-14 6:46 ` Linus Walleij
2013-01-14 7:27 ` Chanho Min
2013-01-14 8:41 ` Chanho Min
2013-01-22 12:45 ` [PATCH v2] " Chanho Min
2013-01-22 13:18 ` Linus Walleij
2013-01-23 5:07 ` Chanho Min
2013-01-25 20:25 ` Greg Kroah-Hartman
2013-01-25 21:26 ` Russell King - ARM Linux
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='CAOAMb1Bf-kB1=HkgMd_w-5v6Wh0XVX4knotiOu5CLKqQg+3X9g@mail.gmail.com' \
--to=chanho.min@lge.com \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pawel.moll@arm.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;
as well as URLs for NNTP newsgroup(s).