From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V5 2/4] serial: Add Tegra2 serial port support
Date: Mon, 24 Jan 2011 13:14:45 -0600 [thread overview]
Message-ID: <1295896485.2045.237.camel@petert> (raw)
In-Reply-To: <AANLkTi=uPxZUEeO52EJgQALWL0hznkdGvtdRzMMwibNp@mail.gmail.com>
<snip>
> I see what you're talking about now - I've got uart.c in 2 patch files - created
> in 0001 and then moved in 0002. My bad - that wasn't the intent, just what
> happened when I applied my V4 patches to a new branch to get the V5 patchset
> built. I'll fix it and resubmit.
>
> As to 0002 not adding serial port support for Tegra2, that's all it does - adds
> TEGRA2 defines to serial.h/serial.c for the eserial* tables, and then adds
> code to turn on Tegra2-specific UART HW. If I remove any mention of uart.c
> in patch 0001 (add basic Tegra2 support), then does patch 0002 make
> sense to you?
Yeah, that'd make more sense. Patch 2 would just contain:
common/serial.c | 3 +-
drivers/serial/Makefile | 1 +
drivers/serial/serial_tegra2.c | 205 ++++++++++++++++++++++++++++++++++
drivers/serial/serial_tegra2.h | 49 ++++++++
include/serial.h | 3 +-
> >> > <snip>
> >> >
> >> > +void uart_init(void)
> >> >> +{
> >> >> + /* Init each UART - there may be more than 1 on a board/build */
> >> >> +#if (CONFIG_TEGRA2_ENABLE_UARTA)
> >> >> + init_uart();
> >> >> +#endif
> >> >> +#if (CONFIG_TEGRA2_ENABLE_UARTD)
> >> >> + init_uart();
> >> >> +#endif
> >> >> +}
> >> >
> >> > How about:
> >> > #if defined(CONFIG_TEGRA2_ENABLE_UARTA) || defined(CONFIG_TEGRA2_ENABLE_UARTD)
> >> > init_uart();
> >> > #endif
> >> That won't work for a board like Harmony where the developer wants
> >> both UARTs active, since uart_init is only called once.
> >
> > Why should init_uart() be called two times? It looks to initialize both
> > ports, meaning it should only be called once, right?
> Correct, again (need more coffee!) Your if defined construct wouldn't work
> as written, though, because CONFIG_TEGRA2_ENABLE_UARTx is always
> defined (as 0 or 1). I'd have to rework it.
You could also just get rid of uart_init() altogether and rename
init_uart() to uart_init(). That would get rid of some idefs and
simplify the flow.
Best,
Peter
next prev parent reply other threads:[~2011-01-24 19:14 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 [this message]
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
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=1295896485.2045.237.camel@petert \
--to=ptyser@xes-inc.com \
--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