linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier.adi@gmail.com>
To: Sonic Zhang <sonic.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 02:24:16 -0400	[thread overview]
Message-ID: <8bd0f97a0909172324j32331e6ele1435cd93de188c@mail.gmail.com> (raw)
In-Reply-To: <4e5ebad50909172154m3c6450f2u7512f20ee3f1951e@mail.gmail.com>

On Fri, Sep 18, 2009 at 00:54, Sonic Zhang wrote:
> On Thu, Sep 17, 2009 at 2:56 AM, Mike Frysinger wrote:
>> On Wed, Sep 16, 2009 at 06:02, sonic zhang wrote:
>>> 3. Move most platform data into arch specific board files.
>>
>> might as well do it right now since you've done most of it already.
>> i.e. all of the peripheral logic should be in the boards, not the
>> driver.  so the bfin_uart_pin_req_sportx lists should get moved to the
>> platform resources as well as the SPORT base addresses.
>
> No. You can't. Because the console is registered and running much
> earlier than the platform data is initialized. You have to know the
> peripheral lists and base address before registering the console.

this is why the early_platform_driver framework was created.  i was
looking into adding this to the Blackfin serial driver.  check out
Documentation/driver-model/platform.txt.

>>> Signed-off-by: Michael Frysinger <michael.frysinger@analog.com>
>>
>> you shouldnt add s-o-b tags for people who didnt opt for them ... i
>> was sleeping when you wrote, committed, and e-mailed out these
>> changes.  i also handt posted these changes yet because i knew there
>> were still issues to be worked out.
>
> OK. I mean you also did some cleanup to this patch.

well once we get these issues hashed out, i'm happy to say the code is
good stuff ;)
-mike
--
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

      parent reply	other threads:[~2009-09-18  6:24 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
2009-09-18  6:24     ` Mike Frysinger [this message]

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=8bd0f97a0909172324j32331e6ele1435cd93de188c@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=sonic.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).