linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <mike@compulab.co.il>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: linux-omap@vger.kernel.org, Felipe Balbi <balbi@ti.com>
Subject: Re: [PATCH 2/2] Add basic devices support for Nook Color
Date: Thu, 28 Apr 2011 09:14:36 +0300	[thread overview]
Message-ID: <4DB905CC.7030907@compulab.co.il> (raw)
In-Reply-To: <1A637068-3F89-4B73-8A36-5278EB69C8CD@linuxhacker.ru>

(adding Felipe to cc)

Felipe, can you comment on the mUSB part, please?

On 04/27/11 19:12, Oleg Drokin wrote:
> Hello!
> 
>  Thanks for the feedback.
> On Apr 27, 2011, at 4:49 AM, Mike Rapoport wrote:
>>> MMC/SD interface, i2c, usb.
>> You should have added these at the first patch instead of Android devices.
> 
> So, basically you want all board file changes to come as a single patch, right?

I would split you series into three patches:
1) TWL updates
2) addition of board-encore
3) defconfig updates

The patch that adds board-encore would include MMC, i2c and mUSB.

>>> ---
>>> arch/arm/configs/encore-nookcolor-defconfig | 2015 +++++++++++++++++++++++++++
>> The defconfig should be a separate patch. You should rather add encore board
>> options to omap2plus_defconfig.
> 
> Hm, ok.
> 
>>> +static struct i2c_board_info __initdata encore_i2c_bus2_info[] = {
>>> +};
>>> +
>>> +
>>> +static struct omap_musb_board_data musb_board_data = {
>>> +	.interface_type		= MUSB_INTERFACE_ULPI,
>>> +#ifdef CONFIG_USB_MUSB_OTG
>>> +	.mode			= MUSB_OTG,
>>> +#elif defined(CONFIG_USB_MUSB_HDRC_HCD)
>>> +	.mode			= MUSB_HOST,
>>> +#elif defined(CONFIG_USB_GADGET_MUSB_HDRC)
>>> +	.mode			= MUSB_PERIPHERAL,
>>> +#endif
>> This kind of ifdefery is handled inside the musb driver. I'd set the mode to
>> MUSB_OTG unless you want to explicitly limit it to HOST or PERIPHERAL
> 
> Actually it's not.
> If I set MUSB_OTG here and then I choose PERIPHERAL mode in the kernel config,
> the musb transceiver code will complain about board file and kernel config mismatch.
> The Nook Color is advertised as peripheral device, but OTG must be working too
> (not totally working at this point) I think there is value to be able to configure it
> in two different modes.

Frankly, I haven't tried choosing different modes in the kernel config and in
the board data. Still, I believe that board data should define desired operation
mode and the driver should do the best effort to enable the controller in the
desired mode.

> Bye,
>     Oleg


-- 
Sincerely yours,
Mike.

  reply	other threads:[~2011-04-28  6:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27  1:52 Initial B&N Nook Color support green
2011-04-27  1:52 ` [PATCH 1/2] Initial B&N Nook Color (Encore) support green
2011-04-27  8:54   ` Mike Rapoport
2011-04-27  1:52 ` [PATCH 2/2] Add basic devices support for Nook Color green
2011-04-27  8:49   ` Mike Rapoport
2011-04-27 16:12     ` Oleg Drokin
2011-04-28  6:14       ` Mike Rapoport [this message]
2011-04-28 16:10         ` Oleg Drokin
2011-04-29  9:21           ` Felipe Balbi
2011-06-05 20:05             ` back-door musb USB host support Oleg Drokin
2011-06-06  9:30               ` 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=4DB905CC.7030907@compulab.co.il \
    --to=mike@compulab.co.il \
    --cc=balbi@ti.com \
    --cc=green@linuxhacker.ru \
    --cc=linux-omap@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).