From: Sebastian Andrzej Siewior <bigeasy-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
To: Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>
Cc: Tanya Brokhman <tlinder-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
gregkh-l3A5Bk7waGM@public.gmane.org,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ablay-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
"'open list:USB GADGET/PERIPH...'"
<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
'open list'
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 2/5 v6] usb: Add usb_endpoint_descriptor to be part of the struct usb_ep
Date: Mon, 11 Apr 2011 16:39:30 +0200 [thread overview]
Message-ID: <20110411143930.GD4018@linutronix.de> (raw)
In-Reply-To: <20110328084624.GI2251-UiBtZHVXSwEVvW8u9ZQWYwjfymiNCTlR@public.gmane.org>
* Felipe Balbi | 2011-03-28 11:46:25 [+0300]:
>> Could you please share you concerns? Even if they are not strong arguments
>> :).
>> Our pros for this change were that it seems more accurate that the EP
>> descriptor will be handled by the composite layer and not the FDs. Thus we
>> tried to spare the FD from saving the chosen EP descriptor and passing it to
>> different functions.
>> This change is needed for our algorithm of SS implementation in the later
>> patches in this series.
>
>Yes, I understood that much, but it's useful for UDCs to access the EP
>descriptor (ok, we can still access it by dereferencing ep) since we can
>(actually we need to) use that to let the HW know about max packet
>sizes, endpoint types, etc etc.
>
>Also, I'm not sure composite.c should know the details about the
>endpoint. That's just a thin layer implementing the more generic part
>(standard usb requests, handling, helpers for finding endpoints, etc),
>but the one who should look into endpoint descriptors is the underlying
>controller code for the reasons I listed above.
>
>That's my feeling...
If I look at the diffstat between patch 2 and 4 I see
| 30 files changed, 299 insertions(+), 393 deletions(-)
So she got rid of almost 100 lines. While looking at the code it seems
that every gadget driver does the same thing which is now done in one
place. I like that so far :)
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Felipe Balbi <balbi@ti.com>
Cc: Tanya Brokhman <tlinder@codeaurora.org>,
gregkh@suse.de, linux-arm-msm@vger.kernel.org,
ablay@codeaurora.org,
"'open list:USB GADGET/PERIPH...'" <linux-usb@vger.kernel.org>,
"'open list'" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/5 v6] usb: Add usb_endpoint_descriptor to be part of the struct usb_ep
Date: Mon, 11 Apr 2011 16:39:30 +0200 [thread overview]
Message-ID: <20110411143930.GD4018@linutronix.de> (raw)
In-Reply-To: <20110328084624.GI2251@legolas.emea.dhcp.ti.com>
* Felipe Balbi | 2011-03-28 11:46:25 [+0300]:
>> Could you please share you concerns? Even if they are not strong arguments
>> :).
>> Our pros for this change were that it seems more accurate that the EP
>> descriptor will be handled by the composite layer and not the FDs. Thus we
>> tried to spare the FD from saving the chosen EP descriptor and passing it to
>> different functions.
>> This change is needed for our algorithm of SS implementation in the later
>> patches in this series.
>
>Yes, I understood that much, but it's useful for UDCs to access the EP
>descriptor (ok, we can still access it by dereferencing ep) since we can
>(actually we need to) use that to let the HW know about max packet
>sizes, endpoint types, etc etc.
>
>Also, I'm not sure composite.c should know the details about the
>endpoint. That's just a thin layer implementing the more generic part
>(standard usb requests, handling, helpers for finding endpoints, etc),
>but the one who should look into endpoint descriptors is the underlying
>controller code for the reasons I listed above.
>
>That's my feeling...
If I look at the diffstat between patch 2 and 4 I see
| 30 files changed, 299 insertions(+), 393 deletions(-)
So she got rid of almost 100 lines. While looking at the code it seems
that every gadget driver does the same thing which is now done in one
place. I like that so far :)
Sebastian
next prev parent reply other threads:[~2011-04-11 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 8:03 [PATCH 2/5 v6] usb: Add usb_endpoint_descriptor to be part of the struct usb_ep Tatyana Brokhman
2011-03-23 8:03 ` Tatyana Brokhman
2011-03-25 13:42 ` Felipe Balbi
2011-03-27 12:26 ` Tanya Brokhman
2011-03-27 12:26 ` Tanya Brokhman
2011-03-28 8:46 ` Felipe Balbi
[not found] ` <20110328084624.GI2251-UiBtZHVXSwEVvW8u9ZQWYwjfymiNCTlR@public.gmane.org>
2011-04-11 14:39 ` Sebastian Andrzej Siewior [this message]
2011-04-11 14:39 ` Sebastian Andrzej Siewior
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=20110411143930.GD4018@linutronix.de \
--to=bigeasy-hfztesqfncyowbw4kg4ksq@public.gmane.org \
--cc=ablay-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=gregkh-l3A5Bk7waGM@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tlinder-sgV2jX0FEOL9JmXXK+q4OQ@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 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.