From: Sonic Zhang <sonic.adi@gmail.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Serial <linux-serial@vger.kernel.org>
Subject: Re: [PATCH][uart] fit blackfin uart over sport driver into common uart inftrastructure (v2)
Date: Fri, 18 Sep 2009 13:11:50 +0800 [thread overview]
Message-ID: <4e5ebad50909172211s309cfcdbl7edd904178996799@mail.gmail.com> (raw)
In-Reply-To: <4e5ebad50909172154m3c6450f2u7512f20ee3f1951e@mail.gmail.com>
On Fri, Sep 18, 2009 at 12:54 PM, Sonic Zhang <sonic.adi@gmail.com> wrote:
> On Thu, Sep 17, 2009 at 2:56 AM, Mike Frysinger <vapier.adi@gmail.com> wrote:
>>
>> then we get proper device bindings between ttySS# and SPORT# by using
>> the .id field. ttySS0 should always be SPORT0, ttySS1 should always
>> be SPORT1, etc...
>
> You can't either. Because the index of tty devices is increased
> automatically when you successfully register a uart port. If sport0
> is used for devices other than uart, uart over sport1 is always bond
> to ttySS0.
>
>
OK. This looks possible. I will take a look.
Sonic
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-09-18 5:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 10:02 [PATCH][uart] fit blackfin uart over sport driver into common uart inftrastructure (v2) sonic zhang
2009-09-16 18:56 ` Mike Frysinger
2009-09-18 4:54 ` Sonic Zhang
2009-09-18 5:11 ` Sonic Zhang [this message]
2009-09-18 6:24 ` Mike Frysinger
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=4e5ebad50909172211s309cfcdbl7edd904178996799@mail.gmail.com \
--to=sonic.adi@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=vapier.adi@gmail.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).