From: Govindraj <govindraj.ti@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Cc: "Govindraj.R" <govindraj.raja@ti.com>,
linux-omap@vger.kernel.org, linux-serial@vger.kernel.org,
Kevin Hilman <khilman@deeprootsystems.com>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH v3] serial: Add OMAP high-speed UART driver
Date: Mon, 7 Jun 2010 18:58:51 +0530 [thread overview]
Message-ID: <AANLkTimEtn-ef4ygY2Cu3ay4vAGHpCwtxrf8U9nW9NV8@mail.gmail.com> (raw)
In-Reply-To: <201006070809.47853.luke@dashjr.org>
On Mon, Jun 7, 2010 at 6:39 PM, Luke-Jr <luke@dashjr.org> wrote:
> On Monday 07 June 2010 01:49:05 am Govindraj wrote:
>> Hope your are trying to use Kevins Wip-UART branch.
>> Since platform data support is currently available in that branch.
>
> Nope... Google doesn't seem to know where this branch is, either. :/
Link:
http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git;a=summary
Branch:
pm-wip/uart
>
>> ensure you have selected omap-serial driver
>
> I'm not using it for console, anyway.
>
If you are trying to use with any client device connected to uart
then we need to ensure the client driver speaks to omap-serial
dev entries.
The client device application may be designed to speak to
8250 entries probably you may need to check.
In that case you need to change device name to that of 8250
so that no change is needed in application though and in that way
we make it to speak with omap-serial.
---
Regards,
Govindraj.R
next prev parent reply other threads:[~2010-06-07 13:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 13:54 [PATCH v3] serial: Add OMAP high-speed UART driver Govindraj.R
2010-06-05 18:48 ` Luke-Jr
2010-06-07 6:49 ` Govindraj
2010-06-07 13:09 ` Luke-Jr
2010-06-07 13:28 ` Govindraj [this message]
2010-06-07 16:15 ` Luke-Jr
2010-06-08 6:30 ` Govindraj
2010-07-07 12:02 ` Tony Lindgren
2010-07-07 12:22 ` Govindraj
2010-08-09 19:29 ` Kevin Hilman
2010-08-11 13:10 ` Govindraj
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=AANLkTimEtn-ef4ygY2Cu3ay4vAGHpCwtxrf8U9nW9NV8@mail.gmail.com \
--to=govindraj.ti@gmail.com \
--cc=govindraj.raja@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=luke@dashjr.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;
as well as URLs for NNTP newsgroup(s).