Here I present the conversion of everthing that is required to provide
the equivalent of g_ncm.ko with configfs.
A branch will be available here (from 23rd May 2013, afternoon UTC):
git://git.infradead.org/users/kmpark/linux-samsung usb-gadget-configfs
v3..v4:
- don't unregister a network interf
u_ether.c has been #include'd by all gadgets which implement
USB Ethernet functions. In order to add configfs support,
the f_ecm.c, f_eem.c, f_ncm.c, f_subset.c, f_rndis.c need to be
converted into modules and must not be #include'd. Consequently,
the u_ether.c needs to be a module too, in a manner
In order to convert to configfs the usb functions need to be converted
to a new interface and compiled as modules. This patch creates an rndis
module which will be used by the new functions. After all users of
f_rndis are converted to the new interface, this module can be
merged with f_rndis module
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/f_ncm.c | 166
drivers/usb/gadget/u_ncm.h |9 +++
2 files changed, 175 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/gadget/f_ncm.c b/drivers/usb/g
There are no old function interface users left, so the old interface
can be removed.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/f_ncm.c | 80 --
drivers/usb/gadget/u_ether.h |2 -
2 files changed, 0 in
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/f_ncm.c | 26 ++
1 files changed, 10 insertions(+), 16 deletions(-)
diff --git a/drivers/usb/gadget/f_ncm.c b/drivers/usb/gadget/f_ncm.c
index d8069de..effd2fa 100644
--- a/drivers
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/ncm.c | 57 +++-
2 files changed, 36 insertions(+), 22 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gad
Add an interface to create a struct netdev_dev filled with default values, an
interface which makes it
an interface to fill the struct with useful values and an interface to
read the values set.
The patch also adds an interface to register the net device associated
with an ethernet-over-usb link.
Converting ncm to the new function interface requires converting
the USB ncm's function code and its users.
This patch converts the f_ncm.c to the new function interface.
The file is now compiled into a separate usb_f_ncm.ko module.
The old function interface is provided by means of a preprocessor
Hi,
On 22/05/13 12:18, Jiri Slaby wrote:
> Some drivers can be built on more platforms than they run on. This
> causes users and distributors packaging burden when they have to
> manually deselect some drivers from their allmodconfigs. Or sometimes
> it is even impossible to disable the drivers wi
Here I present the conversion of everthing that is required to provide
the equivalent of g_cdc.ko with configfs.
A branch will be available here (from 23rd May 2013, afternoon UTC):
git://git.infradead.org/users/kmpark/linux-samsung usb-gadget-configfs
v2..v3:
- don't unregister a network interf
Converting ecm to the new function interface requires converting
the USB ecm's function code and its users.
This patch converts the f_ecm.c to the new function interface.
The file is now compiled into a separate usb_f_ecm.ko module.
The old function interface is provided by means of a preprocessor
All USB Ethernet functions will have very similar attributes in configfs.
This patch provides helper definitions to ease writing the functions and
reduce source code duplication.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/f_ncm.c| 139 +
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/f_ecm.c | 50 +++-
drivers/usb/gadget/u_ecm.h |9
2 files changed, 58 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/gadget/f_ecm.c b/drivers/u
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/f_ecm.c | 23 +--
1 files changed, 9 insertions(+), 14 deletions(-)
diff --git a/drivers/usb/gadget/f_ecm.c b/drivers/usb/gadget/f_ecm.c
index b3a1747..1b2139d 100644
--- a/drivers/usb
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/cdc2.c | 84 ++-
2 files changed, 52 insertions(+), 33 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadg
Here I present the conversion of everything that is required to provide
the equivalent of g_nokia.ko with configfs.
A branch will be available here (from 23rd May 2013, afternoon UTC):
git://git.infradead.org/users/kmpark/linux-samsung usb-gadget-configfs
v1..v2:
- don't unregister a network int
There are no old function interface users left, so the old interface
can be removed.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/f_obex.c | 52 ---
1 files changed, 0 insertions(+), 52 deletions(-)
diff --gi
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/nokia.c | 122 ++--
2 files changed, 85 insertions(+), 38 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gad
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/nokia.c | 56 ++-
2 files changed, 40 insertions(+), 17 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadg
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
.../ABI/testing/configfs-usb-gadget-phonet |8 +++
drivers/usb/gadget/Kconfig | 10
drivers/usb/gadget/f_phonet.c | 56
3 files changed, 74
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/nokia.c | 66 +++
2 files changed, 36 insertions(+), 31 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadg
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/f_phonet.c | 20 +++-
drivers/usb/gadget/nokia.c| 14 +-
drivers/usb/gadget/u_phonet.h |6 +++---
3 files changed, 23 insertions(+), 17 deletions(-)
diff --git a/driv
Converting f_phonet to the new function interface requires converting
the f_phonet's function code and its users.
This patch converts the f_phonet.c to the new function interface.
The file is now compiled into a separate usb_f_phonet.ko module.
The old function interface is provided by means of pre
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/f_obex.c | 23 ---
1 files changed, 8 insertions(+), 15 deletions(-)
diff --git a/drivers/usb/gadget/f_obex.c b/drivers/usb/gadget/f_obex.c
index 29a348a..1b61fe7 100644
--- a/drivers/
There are no old function interface users left, so the old interface
can be removed.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/f_phonet.c | 84 ++---
drivers/usb/gadget/u_phonet.h |1 -
2 files changed, 4 i
Hi Felipe,
if it's ok with you I send the patch series via at91
with the DT
Best Regards,
J.
On 18:21 Mon 20 May , Jean-Christophe PLAGNIOL-VILLARD wrote:
> HI,
>
> v4:
> fix multi instance support
>
> v3:
> rebase againt 3.10-rc1 + dt macro cleanup
>
Use the wrapper functions for getting and setting the driver data using
platform_device instead of using dev_{get,set}_drvdata() with &pdev->dev,
so we can directly pass a struct platform_device.
Also, unnecessary dev_set_drvdata() is removed, because the driver core
clears the driver data to NULL
Use the wrapper functions for getting and setting the driver data using
platform_device instead of using dev_{get,set}_drvdata() with &pdev->dev,
so we can directly pass a struct platform_device.
Signed-off-by: Jingoo Han
---
drivers/usb/gadget/fsl_qe_udc.c |4 ++--
drivers/usb/gadget/fusb
Hi Greg,
There is one patch for 3.10 that fixes an issue with dma_mask pointer
when ehci-omap is used as a module and kernel is booted using
device tree. More details in the patch.
Roger Quadros (1):
USB: ehci-omap: Reset dma_mask pointer on probe
drivers/usb/host/ehci-omap.c |3 +--
1 fi
Device tree probed devices don't get dma_mask set. Previously
we were setting the dma_mask pointer only if it was NULL.
However, the address of 'omap_ehci_dma_mask' would change
each time the module is unloaded and loaded back thus causing
the devices dma_mask pointer to be invalid on the next load
On 23/05/2013 04:23, Bo Shen :
Hi J,
On 5/21/2013 00:25, Jean-Christophe PLAGNIOL-VILLARD wrote:
so we can have multiple usb gadget instance
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
Cc: Nicolas Ferre
Cc: linux-usb@vger.kernel.org
For this series, test OK on at91sam9m10g45ek and at91
This series of patches begins the process of splitting ohci-hcd up into
a core library module and independent pci driver modules.
Patch 1/3 prepares the way by exporting a few functions from ohci-hcd
and adding a new mechanism for platform-specific drivers to initialize
their hc_driver structures.
This patch prepares ohci-hcd for being split up into a core
library and separate platform driver modules. A generic
ohci_hc_driver structure is created, containing all the "standard"
values, and a new mechanism is added whereby a driver module can
specify a set of overrides to those values. In ad
Note that this changes is part of separating the ohci pci host controller
driver from ohci-hcd host code.
This contains :
-Moved sb800_prefetch() function from ohci-pci.c to pci-quirks.c file
and EXPORTed, this is part of the effort to move the ohci pci related
code to generic pci code.
-Pass
This patch splits the PCI portion of ohci-hcd out into its
own separate driver module, called ohci-pci.
The major point of difficulty lies in ohci-pci's many vendor- and
device-specific workarounds. Some of them have to be applied before
calling ohci_start() some after, which necessitates a fair
On Wed, 22 May 2013, Vincent Palatin wrote:
> Add a quirk to ignore Jabra speakerphone 410 and 510 devices HID
> interface.
> On those devices, the USB audio interface is working nicely,
> but the HID interface is not working with the kernel usbhid driver,
> and it requires a specific userspace pr
Hi,
On Tue, May 21, 2013 at 09:26:32AM +0800, Peter Chen wrote:
> On Mon, May 20, 2013 at 06:18:52PM +0300, Felipe Balbi wrote:
> > On Mon, May 20, 2013 at 10:55:57AM +0800, Peter Chen wrote:
> > > If the glue layer is removed first (core layer later),
> > > it deletes the phy device first, then t
Alexey Orishko writes:
> Hi all,
>
> On Wed, May 22, 2013 at 10:40 PM, Bjørn Mork wrote:
>
>> Thomas Schäfer writes:
>>
>> > TX-counter-problem
>> > ...
>> >
>> >> This is expected as a result of the cdc_ncm <=> usbnet design.
>> > .
>> >
>> >> The buffer filling may seem strange, but Alexe
Hi all,
I have a lot of linux computers equipped with a GlobalSat Br-353 GPS receiver,
which is connected via USB (an integrated PL2303). The GPS receiver emits
one multi-line message every second, giving position and time. I listen
to this messages in a user program running in the highest prior
On Thursday 23 May 2013, Manjunath Goudar wrote:
> @@ -1275,7 +1266,7 @@ MODULE_LICENSE ("GPL");
> #define PLATFORM_DRIVERohci_platform_driver
> #endif
>
> -#if!defined(PCI_DRIVER) && \
> +#if!defined(PCI_DRIVER) && \
> !defined(PLATFORM_DRIVER) &&\
>
On Wed, 2013-05-22 at 19:23 -0700, Greg Kroah-Hartman wrote:
> On Wed, May 22, 2013 at 11:18:46AM +0200, Jiri Slaby wrote:
> > Some drivers can be built on more platforms than they run on. This
> > causes users and distributors packaging burden when they have to
> > manually deselect some drivers f
On Wed, 22 May 2013, Joe Julian wrote:
> Right, and I'm supposed to know that how? You're the one who's an
> expert on usb. You know how HID keyboards pass data. I'm starting
> from scratch and only have data that is sensitive. It's hard to know
> what you can share when you don't know what you ha
On Thu, 23 May 2013, Sachin Kamat wrote:
> 'hcd' can never be NULL and the spear_ehci_hcd_drv_remove routine
> will never be called in_interrupt. Hence remove these checks.
>
> Signed-off-by: Sachin Kamat
> Cc: Viresh Kumar
> Cc: Alan Stern
> ---
> Compile tested on linux-next (20130522).
> --
usb 2.0 devices with link power managment (LPM) can describe their idle link
timeouts either in BESL or HIRD format, so far xHCI has only supported HIRD but
later xHCI errata add BESL support as well
BESL timeouts need to inform exit latency changes with an evaluate
context command the same way US
Adds abitilty to tune L1 timeout (inactivity timer for usb2 link sleep)
and BESL (best effort service latency)via sysfs.
This also adds a new usb2_lpm_parameters structure with those variables to
struct usb_device.
Signed-off-by: Mathias Nyman
---
Documentation/ABI/testing/sysfs-bus-usb | 27
On Thu, 23 May 2013, Roger Quadros wrote:
> Device tree probed devices don't get dma_mask set. Previously
> we were setting the dma_mask pointer only if it was NULL.
> However, the address of 'omap_ehci_dma_mask' would change
> each time the module is unloaded and loaded back thus causing
> the de
On Thu, 23 May 2013, Jingoo Han wrote:
> Use the wrapper functions for getting and setting the driver data using
> platform_device instead of using dev_{get,set}_drvdata() with &pdev->dev,
> so we can directly pass a struct platform_device.
>
> Also, unnecessary dev_set_drvdata() is removed, beca
This series adds usb2 best effort service latency (BESL) link PM support
to xHCI. BESL is an updated alternative to host initated resume delay
(HIRD) method of describing idle link timeouts.
Additionally this series fixes port capability checking
and replaces magic numbers with port register names
Hardware link powermanagement in usb2 is a per-port capability.
Previously support for hw lpm was enabled for all ports if any usb2 port
supported it.
Now instead cache the capability values and check them for each port
individually
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-mem.c
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 16 +++-
drivers/usb/host/xhci.c |4 ++--
drivers/usb/host/xhci.h |5 +
3 files changed, 14 insertions(+), 11 deletions(-)
diff --git a/drivers/usb/host/xhci-hub.c b/drivers/usb/host/xhci-hub.c
index
Hello.
On 23-05-2013 10:01, Ravi Babu wrote:
removed unused nop xceiv (un_)register API's from all musb
platform drivers
Since when are they unused?
Signed-off-by: Ravi Babu
WBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message t
On 23-05-2013 10:01, Ravi Babu wrote:
In case of mutli instance support, use get-phy object using phandle
to return to repsective phy xceiv object for each instance
Only "respective" and s/xceiv/transceiver/.
Signed-off-by: Ravi Babu
WBR, Sergei
--
To unsubscribe from this list: send
On Thu, 23 May 2013, Manjunath Goudar wrote:
> This patch prepares ohci-hcd for being split up into a core
> library and separate platform driver modules. A generic
> ohci_hc_driver structure is created, containing all the "standard"
> values, and a new mechanism is added whereby a driver module
On 23-05-2013 10:01, Ravi Babu wrote:
The am33xx platforms suppors dual musb instance which need two instances
of usb-phy. Add dual instance usb-phy DT bindings for am333x platform.
Signed-off-by: Ravi Babu
---
arch/arm/boot/dts/am33xx.dtsi | 17 +
1 files changed, 17 in
On Thu, 23 May 2013, Manjunath Goudar wrote:
> Note that this changes is part of separating the ohci pci host controller
> driver from ohci-hcd host code.
> This contains :
> -Moved sb800_prefetch() function from ohci-pci.c to pci-quirks.c file
> and EXPORTed, this is part of the effort to move
On Thu, 23 May 2013, Manjunath Goudar wrote:
> This patch splits the PCI portion of ohci-hcd out into its
> own separate driver module, called ohci-pci.
>
> The major point of difficulty lies in ohci-pci's many vendor- and
> device-specific workarounds. Some of them have to be applied before
> c
On 05/23/2013 05:11 PM, Alan Stern wrote:
> On Thu, 23 May 2013, Roger Quadros wrote:
>
>> Device tree probed devices don't get dma_mask set. Previously
>> we were setting the dma_mask pointer only if it was NULL.
>> However, the address of 'omap_ehci_dma_mask' would change
>> each time the module
On Thu, May 23, 2013 at 03:07:09PM +0200, Philippe De Muyter wrote:
> Hi all,
>
> I have a lot of linux computers equipped with a GlobalSat Br-353 GPS receiver,
> which is connected via USB (an integrated PL2303). The GPS receiver emits
> one multi-line message every second, giving position and t
The following changes since commit f722406faae2d073cc1d01063d1123c35425939e:
Linux 3.10-rc1 (2013-05-11 17:14:08 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/
tags/usb-3.10-rc2
for you to fetch changes up to 2a0ebf80aa95cc758d4
On Thu, May 23, 2013 at 09:14:57AM -0700, Greg KH wrote:
> The following changes since commit f722406faae2d073cc1d01063d1123c35425939e:
>
> Linux 3.10-rc1 (2013-05-11 17:14:08 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/
On Thursday 23 May 2013, Alan Stern wrote:
> On Thu, 23 May 2013, Manjunath Goudar wrote:
> Also, you left out one thing that should still be here. What happened
> to the part about changing
>
> #if !defined(PCI_DRIVER) && \
>
> to
>
> #if !ENABLED(CONFIG_USB_OHCI_HCD_PCI) &&\
Sergei
> Subject: Re: [PATCH v1 2/9] usb: musb: nop: remove unused
> nop_xceiv_(un)register APIs from glue
> Hello.
> On 23-05-2013 10:01, Ravi Babu wrote:
>> removed unused nop xceiv (un_)register API's from all musb
>> platform drivers
>Since when are they unused?
Please refer to commit
> Subject: Re: [PATCH v1 7/9] usb: musb: dsps: use get-usb-phy by phandle for
> multi instance
> On 23-05-2013 10:01, Ravi Babu wrote:
>> In case of mutli instance support, use get-phy object using phandle to
>> return to repsective phy xceiv object for each instance
> Only "respective" and
Sergei
>>
>> +phy1: usbphy-gs70@44e10620 {
>> +compatible = "ti,dsps-usbphy";
>> +reg = <0x44e10620 0x8
>> + 0x44e10648 0x4>;
>> +reg-names = "phy_ctrl","phy_wkup";
>> +id = <0>;
>
On Thu, 23 May 2013, Arnd Bergmann wrote:
> On Thursday 23 May 2013, Alan Stern wrote:
> > On Thu, 23 May 2013, Manjunath Goudar wrote:
>
> > Also, you left out one thing that should still be here. What happened
> > to the part about changing
> >
> > #if !defined(PCI_DRIVER) && \
> >
On Thursday 23 May 2013, Alan Stern wrote:
> > >
> >
> > This section of the driver is gone now since 86510bb248 "USB: OHCI:
> > clarify Kconfig dependencies", so the change is no longer needed.
>
> I don't know what tree you're referring to. That commit is not present
> in Greg's usb-linus or
Hello.
On 05/23/2013 09:13 PM, B, Ravi wrote:
+ phy1: usbphy-gs70@44e10620 {
+ compatible = "ti,dsps-usbphy";
+ reg = <0x44e10620 0x8
+ 0x44e10648 0x4>;
+ reg-names = "phy_ctrl","phy_w
Hello.
On 05/23/2013 09:07 PM, B, Ravi wrote:
removed unused nop xceiv (un_)register API's from all musb
platform drivers
Since when are they unused?
Please refer to commit id 662dca54 : usb: otg: support for multiple
transceivers by a single controller.
Usb_get_phy() is used to get the
On Mon, May 20, 2013 at 06:25:55PM +0200, Jean-Christophe PLAGNIOL-VILLARD
wrote:
> drop static struct usba_udc the_udc
>
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
> Cc: Nicolas Ferre
> Cc: linux-usb@vger.kernel.org
Acked-by: Felipe Balbi
> ---
> drivers/usb/gadget/atmel_usba_udc.c
On Mon, May 20, 2013 at 06:25:54PM +0200, Jean-Christophe PLAGNIOL-VILLARD
wrote:
> so we can have multiple usb gadget instance
>
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
> Cc: Nicolas Ferre
> Cc: linux-usb@vger.kernel.org
Acked-by: Felipe Balbi
--
balbi
signature.asc
Description
On Mon, May 20, 2013 at 06:25:56PM +0200, Jean-Christophe PLAGNIOL-VILLARD
wrote:
> Allow to compile the driver all the time if AT91 enabled.
>
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
> Cc: Nicolas Ferre
> Cc: linux-usb@vger.kernel.org
Acked-by: Felipe Balbi
--
balbi
signature.a
Hi,
I am attempting to get a wireless USB mass storage device to work with
an HWA as the host controller. Everything works fine as long as the SCSI
reads are smaller than 4kbytes. When the usb-storage driver receives the
first 16kB read, it breaks it up into 4-4kB URBs and sends it to the HWA
On Thu, 23 May 2013, Thomas Pugliese wrote:
> Hi,
> I am attempting to get a wireless USB mass storage device to work with
> an HWA as the host controller. Everything works fine as long as the SCSI
> reads are smaller than 4kbytes. When the usb-storage driver receives the
> first 16kB read,
On Thu, 23 May 2013, Alan Stern wrote:
> On Thu, 23 May 2013, Thomas Pugliese wrote:
>
> > Hi,
> > I am attempting to get a wireless USB mass storage device to work with
> > an HWA as the host controller. Everything works fine as long as the SCSI
> > reads are smaller than 4kbytes. When th
From: Thomas Abraham
Exynos5440 does not require any explict USB phy configuration. So skip
the USB phy configuration for Exynos5440 based platforms.
Signed-off-by: Thomas Abraham
Signed-off-by: Jingoo Han
---
Changes since v2:
- changed all occurrences of s5p_ehci->pdata->phy*.
- set s5p_ehci
On 05/23/2013 09:01:40 AM, Ben Hutchings wrote:
On Wed, 2013-05-22 at 19:23 -0700, Greg Kroah-Hartman wrote:
> On Wed, May 22, 2013 at 11:18:46AM +0200, Jiri Slaby wrote:
> > Some drivers can be built on more platforms than they run on. This
> > causes users and distributors packaging burden when
Subject: Re: [PATCH v1 8/9] usb: phy: dts: Adding usbphy DT bindings for am33xx
Hello.
On 05/23/2013 09:13 PM, B, Ravi wrote:
>
>>> + phy1: usbphy-gs70@44e10620 {
>>> + compatible = "ti,dsps-usbphy";
>>> + reg = <0x44e10620 0x8
>>> +
Subject: Re: [PATCH v1 2/9] usb: musb: nop: remove unused
nop_xceiv_(un)register APIs from glue
Hello.
On 05/23/2013 09:07 PM, B, Ravi wrote:
>>> removed unused nop xceiv (un_)register API's from all musb platform
>>> drivers
>> Since when are they unused?
> Please refer to commit id 662d
If the glue layer is removed first (core layer later),
it deletes the phy device first, then the core device.
But at core's removal, it still uses PHY's resources, it may
cause kernel's oops. It is much like the problem
Paul Zimmerman reported at:
http://marc.info/?l=linux-usb&m=136547502011472&w=2
If the glue layer is removed first (core layer later),
it deletes the phy device first, then the core device.
But at core's removal, it still uses PHY's resources, it may
cause kernel's oops. It is much like the problem
Paul Zimmerman reported at:
http://marc.info/?l=linux-usb&m=136547502011472&w=2
If the glue layer is removed first (core layer later),
it deletes the phy device first, then the core device.
But at core's removal, it still uses PHY's resources, it may
cause kernel's oops. It is much like the problem
Paul Zimmerman reported at:
http://marc.info/?l=linux-usb&m=136547502011472&w=2
If the glue layer is removed first (core layer later),
it deletes the phy device first, then the core device.
But at core's removal, it still uses PHY's resources, it may
cause kernel's oops. It is much like the problem
Paul Zimmerman reported at:
http://marc.info/?l=linux-usb&m=136547502011472&w=2
83 matches
Mail list logo
