From: Kalle Valo <kalle.valo@iki.fi>
To: "Luke-Jr" <luke@dashjr.org>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-omap\@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Balbi Felipe \(Nokia-D\/Helsinki\)" <felipe.balbi@nokia.com>
Subject: Re: [PATCH] OMAP2: add USB platform data and initialization for Nokia N800 and N810
Date: Tue, 29 Dec 2009 10:29:22 +0200 [thread overview]
Message-ID: <87d41yxjx9.fsf@purkki.valot.fi> (raw)
In-Reply-To: <200912290152.16357.luke@dashjr.org> (Luke-Jr's message of "Tue\, 29 Dec 2009 01\:52\:04 -0600")
"Luke-Jr" <luke@dashjr.org> writes:
> Add platform data and initialization for USB on Nokia N800 and N810 devices
> via the TUSB6010 chipset.
Excellent, thank you for doing this.
> Tested on Nokia N810 in Linux-OMAP tree. Mainline is not bootable yet.
What's the problem in mainline? I haven't tested n8x0 for months :(
> --- a/arch/arm/mach-omap2/Kconfig
> +++ b/arch/arm/mach-omap2/Kconfig
> @@ -117,6 +117,11 @@ config MACH_NOKIA_N8X0
> select MACH_NOKIA_N810
> select MACH_NOKIA_N810_WIMAX
>
> +config MACH_NOKIA_N8X0_USB
> + bool
> + depends on MACH_NOKIA_N8X0 && MACH_OMAP2_TUSB6010
> + default y
> +
Is is really needed to add new kconfig variable? Can't we just use
MACH_OMAP2_TUSB6010 in code?
> --- /dev/null
> +++ b/arch/arm/mach-omap2/board-n8x0-usb.c
I think a separate file is not needed, it's not that much code. I
recommend to just adding it directly to board-n8x0.c. It's simple and
easier for everyone.
> --- a/arch/arm/mach-omap2/board-n8x0.c
> +++ b/arch/arm/mach-omap2/board-n8x0.c
> @@ -109,8 +109,16 @@ static void __init n8x0_init_irq(void)
> omap_gpio_init();
> }
>
> +#ifdef CONFIG_MACH_NOKIA_N8X0_LCD
> +extern void n8x0_usb_init(void);
> +#else
> +static inline void n8x0_usb_init (void) {}
> +#endif
CONFIG_MACH_NOKIA_N8X0_LCD does not look right here.
--
Kalle Valo
next prev parent reply other threads:[~2009-12-29 8:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 7:52 Luke-Jr
2009-12-29 8:29 ` Kalle Valo [this message]
2009-12-29 8:46 ` Luke-Jr
2009-12-29 8:55 ` Kalle Valo
2009-12-29 12:51 ` Felipe Balbi
2009-12-29 21:05 ` Luke-Jr
2009-12-30 3:10 ` Luke-Jr
2009-12-30 7:17 ` Kalle Valo
2009-12-30 9:02 ` Luke-Jr
2009-12-30 12:04 ` Felipe Balbi
2009-12-29 19:24 ` Tony Lindgren
2009-12-29 19:35 ` Felipe Balbi
2009-12-29 19:42 ` Tony Lindgren
2009-12-29 19:49 ` Felipe Balbi
2009-12-29 19:53 ` Tony Lindgren
2009-12-29 19:57 ` Felipe Balbi
2009-12-29 20:28 ` Luke-Jr
2009-12-29 20:35 ` Felipe Balbi
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=87d41yxjx9.fsf@purkki.valot.fi \
--to=kalle.valo@iki.fi \
--cc=felipe.balbi@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=luke@dashjr.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
all inboxes | Powered by JetHome®