devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>
To: Paul Zimmerman <Paul.Zimmerman-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
Cc: "balbi-l0cyMroinI0@public.gmane.org"
	<balbi-l0cyMroinI0@public.gmane.org>,
	Linux USB Mailing List
	<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH 8/9] usb: dwc3: gadget: dynamically re-size TxFifos
Date: Thu, 26 Jan 2012 14:15:30 +0200	[thread overview]
Message-ID: <20120126121528.GO15110@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <F6C4814A9B336243ABC3D1FB44E08AE801D53C9116-uiPIUNf6hlr3OT/vyeh27fufCSb+aD3WLzEdoUbNIic@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

Hi,

On Wed, Jan 25, 2012 at 10:54:56AM -0800, Paul Zimmerman wrote:
> On Wed, 25 Jan 2012, Felipe Balbi wrote:
> 
> > > > You probably don't want a module parameter. Maybe we could enable this depending
> > > > on the PCI ID, or from platform data?
> > > 
> > > Platform data will be vanishing soon, but we can have a devicetree
> > > attribute to select that, for sure ;-)
> > > 
> > > Will hack that up quickly and send a revised patch.
> 
> > here's the differential diff to add a flag for fifo resizing:
> 
> <snip>
> 
> Thanks Felipe, looks good.
> 
> One question, though. I am completely ignorant about the device tree stuff.
> Will a standard PC platform have a device tree for the PCI devices, and if
> so, where will this option flag get set?

I'm not sure how devicetree is implemented for the PCI stuff, maybe the
guys in the devicetree mailing list can help. Any tips guys ?

Anyway, when I actually figure out a nice way to allocate fifo space
based on enabled endpoints, I believe most users will just start setting
that flag because it's far better to use the FIFO for enabled endpoints
then not allocate it at all (image a situation where we have 4 IN eps
and 1024 bytes FIFO space for each one of them, if we're running with
only 1 IN ep enabled, we could allocate all 4x 1024 to the only enabled
endpoint).

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

           reply	other threads:[~2012-01-26 12:15 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <F6C4814A9B336243ABC3D1FB44E08AE801D53C9116-uiPIUNf6hlr3OT/vyeh27fufCSb+aD3WLzEdoUbNIic@public.gmane.org>]

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=20120126121528.GO15110@legolas.emea.dhcp.ti.com \
    --to=balbi-l0cymroini0@public.gmane.org \
    --cc=Paul.Zimmerman-HKixBCOQz3hWk0Htik3J/w@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).