From: Nishanth Menon <nm@ti.com>
To: "Pandita, Vikram" <vikram.pandita@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Vikram Pandita <vikram.pandtia@ti.com>
Subject: Re: [PATCH 3/8] omap: zoom2: split baord file for reuse
Date: Tue, 3 Nov 2009 16:17:25 -0600 [thread overview]
Message-ID: <4AF0ABF5.2030700@ti.com> (raw)
In-Reply-To: <1257283215-6448-4-git-send-email-vikram.pandita@ti.com>
Pandita, Vikram had written, on 11/03/2009 03:20 PM, the following:
Please fix subject typo:
[PATCH 3/8] omap: zoom2: split baord file for reuse
^^^^
board
[...]
> diff --git a/arch/arm/mach-omap2/board-zoom-peripherals.c b/arch/arm/mach-omap2/board-zoom-peripherals.c
> new file mode 100755
> index 0000000..c799eca
> --- /dev/null
> +++ b/arch/arm/mach-omap2/board-zoom-peripherals.c
generic -> zoom Vs LDP.. Vs Zoom2 Vs Zoom3 naming conventions.. are we
saying we dont care about LDP anymore? all zooms are zoom2 or zoom3?
[...]
> +
> +//static struct twl4030_gpio_platform_data zoom_gpio_data = {
> +// .gpio_base = OMAP_MAX_GPIO_LINES,
> +// .irq_base = TWL4030_GPIO_IRQ_BASE,
> +// .irq_end = TWL4030_GPIO_IRQ_END,
> +// .pulldowns = BIT(0) | BIT(1) | BIT(2) | BIT(3)
> +// | BIT(4) | BIT(5)
> +// | BIT(8) | BIT(9) | BIT(10) | BIT(11)
> +// | BIT(12) | BIT(13) | BIT(14) | BIT(15)
> +// | BIT(16) | BIT(17) ,
> +// .setup = zoom_twlgpio_setup,
> +//};
NAK to //
> +static struct twl4030_gpio_platform_data zoom_gpio_data = {
> + .gpio_base = OMAP_MAX_GPIO_LINES,
> + .irq_base = TWL4030_GPIO_IRQ_BASE,
> + .irq_end = TWL4030_GPIO_IRQ_END,
> + .setup = zoom_twl_gpio_setup,
> +};
> +
> +static struct twl4030_usb_data zoom_usb_data = {
> + .usb_mode = T2_USB_MODE_ULPI,
> +};
> +
> +/* TODO: enable T2 scripts */
> +#if 0
NAK to #if 0 - introduce seperately if not operational.
[...]
> diff --git a/arch/arm/mach-omap2/board-zoom2.c b/arch/arm/mach-omap2/board-zoom2.c
> old mode 100644
> new mode 100755
> index 4ad9b94..abcc1ae
> --- a/arch/arm/mach-omap2/board-zoom2.c
> +++ b/arch/arm/mach-omap2/board-zoom2.c
> @@ -1,8 +1,6 @@
> /*
> * Copyright (C) 2009 Texas Instruments Inc.
> - * Mikkel Christensen <mlc@ti.com>
> *
> - * Modified from mach-omap2/board-ldp.c
[Should we loose the history?]
[...]
> -static void __init omap_zoom2_init_irq(void)
> +static void __init omap_zoom_init_irq(void)
Question on naming.. as raised above.
[...]
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2009-11-03 22:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 21:20 [PATCH 0/8] RFC: introduce 3630 boards Vikram Pandita
2009-11-03 21:20 ` [PATCH 1/8] omap: 3630: update is_chip variable Vikram Pandita
2009-11-03 21:20 ` [PATCH 2/8] omap: DEBUG_LL: allow no omap uart configuration Vikram Pandita
2009-11-03 21:20 ` [PATCH 3/8] omap: zoom2: split baord file for reuse Vikram Pandita
2009-11-03 21:20 ` [PATCH 4/8] omap: zoom2: update defconfig Vikram Pandita
2009-11-03 21:20 ` [PATCH 5/8] omap: zoom3: introduce zoom3 board support Vikram Pandita
2009-11-03 21:20 ` [PATCH 6/8] omap: zoom3: defconfig creation Vikram Pandita
2009-11-03 21:20 ` [PATCH 7/8] omap: 3630sdp: introduce 3630 sdp board support Vikram Pandita
2009-11-03 21:20 ` [PATCH 8/8] omap: 3630sdp: defconfig creation Vikram Pandita
2009-11-03 22:31 ` [PATCH 7/8] omap: 3630sdp: introduce 3630 sdp board support Nishanth Menon
2009-11-03 22:28 ` [PATCH 5/8] omap: zoom3: introduce zoom3 " Nishanth Menon
2009-11-04 7:09 ` [PATCH 4/8] omap: zoom2: update defconfig G, Manjunath Kondaiah
2009-11-03 22:17 ` Nishanth Menon [this message]
2009-11-03 22:09 ` [PATCH 2/8] omap: DEBUG_LL: allow no omap uart configuration Nishanth Menon
2009-11-03 21:23 ` [PATCH 0/8] RFC: introduce 3630 boards Pandita, Vikram
2009-11-03 21:26 ` Pandita, Vikram
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=4AF0ABF5.2030700@ti.com \
--to=nm@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=vikram.pandita@ti.com \
--cc=vikram.pandtia@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.