From: Mike Rapoport <mike@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V5 2/4] serial: Add Tegra2 serial port support
Date: Thu, 27 Jan 2011 09:41:10 +0200 [thread overview]
Message-ID: <4D412196.8050702@compulab.co.il> (raw)
In-Reply-To: <AANLkTinKoZ4mjqkemNf8LfywLRMWe34ehVaMC01swRSp@mail.gmail.com>
Tom,
On 01/26/11 19:05, Tom Warren wrote:
> Mike,
>
> On Wed, Jan 26, 2011 at 1:13 AM, Mike Rapoport <mike@compulab.co.il> wrote:
>> My point was that pin muxing belongs to the board code rather than to the
>> driver. Driver should just assume that pins are configured elsewhere and it does
>> not need to deal with pin muxing at all.
> I understand that point - sorry if I wasn't clear. No objection to
> having pinmux code in board files.
>
>> Moreover, I'd prefer to see pinmux_board_init or something similar that
>> configures all the pins at once rather than collection of pinmux_init_uart,
>> pinmux_init_sdmmc, pinmux_init_gmi etc that will grow as more drivers are added.
>>
> I see a couple of reasons not to do it that way. First, I don't know
> at this time what all the pinmux settings will be, since I haven't
> ported all the periph driver code yet. It's vastly different from
> what's acceptable in U-Boot, and will all need significant rewrite.
> It'd take me a week to gather all that info, and I'm not at full BW on
> this project (one of 4 on my plate right now).
> Second, I've been chastised before for including code/features in this
> initial patchset that aren't needed or used. I'm trying to keep the
> code as simple as possible to make it easier on reviewers and get
> through the review in as short a time as possible. This has already
> dragged on far longer than I thought it would.
> I'm willing to change the pinmux code to make it as generic as
> possible, but only if there's a consensus on the list that it has to
> be that way to get accepted & pushed.
I'm Ok with pinmux_init_uart in the board code for now. I think that the generic
pinmux functionality can be added afterwards.
>>
> Thanks,
> Tom
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2011-01-27 7:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 23:06 [U-Boot] [PATCH V5 0/4] Add basic NVIDIA Tegra2 SoC support Tom Warren
2011-01-21 23:06 ` [U-Boot] [PATCH V5 1/4] arm: Tegra2: " Tom Warren
2011-01-24 18:58 ` Wolfgang Denk
2011-01-21 23:06 ` [U-Boot] [PATCH V5 2/4] serial: Add Tegra2 serial port support Tom Warren
2011-01-21 23:46 ` Peter Tyser
2011-01-24 17:32 ` Tom Warren
2011-01-24 17:51 ` Peter Tyser
2011-01-24 18:05 ` Tom Warren
2011-01-24 19:09 ` Wolfgang Denk
2011-01-24 19:14 ` Peter Tyser
2011-01-24 20:15 ` Tom Warren
2011-01-24 19:05 ` Wolfgang Denk
2011-01-25 8:11 ` Mike Rapoport
2011-01-25 16:50 ` Tom Warren
2011-01-25 21:12 ` Mike Rapoport
2011-01-25 21:37 ` Tom Warren
2011-01-25 22:11 ` Tom Warren
2011-01-25 22:24 ` Peter Tyser
2011-01-26 8:13 ` Mike Rapoport
2011-01-26 15:58 ` Peter Tyser
2011-01-27 7:54 ` Mike Rapoport
2011-01-26 17:05 ` Tom Warren
2011-01-27 7:41 ` Mike Rapoport [this message]
2011-01-27 16:08 ` Tom Warren
2011-01-21 23:06 ` [U-Boot] [PATCH V5 3/4] arm: Tegra2: Add support for NVIDIA Harmony board Tom Warren
2011-01-21 23:06 ` [U-Boot] [PATCH V5 4/4] arm: Tegra2: Add support for NVIDIA Seaboard board Tom Warren
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=4D412196.8050702@compulab.co.il \
--to=mike@compulab.co.il \
--cc=u-boot@lists.denx.de \
/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