From: marvin24@gmx.de (Marc Dietrich)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: tegra: paz00: add support serial port on JP1
Date: Sat, 16 Jul 2011 17:59:25 +0200 [thread overview]
Message-ID: <20110716175925.64a56617@ac100.localdomain> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF049E834C23@HQMAIL01.nvidia.com>
Am Fri, 15 Jul 2011 09:39:36 -0700
schrieb Stephen Warren <swarren@nvidia.com>:
> Marc Dietrich wrote at Friday, July 15, 2011 4:24 AM:
> > UART-A is connected to JP1 and used by the bootloader for debugging
> > output while UART-D is connected to the mini-pcie expansion slot.
> >
> > Signed-off-by: Marc Dietrich <marvin24@gmx.de>
> > ---
> > arch/arm/mach-tegra/board-paz00.c | 11 +++++++++++
> > 1 files changed, 11 insertions(+), 0 deletions(-)
> >
> > diff --git a/arch/arm/mach-tegra/board-paz00.c
> > b/arch/arm/mach-tegra/board-paz00.c index 1b076f6..931b06e 100644
> > --- a/arch/arm/mach-tegra/board-paz00.c
> > +++ b/arch/arm/mach-tegra/board-paz00.c
> > @@ -47,7 +47,17 @@
> > #include "gpio-names.h"
> >
> > static struct plat_serial8250_port debug_uart_platform_data[] = {
> > +/* serial port on JP1 */
> > {
>
> Shouldn't the indentation of the comment be aligned to the brace?
ok, seems to be the common kernel style. Will be fixed in V2.
> I'm not sure if the order of entries in the array matters. It'd
> presumably be safer to add the new UART entry to the end of the array
> so that any existing index-based number isn't changed.
yeah, it will change the numbering, but none I know of used the serial
interface of the mini-pcie and it makes some sense to have the
bootloader output on number 0.
> > + .membase = IO_ADDRESS(TEGRA_UARTA_BASE),
> > + .mapbase = TEGRA_UARTA_BASE,
> > + .irq = INT_UARTA,
> > + .flags = UPF_BOOT_AUTOCONF,
> > + .iotype = UPIO_MEM,
> > + .regshift = 2,
> > + .uartclk = 216000000,
> > + }, {
> > +/* serial port on mini-pcie */
> > .membase = IO_ADDRESS(TEGRA_UARTD_BASE),
> > .mapbase = TEGRA_UARTD_BASE,
> > .irq = INT_UARTD,
> > @@ -137,6 +147,7 @@ static void __init tegra_paz00_fixup(struct
> > machine_desc *desc,
> >
> > static __initdata struct tegra_clk_init_table
> > paz00_clk_init_table[] = { /* name
> > parent rate enabled */
> > + { "uarta", "pll_p", 216000000, true },
> > { "uartd", "pll_p", 216000000, true },
> > { NULL, NULL,
> > 0, 0}, };
> > --
> > 1.7.4.1
>
next prev parent reply other threads:[~2011-07-16 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 10:24 [PATCH 0/3] ARM: tegra: paz00: Add Wifi and second serial port support Marc Dietrich
2011-07-15 10:24 ` [PATCH 1/3] ARM: tegra: paz00: add support serial port on JP1 Marc Dietrich
2011-07-15 16:39 ` Stephen Warren
2011-07-16 15:59 ` Marc Dietrich [this message]
2011-07-15 10:24 ` [PATCH 2/3] ARM: tegra: paz00: export the WIFI rfkill gpio Marc Dietrich
2011-07-15 12:17 ` Vasily Khoruzhick
2011-07-22 20:38 ` Marc Dietrich
2011-07-15 16:53 ` Stephen Warren
2011-07-15 17:25 ` Sergei Shtylyov
2011-07-15 17:30 ` Stephen Warren
2011-07-15 10:24 ` [PATCH 3/3] ARM: tegra: paz00: enable wifi led Marc Dietrich
2011-07-15 17:10 ` Stephen Warren
2011-07-16 16:19 ` Marc Dietrich
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=20110716175925.64a56617@ac100.localdomain \
--to=marvin24@gmx.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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