public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Krivoschekov <dmitry.krivoschekov@gmail.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: "felipe.balbi@nokia.com" <felipe.balbi@nokia.com>,
	ext Tony Lindgren <tony@atomide.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/4] usb: musb: musb on omap3 has 32 endpoints
Date: Wed, 25 Jun 2008 18:42:57 +0400	[thread overview]
Message-ID: <48625971.8060800@gmail.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB022BE46969@dbde02.ent.ti.com>

apologies for being late with my comment, and it might be not directly
related  to the initial patch but,

Gadiyar, Anand wrote:
>>>> Fix hdrc_cnf.h for omap3 configuration.
>>> Does this break the configuration for omap2?
>>>
>>> We should set these dynamically if different for omap2 and omap3
>>> so we can compile both into the same kernel.
>> Should check omap2430 trm to be sure, maybe someone in TI
>> could help us with it ?
>
> It won't break the 2430. The 2430 has 32 endpoints as well.
to be more precise, OMAP2430 has 1 control + 15 TX + 15 RX endpoints,
i.e.total of 31 eps.

To me it's not clear if these TX/RX endpoints is really independent.  In
other words,  is it
really possible to schedule for example 1st TX and 1st RX endpoint at
the same time (in the same USB frame)?

If you look at Felipe's patch, it changes a total number of eps from 8
to 16. In my understanding the driver is now able to schedule only this
number of endpoints. That is, the driver consider both 1TX and 1RX
endpoints as the same endpoint that is able to operate for Tx and Rx.
And, the driver can use only 16 endpoints at the same time, not 31.

But if all those 15Tx and 15Rx eps are mutually independent then it
makes sense to treat them in another way, MUSB_C_NUM_EPS should be 31
plus appropriate modifications to the driver are needed.


Of course I may be missing something, please correct me if I'm wrong
with my conclusions.


Thanks,
Dmitry
>
>
>> Maybe we could bring it via platform_data as well?
>
> Yep. That would be good.
>
> - Anand
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  parent reply	other threads:[~2008-06-25 14:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13 10:03 [PATCH 0/4] more musb/i2c patches Felipe Balbi
2008-06-13 10:04 ` [PATCH 1/4] usb: musb: musb on omap3 has 32 endpoints Felipe Balbi
2008-06-13 10:04   ` [PATCH 2/4] usb: musb: add MODULE_ALIAS for udev module loading Felipe Balbi
2008-06-13 10:04     ` [PATCH 3/4] i2c: allow twl modules to be built as modules Felipe Balbi
2008-06-13 10:04       ` [PATCH 4/4] i2c: add MODULE_ALIAS to twl4030 drivers Felipe Balbi
2008-06-23 11:11         ` Tony Lindgren
2008-06-23 11:11       ` [PATCH 3/4] i2c: allow twl modules to be built as modules Tony Lindgren
2008-06-23 11:11     ` [PATCH 2/4] usb: musb: add MODULE_ALIAS for udev module loading Tony Lindgren
2008-06-23 11:10   ` [PATCH 1/4] usb: musb: musb on omap3 has 32 endpoints Tony Lindgren
2008-06-23 11:14     ` Felipe Balbi
2008-06-23 11:18       ` Tony Lindgren
2008-06-24  4:22       ` Gadiyar, Anand
2008-06-24  8:15         ` Felipe Balbi
2008-06-25 14:42         ` Dmitry Krivoschekov [this message]
2008-06-26 12:15           ` Tony Lindgren

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=48625971.8060800@gmail.com \
    --to=dmitry.krivoschekov@gmail.com \
    --cc=felipe.balbi@nokia.com \
    --cc=gadiyar@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox