From: Laxman Dewangan <ldewangan@nvidia.com>
To: Prashant Gaikwad <pgaikwad@nvidia.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] ARM: tegra30: Add support for Uart clock source divider as 15.1
Date: Tue, 18 Dec 2012 18:35:37 +0530 [thread overview]
Message-ID: <50D06A21.2000102@nvidia.com> (raw)
In-Reply-To: <50D0163F.3030806@nvidia.com>
On Tuesday 18 December 2012 12:37 PM, Prashant Gaikwad wrote:
> On Tuesday 18 December 2012 11:54 AM, Laxman Dewangan wrote:
>> On Tuesday 18 December 2012 11:44 AM, Prashant Gaikwad wrote:
>>>
>>> My clock driver rework includes this fix. Divider supports both DIVU71
>>> and DIVU151.
>>> UART divider is set to DIVU151.
>> Prashant,
>> I like to go this patch as first patch towards bug fixes rather than
>> after moving the clock. The reason is that we will pull this change in
>> our downstream and will be available in our K3.7 code.
> Laxman,
>
> We are not going to use ccf in our downstream kernel port to K3.7. How
> does that help pushing in upstream?
Ok, as per our internal discussion, I am going to drop first three
patches. I will relookinto these patches once your series get applied
and will work if there is any missing items.
Stephen,
I will respin the 4th patch based on how the discussion on serial driver
goes. I will send the new patch for 4th change.
next prev parent reply other threads:[~2012-12-18 13:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 12:08 [PATCH 0/4] ARM: tegra: add support for highspeed serial driver Laxman Dewangan
2012-12-17 12:08 ` [PATCH 1/4] ARM: tegra30: Add support for Uart clock source divider as 15.1 Laxman Dewangan
[not found] ` <1355746101-15291-2-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-17 21:43 ` Stephen Warren
[not found] ` <50CF91F7.5010402-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-18 6:14 ` Prashant Gaikwad
[not found] ` <50D009E0.3050409-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-18 6:24 ` Laxman Dewangan
[not found] ` <50D00C1D.9090100-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-18 7:07 ` Prashant Gaikwad
2012-12-18 13:05 ` Laxman Dewangan [this message]
2012-12-17 12:08 ` [PATCH 2/4] ARM: tegra: add connection name for uart clock table Laxman Dewangan
[not found] ` <1355746101-15291-3-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-17 21:44 ` Stephen Warren
[not found] ` <50CF9233.3010506-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-18 7:05 ` Laxman Dewangan
2012-12-18 16:55 ` Stephen Warren
2012-12-17 12:08 ` [PATCH 3/4] ARM: tegra: Add OF_DEV_AUXDATA for uart driver in board dt Laxman Dewangan
2012-12-17 21:47 ` Stephen Warren
[not found] ` <50CF92D5.6090805-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-18 6:18 ` Prashant Gaikwad
[not found] ` <50D00AB9.8090800-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-18 7:00 ` Laxman Dewangan
2012-12-17 12:08 ` [PATCH 4/4] ARM: tegra: dts: add dma requestor and port numbers for serial controller Laxman Dewangan
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=50D06A21.2000102@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pgaikwad@nvidia.com \
--cc=swarren@wwwdotorg.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).