From: Tilman Schmidt <tilman@imap.cc>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC 13/13] USB: Disable hub-initiated LPM for comms devices.
Date: Sat, 19 May 2012 00:38:41 +0200 [thread overview]
Message-ID: <4FB6CF71.7080307@imap.cc> (raw)
In-Reply-To: <20120517173150.GE4967@xanatos>
Am 17.05.2012 19:31, schrieb Sarah Sharp:
> On Thu, May 17, 2012 at 07:07:32PM +0200, Tilman Schmidt wrote:
>>
>> I follow the argument for class drivers. But this patch also
>> modifies drivers for specific existing USB 2.0 only devices
>> which are unlikely to ever grow USB 3.0 support, such as the
>> Gigaset ISDN driver:
>>
>>> drivers/isdn/gigaset/bas-gigaset.c | 1 +
>>> drivers/isdn/gigaset/usb-gigaset.c | 1 +
>
> Is there a particular reason why you think that driver is unlikely to
> ever get USB 3.0 support?
Actually, there is. :-)
- The USB devices driven by this driver aren't built anymore.
- Their USB interface design is quite, um, idiosyncratic, and it's
pretty unlikely that anyone will reuse it. (At least I truly hope
no one will.)
- Their successor models have completely different and incompatible
USB interfaces which this driver is unable to handle.
>> What is the interest of setting the disable_hub_initiated_lpm
>> flag for these?
>
> It's partially to lay the foundation for anyone who wants to make a USB
> 3.0 communications driver in the future. They're likely to start from
> some USB 2.0 class driver, and copy a lot of code. If they notice that
> flag is set in all the USB communications class drivers, they're likely
> to set it as well.
You've got a point there.
> I'm not quite sure where the best place to provide documentation on the
> flag is. I've added the kernel doc comments to the structure, but maybe
> it needs to be documented somewhere in Documentation/usb/?
Documentation/usb/power-management.txt would seem like a natural
place. Although it appears to limit itself to "suspending" in its
first paragraph, it does have a section "xHCI hardware link PM"
at the end already, added by Andiry Xu on 2011-09-23.
Hmmm, that section seems to suggest that LPM exists for USB2, too.
Perhaps I should reconsider my attitude towards your patch.
Thanks,
Tilman
--
Tilman Schmidt E-Mail: tilman at imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Unge?ffnet mindestens haltbar bis: (siehe R?ckseite)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120519/39e38f4d/attachment.pgp
WARNING: multiple messages have this Message-ID (diff)
From: Tilman Schmidt <tilman@imap.cc>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>,
Hansjoerg Lipp <hjlipp@web.de>,
linux-bluetooth@vger.kernel.org,
gigaset307x-common@lists.sourceforge.net, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
libertas-dev@lists.infradead.org, users@rt2x00.serialmonkey.com
Subject: Re: [RFC 13/13] USB: Disable hub-initiated LPM for comms devices.
Date: Sat, 19 May 2012 00:38:41 +0200 [thread overview]
Message-ID: <4FB6CF71.7080307@imap.cc> (raw)
In-Reply-To: <20120517173150.GE4967@xanatos>
[-- Attachment #1: Type: text/plain, Size: 2194 bytes --]
Am 17.05.2012 19:31, schrieb Sarah Sharp:
> On Thu, May 17, 2012 at 07:07:32PM +0200, Tilman Schmidt wrote:
>>
>> I follow the argument for class drivers. But this patch also
>> modifies drivers for specific existing USB 2.0 only devices
>> which are unlikely to ever grow USB 3.0 support, such as the
>> Gigaset ISDN driver:
>>
>>> drivers/isdn/gigaset/bas-gigaset.c | 1 +
>>> drivers/isdn/gigaset/usb-gigaset.c | 1 +
>
> Is there a particular reason why you think that driver is unlikely to
> ever get USB 3.0 support?
Actually, there is. :-)
- The USB devices driven by this driver aren't built anymore.
- Their USB interface design is quite, um, idiosyncratic, and it's
pretty unlikely that anyone will reuse it. (At least I truly hope
no one will.)
- Their successor models have completely different and incompatible
USB interfaces which this driver is unable to handle.
>> What is the interest of setting the disable_hub_initiated_lpm
>> flag for these?
>
> It's partially to lay the foundation for anyone who wants to make a USB
> 3.0 communications driver in the future. They're likely to start from
> some USB 2.0 class driver, and copy a lot of code. If they notice that
> flag is set in all the USB communications class drivers, they're likely
> to set it as well.
You've got a point there.
> I'm not quite sure where the best place to provide documentation on the
> flag is. I've added the kernel doc comments to the structure, but maybe
> it needs to be documented somewhere in Documentation/usb/?
Documentation/usb/power-management.txt would seem like a natural
place. Although it appears to limit itself to "suspending" in its
first paragraph, it does have a section "xHCI hardware link PM"
at the end already, added by Andiry Xu on 2011-09-23.
Hmmm, that section seems to suggest that LPM exists for USB2, too.
Perhaps I should reconsider my attitude towards your patch.
Thanks,
Tilman
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-05-18 22:38 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 21:54 [ath9k-devel] [RFC 00/13] USB 3.0 Link Power Management (LPM) support Sarah Sharp
2012-05-16 21:54 ` Sarah Sharp
2012-05-16 21:55 ` [ath9k-devel] [RFC 05/13] USB: Allow drivers to disable hub-initiated LPM Sarah Sharp
2012-05-16 21:55 ` Sarah Sharp
2012-05-16 21:55 ` [ath9k-devel] [RFC 13/13] USB: Disable hub-initiated LPM for comms devices Sarah Sharp
2012-05-16 21:55 ` Sarah Sharp
2012-05-17 17:07 ` [ath9k-devel] " Tilman Schmidt
2012-05-17 17:07 ` Tilman Schmidt
2012-05-17 17:07 ` Tilman Schmidt
2012-05-17 17:31 ` [ath9k-devel] " Sarah Sharp
2012-05-17 17:31 ` Sarah Sharp
2012-05-17 17:31 ` Sarah Sharp
2012-05-17 17:50 ` [ath9k-devel] " Andre Bella
2012-05-17 17:50 ` Andre Bella
2012-05-18 22:38 ` Tilman Schmidt [this message]
2012-05-18 22:38 ` Tilman Schmidt
2012-05-18 23:09 ` [ath9k-devel] " Sarah Sharp
2012-05-18 23:09 ` Sarah Sharp
2012-05-18 23:09 ` Sarah Sharp
2012-05-16 22:45 ` [ath9k-devel] [RFC 05/13] USB: Allow drivers to disable hub-initiated LPM Sarah Sharp
2012-05-16 22:45 ` Sarah Sharp
2012-05-16 22:45 ` Sarah Sharp
2012-05-16 22:45 ` [ath9k-devel] [RFC 13/13] USB: Disable hub-initiated LPM for comms devices Sarah Sharp
2012-05-16 22:45 ` Sarah Sharp
2012-05-16 22:45 ` Sarah Sharp
2012-05-16 23:20 ` [ath9k-devel] " Greg Kroah-Hartman
2012-05-16 23:20 ` Greg Kroah-Hartman
2012-05-16 23:20 ` Greg Kroah-Hartman
2012-05-17 4:52 ` [ath9k-devel] " Sarah Sharp
2012-05-17 4:52 ` Sarah Sharp
2012-05-17 4:52 ` Sarah Sharp
2012-05-17 14:49 ` [ath9k-devel] " Greg Kroah-Hartman
2012-05-17 14:49 ` Greg Kroah-Hartman
2012-05-17 14:49 ` Greg Kroah-Hartman
2012-05-17 16:29 ` [ath9k-devel] " Sarah Sharp
2012-05-17 16:29 ` Sarah Sharp
2012-05-17 16:39 ` [ath9k-devel] " Greg Kroah-Hartman
2012-05-17 16:39 ` Greg Kroah-Hartman
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=4FB6CF71.7080307@imap.cc \
--to=tilman@imap.cc \
--cc=ath9k-devel@lists.ath9k.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.