fix typo which cause following build warning
warning: "pr_vdebug" redefined
Signed-off-by: Bo Shen
---
drivers/usb/gadget/u_serial.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/u_serial.c b/drivers/usb/gadget/u_serial.c
index c5034d9..b369292 100644
On Tue, Mar 12, 2013 at 11:46:49AM +0200, Felipe Balbi wrote:
> On Tue, Mar 12, 2013 at 05:03:18PM +0800, Peter Chen wrote:
> > Let the common struct usb_gadget own it.
> >
> > CC: Alexander Shishkin
> > CC: Jean-Christophe PLAGNIOL-VILLARD
> > CC: Li Yang
> > CC: Roland Stigge
> > CC: Yu Xu
On my Exynos 5 based Arndale system, I need to pull the reset line down
and then let it go up again to actually perform a reset. Without that
reset, I can't find any USB hubs on my bus, rendering the USB controller
useless.
So this patch implements the above logic, making EHCI and OHCI work on
Arn
Dan Williams wrote:
>With Gobi 1K devices, USB interface #3's altsetting is 0 by default,
>but
>altsetting 0 only provides one interrupt endpoint and is not sufficent
>for QMI. Altsetting 1 provides all 3 endpoints required for qmi_wwan
>and works with QMI.
>
>IIRC the altsetting used to be set
With Gobi 1K devices, USB interface #3's altsetting is 0 by default, but
altsetting 0 only provides one interrupt endpoint and is not sufficent
for QMI. Altsetting 1 provides all 3 endpoints required for qmi_wwan
and works with QMI.
IIRC the altsetting used to be set by qcserial back before we ma
On Mon, 11 Mar 2013, Noone Nowhere wrote:
> Hello Alan this is VoRTeX from the linux kernel ata wiki, greetings
> from the occupied Greece...Nick uses UNIX since 2003 (FreeBSD back
> then...5.2.1) and after all these years
> is an expert in Linux and in HDDs. In 2008 a repeated silent data
> corru
On Tue, 12 Mar 2013, Martin Mokrejs wrote:
> Hi Greg,
>
> Greg KH wrote:
> > On Tue, Mar 12, 2013 at 11:45:39AM +0100, Martin Mokrejs wrote:
> >> Hi,
> >> while testing how my computer behaves with USB disabled I see this line
> >> still
> >> in dmesg output:
> >>
> >> Initializing USB Mass S
On Tue, 12 Mar 2013, Jenya Y wrote:
> > I'll try to work out a patch in the next few days. Can you recreate
> > the arrangement where all the errors occurred, in order to test the
> > patch when it is ready?
> >
> > Alan Stern
> >
> Absolutely, I'd be glad to help.
>
> Just tell me what kernel s
On Tuesday 12 March 2013 17:58:30 Martin Mokrejs wrote:
> No, I just wondered why 'nousb' disables on the runtime ehci/xhci (also
> included
> statically in the kernbel binary) while not other USB-related modules. Maybe
> it
> was thought that no downstream modules will load because of unmet depe
Hi Greg,
Greg KH wrote:
> On Tue, Mar 12, 2013 at 11:45:39AM +0100, Martin Mokrejs wrote:
>> Hi,
>> while testing how my computer behaves with USB disabled I see this line
>> still
>> in dmesg output:
>>
>> Initializing USB Mass Storage driver...
>
> Did you build the driver into the kernel?
* Roger Quadros [130312 04:47]:
> Hi Tony,
>
> These patches provide the SoC side code required to support
> the changes in the OMAP USB Host drivers done in [1], [2] & [3].
...
> arch/arm/mach-omap2/board-3430sdp.c| 97 +++-
> arch/arm/mach-omap2/board-3630sdp.c
On 03/12/2013 04:20 PM, Roger Quadros wrote:
> On 03/12/2013 04:42 PM, Marc Kleine-Budde wrote:
>> On 03/12/2013 03:28 PM, Roger Quadros wrote:
>>> On 03/12/2013 04:17 PM, Marc Kleine-Budde wrote:
On 03/12/2013 03:12 PM, Roger Quadros wrote:
> On 03/12/2013 01:54 PM, Marc Kleine-Budde wrot
On Tue, 12 Mar 2013, Roger Quadros wrote:
> The HSIC devices need to be kept in reset while the EHCI controller
> is being initialized and only brought out of reset after the
> initialization is complete, else HSIC devices will not be detected.
This is not a great description of what the patch do
On Tue, 12 Mar 2013, Roger Quadros wrote:
> Even when not in PHY mode, the USB device on the port (e.g. HUB)
> might need resources like RESET which can be modelled as a PHY
> device. So try to get the PHY device in any case.
>
> Signed-off-by: Roger Quadros
> CC: Alan Stern
Acked-by: Alan Ste
On Tue, 12 Mar 2013, Huang Rui wrote:
> Hi Alan,
>
> The same problem is encountered in my side. Bruce's log doesn't
> demonstrate the break point. I attached a new one.
>
> [ 14.359603] hub 1-0:1.0: state 7 ports 4 chg 0004 evt
> [ 14.359613] hub 1-0:1.0: port 2, status 0101, change 00
On 03/12/2013 04:42 PM, Marc Kleine-Budde wrote:
> On 03/12/2013 03:28 PM, Roger Quadros wrote:
>> On 03/12/2013 04:17 PM, Marc Kleine-Budde wrote:
>>> On 03/12/2013 03:12 PM, Roger Quadros wrote:
On 03/12/2013 01:54 PM, Marc Kleine-Budde wrote:
> On 03/12/2013 12:24 PM, Roger Quadros wrot
On Mon, Mar 11, 2013 at 11:28:38PM +0100, Bjørn Mork wrote:
> Greg KH writes:
> >
> >> Currently, when a userspace application sees a /dev/cdc-wdmX device, it
> >> will have to
> >> - check which USB interface it belongs to,
> >> - parse the DMM descriptor if it is CDC WDM,
> >> - parse the MBIM
On Tue, Mar 12, 2013 at 3:37 PM, kishon wrote:
> Hi,
>
>
> On Sunday 10 March 2013 06:38 AM, Grazvydas Ignotas wrote:
>>
>> On USB_EVENT_ID event the musb glue enables VBUS by calling
>> omap2430_musb_set_vbus(musb, 1) that sets the session bit, but on
>> USB_EVENT_NONE reverse action is never mad
On Tue, Mar 12, 2013 at 3:32 PM, kishon wrote:
> Hi,
>
>
> On Sunday 10 March 2013 06:37 AM, Grazvydas Ignotas wrote:
>>
>> In some rare cases we may get multiple interrupts that will generate
>> duplicate omap_musb_mailbox() calls. This is a problem because each
>> VBUS/ID event generates runtime
On 03/12/2013 03:28 PM, Roger Quadros wrote:
> On 03/12/2013 04:17 PM, Marc Kleine-Budde wrote:
>> On 03/12/2013 03:12 PM, Roger Quadros wrote:
>>> On 03/12/2013 01:54 PM, Marc Kleine-Budde wrote:
On 03/12/2013 12:24 PM, Roger Quadros wrote:
> Add clk_rate parameter to platform data. If su
On 03/12/2013 04:17 PM, Marc Kleine-Budde wrote:
> On 03/12/2013 03:12 PM, Roger Quadros wrote:
>> On 03/12/2013 01:54 PM, Marc Kleine-Budde wrote:
>>> On 03/12/2013 12:24 PM, Roger Quadros wrote:
Add clk_rate parameter to platform data. If supplied, the
NOP phy driver will program the cl
On 03/12/2013 03:12 PM, Roger Quadros wrote:
> On 03/12/2013 01:54 PM, Marc Kleine-Budde wrote:
>> On 03/12/2013 12:24 PM, Roger Quadros wrote:
>>> Add clk_rate parameter to platform data. If supplied, the
>>> NOP phy driver will program the clock to that rate during probe.
>>>
>>> Also add 2 flags
On 03/12/2013 01:54 PM, Marc Kleine-Budde wrote:
> On 03/12/2013 12:24 PM, Roger Quadros wrote:
>> Add clk_rate parameter to platform data. If supplied, the
>> NOP phy driver will program the clock to that rate during probe.
>>
>> Also add 2 flags, needs_vcc and needs_reset.
>> If the flag is set a
Hi Benoit,
On 03/12/2013 03:17 PM, Benoit Cousson wrote:
> Hi Roger,
>
> On 03/12/2013 12:43 PM, Roger Quadros wrote:
>> Currently on OMAP, it is not possible to specify a clock consumer
>> to any of the OMAP generated clocks using the device tree. This can pose
>> a problem for external devices
From: Oliver Neukum
The buffer for responses must not overflow.
If this would happen, set a flag, drop the data and return
an error after user space has read all remaining data.
Signed-off-by: Oliver Neukum
CC: sta...@kernel.org
---
drivers/usb/class/cdc-wdm.c | 23 ---
1
On Tue, Mar 12, 2013 at 11:45:39AM +0100, Martin Mokrejs wrote:
> Hi,
> while testing how my computer behaves with USB disabled I see this line
> still
> in dmesg output:
>
> Initializing USB Mass Storage driver...
Did you build the driver into the kernel? Or is it being automatically
loaded
Hi,
On Sunday 10 March 2013 06:38 AM, Grazvydas Ignotas wrote:
On USB_EVENT_ID event the musb glue enables VBUS by calling
omap2430_musb_set_vbus(musb, 1) that sets the session bit, but on
USB_EVENT_NONE reverse action is never made, and that breaks PM.
Disable VBUS unconditionally on USB_EVENT
Hi,
On Sunday 10 March 2013 06:37 AM, Grazvydas Ignotas wrote:
In some rare cases we may get multiple interrupts that will generate
duplicate omap_musb_mailbox() calls. This is a problem because each
VBUS/ID event generates runtime_pm call in OMAP glue code, causing
unbalanced gets or puts and b
Martin Mokrejs wrote:
> Martin Mokrejs wrote:
>> Hi,
>> I booted same kernel under same BIOS settings with the only difference that
>> in the latter case I added 'nousb'. While inspecting the diffs in dmesg
>> outputs
>> I see that something is happening with my network card and
>>
>> +r8169 00
On Tue, Mar 12, 2013 at 10:56:20AM +0100, Oliver Neukum wrote:
> On Monday 11 March 2013 22:11:55 Bjørn Mork wrote:
> > > What ever was decided here? Can someone please send me the patch that
> > > you two agreed would solve this problem?
> >
> > I believe Oliver's patch titled "cdc-wdm: fix buff
Hi Roger,
On 03/12/2013 12:43 PM, Roger Quadros wrote:
> Currently on OMAP, it is not possible to specify a clock consumer
> to any of the OMAP generated clocks using the device tree. This can pose
> a problem for external devices that run off an OMAP clock as we
> can't reliably provide a referen
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Tue, Mar 12, 2013 at 09:02:29AM +0100, LECOQ Vincent wrote:
> USB Linux drivers can't be closed yes, but what case of userland programs
> with libusb ?
Yes, you can do whatever you want in userspac
Martin Mokrejs wrote:
> Hi,
> I booted same kernel under same BIOS settings with the only difference that
> in the latter case I added 'nousb'. While inspecting the diffs in dmesg
> outputs
> I see that something is happening with my network card and
>
> +r8169 :05:00.0: PME# disabled
> +r
On 03/12/2013 12:24 PM, Roger Quadros wrote:
> Add clk_rate parameter to platform data. If supplied, the
> NOP phy driver will program the clock to that rate during probe.
>
> Also add 2 flags, needs_vcc and needs_reset.
> If the flag is set and the regulator couldn't be found
> then the driver wi
Hi Tony,
These patches provide the SoC side code required to support
the changes in the OMAP USB Host drivers done in [1], [2] & [3].
Device tree support is added for Beagleboard and Panda.
NOTE: The first patch needs to be shared between the
OMAP tree and Felipe's USB tree.
[1] MFD side change
Add platform device and data for 'nop-usb-xceiv'. This will be used
as PHY for HS USB port 1, so provide binding information for it.
Get rid of managing the PHY clock as it will be done by the PHY driver.
For that to work we create a clock alias that links the PHY clock name
to the PHY device name
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 2, so provide binding information for it.
Model RESET and Power for HS USB Port 2 as GPIO fixed regulators
and link them to the 'nop-usb-xceiv' PHY.
NOTE: Register the PHY device only after the power regulator has
Add 2 platform devices for 'nop-usb-xceiv'. These will be used
as PHYs for HS USB ports 1 and 2 so provide binding information
for them.
Model RESET for HS USB Ports 1 and 2 as GPIO fixed regulators and
link them to the 2 PHYs we just created.
Signed-off-by: Roger Quadros
Acked-by: Felipe Balbi
Add 2 platform devices for 'nop-usb-xceiv'. These will be used as a
PHY for HS USB Port 1 and 2, so provide binding information for them.
Model RESET for HS USB Port 1 as GPIO fixed regulator and link it
to the 'nop-usb-xceiv' PHY on port 1.
Signed-off-by: Roger Quadros
Acked-by: Felipe Balbi
-
Add 2 platform devices for 'nop-usb-xceiv'. These will be used
as PHYs for HS USB ports 1 and 2 so provide binding information
for them.
Model RESET for HS USB Ports 1 and 2 as GPIO fixed regulators and
link them to the 2 PHYs we just created.
Signed-off-by: Roger Quadros
Acked-by: Felipe Balbi
Add 2 platform devices for 'nop-usb-xceiv'. These will be used
as PHYs for HS USB ports 1 and 2 so provide binding information
for them.
Model RESET for HS USB Ports 1 and 2 as GPIO fixed regulators and
link them to the 2 PHYs we just created.
Signed-off-by: Roger Quadros
Acked-by: Felipe Balbi
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 2, so provide binding information for it.
Model RESET for HS USB Port 2 as GPIO fixed regulator and link
it to the 'nop-usb-xceiv' PHY.
Signed-off-by: Roger Quadros
Acked-by: Felipe Balbi
---
arch/arm/mach-omap
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 1, so provide binding information for it.
Signed-off-by: Roger Quadros
Acked-by: Felipe Balbi
---
arch/arm/mach-omap2/board-devkit8000.c | 20
1 files changed, 12 insertions(+), 8 deletion
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 1, so provide binding information for it.
Model RESET and Power for HS USB Port 1 as GPIO fixed regulators
and link them to the 'nop-usb-xceiv' PHY.
Signed-off-by: Roger Quadros
Acked-by: Felipe Balbi
---
arch/
Add 2 platform devices for 'nop-usb-xceiv'. These will be used
as PHYs for HS USB ports 1 and 2 so provide binding information
for them.
Model RESET for HS USB Ports 1 and 2 as GPIO fixed regulators and
link them to the 2 PHYs we just created.
Signed-off-by: Roger Quadros
Acked-by: Felipe Balbi
Add 2 platform devices for 'nop-usb-xceiv'. These will be used
as PHYs for HS USB ports 1 and 2 so provide binding information
for them.
Model RESET for HS USB Ports 1 and 2 as GPIO fixed regulators and
link them to the 2 PHYs we just created.
Signed-off-by: Roger Quadros
Acked-by: Felipe Balbi
Model RESET and Power for HS USB Port 1 as GPIO fixed regulators
and link them to the 'nop-usb-xceiv' PHY by making them as "reset"
and "vcc" supplies.
The RESET and Power will then be managed by the PHY driver.
Signed-off-by: Roger Quadros
Acked-by: Felipe Balbi
---
arch/arm/mach-omap2/board-
Add clk_rate parameter to platform data. If supplied, the
NOP phy driver will program the clock to that rate during probe.
Also add 2 flags, needs_vcc and needs_reset.
If the flag is set and the regulator couldn't be found
then the driver will bail out with -EPROBE_DEFER.
Signed-off-by: Roger Qua
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 2, so provide binding information for it.
Model RESET for HS USB Port 2 as GPIO fixed regulator and link
it to the 'nop-usb-xceiv' PHY.
Signed-off-by: Roger Quadros
Acked-by: Felipe Balbi
---
arch/arm/mach-omap
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 2, so provide binding information for it.
Model RESET for HS USB Port 2 as GPIO fixed regulator and link
it to the 'nop-usb-xceiv' PHY.
Signed-off-by: Roger Quadros
Acked-by: Felipe Balbi
---
arch/arm/mach-omap
Add 2 platform devices for 'nop-usb-xceiv'. These will be used as a
PHY for HS USB Ports 1 and 2, so provide binding information for them.
Model RESET for HS USB Port 2 as GPIO fixed regulator and link it
to the respective 'nop-usb-xceiv' PHY.
Signed-off-by: Roger Quadros
Acked-by: Felipe Balbi
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 2, so provide binding information for it.
Model RESET for HS USB Port 2 as GPIO fixed regulator and link
it to the 'nop-usb-xceiv' PHY.
Signed-off-by: Roger Quadros
Acked-by: Felipe Balbi
---
arch/arm/mach-omap
Adds device nodes for HS USB Host module, TLL module,
OHCI and EHCI controllers.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap4.dtsi | 30 ++
1 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/o
Provide the RESET and Power regulators for the USB PHY,
the USB Host port mode and the PHY device.
Also provide pin multiplexer information for the USB host
pins.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap4-panda.dts | 56 +
1 files changed, 56
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 2, so provide binding information for it.
Model RESET for HS USB Port 2 as GPIO fixed regulator and link
it to the 'nop-usb-xceiv' PHY.
Signed-off-by: Roger Quadros
Acked-by: Felipe Balbi
---
arch/arm/mach-omap
Provide RESET and Power regulators for the USB PHY,
the USB Host port mode and the PHY device.
Also provide pin multiplexer information for USB host
pins.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap3-beagle.dts | 71
1 files changed, 71 inserti
Adds device nodes for HS USB Host module, TLL module,
OHCI and EHCI controllers.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap3.dtsi | 31 +++
1 files changed, 31 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/
On Panda, the USB Host PHY is clocked by FREF3_CLK (auxclk3_ck) pin
of the OMAP. Provide this information in the device tree.
CC: Russell King
CC: Rajendra Nayak
CC: Santosh Shilimkar
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap4-panda.dts |7 +++
1 files changed, 7 insert
Currently on OMAP, it is not possible to specify a clock consumer
to any of the OMAP generated clocks using the device tree. This can pose
a problem for external devices that run off an OMAP clock as we
can't reliably provide a reference to the clock in the device tree.
This patch allows device tr
This aims at making f_mass_storage.c a module. But first
we need to get rid of "#include "storage_common.c".
This patch makes storage_common.c a separately compiled
file, which is built as a utility module named u_ms.ko.
After all mass storage users are converted to the new
function interface this
The u_ms.ko utility module is now used only by the f_mass_storage_usb.ko module,
so there is no point in splitting the code into two modules.
This patch merges the two into one while keeping their corresponing source
code files compiled separately.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-
This patch is needed to prepare for using the new function interface.
The memory for struct fsg_common can either be provided
by the mass storage user, or it can be allocated by mass storage.
With the new function interface it will be provided by the mass storage user.
The new function interface u
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_mass_storage.c | 66 ---
1 files changed, 0 insertions(+), 66 deletions(-)
diff --gi
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
Converting eem to the new function interface requires converting
the USB eem's function code and its users.
This patch converts the f_eem.c to the new function interface.
The file is now compiled into a separate usb_f_eem.ko module.
The old function interface is provided by means of a preprocessor
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 | 81 +-
drivers/usb/gadget/u_ether.h |2 -
2 files changed, 1 in
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
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/cdc2.c | 57 +++
2 files changed, 42 insertions(+), 16 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/Kconfig |1 +
drivers/usb/gadget/multi.c | 69 +++-
2 files changed, 50 insertions(+), 20 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/acm_ms.c | 78 ---
2 files changed, 45 insertions(+), 34 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/ga
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/ether.c | 44 ++--
2 files changed, 39 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadg
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
Converting mass storage to the new function interface requires converting
the USB mass storage's function code and its users.
This patch converts the f_mass_storage.c to the new function interface.
The file is now compiled into a separate usb_f_mass_storage.ko module.
The old function interface is
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_eem.c | 57 --
drivers/usb/gadget/u_ether.h |1 -
2 files changed, 0 in
Converting ecm subset to the new function interface requires converting
the USB subset's function code and its users.
This patch converts the f_subset.c to the new function interface.
The file is now compiled into a separate usb_f_subset.ko module.
The old function interface is provided by means of
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig|1 +
drivers/usb/gadget/mass_storage.c | 118 +++-
2 files changed, 76 insertions(+), 43 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/u
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/ether.c | 43 +--
2 files changed, 38 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadge
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/ether.c | 41 -
2 files changed, 37 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadget/
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/g_ffs.c | 51 +--
2 files changed, 49 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadge
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/ether.c | 39 ---
2 files changed, 37 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadget/Kc
The u_rndis.ko module is used only by f_rndis_usb.ko module, so
the two can be merged.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |6 --
drivers/usb/gadget/Makefile |4 +---
2 files changed, 1 insertions(+), 9 deletions(-)
diff
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_rndis.c | 69 --
drivers/usb/gadget/u_ether.h | 35 -
2
Locally specified prototypes allow ccg stay insensible to changes
in mainline.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/staging/ccg/f_fs.c | 29 -
1 files changed, 28 insertions(+), 1 deletions(-)
diff --git a/drivers/staging/c
In order for f_fs.c to become a module it cannot be directly
sourced into other files. Consequently, if it itself includes
some header file with static function prototypes, it is no
good if the header is included in some other places.
This patch moves those static prototypes into the f_fs.c.
Since
Converting FunctionFS to the new function interface requires converting
the USB FunctionFS's function code and its users.
This patch converts the f_fs.c to the new function interface.
The file is now compiled into a separate usb_f_fs.ko module.
The old function interface is provided by means of pre
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_fs.c | 70 -
1 files changed, 0 insertions(+), 70 deletions(-)
diff --gi
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/g_ffs.c | 142 +--
2 files changed, 110 insertions(+), 33 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/multi.c | 41 +++--
2 files changed, 36 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadget/
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/g_ffs.c | 75 ++-
2 files changed, 67 insertions(+), 9 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadge
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_subset.c | 59 +
drivers/usb/gadget/u_ether.h |4 ---
2 files changed, 1
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/g_ffs.c | 36 +---
2 files changed, 34 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadget/Kconf
The old function interface included an rndis_bind_config function.
In order not to conflict with this function the new interface
used an rndis_new_bind_config. Now that the old interface is
removed the latter can be called rndis_bind_config to match
its counterpart eth_bind_config.
Signed-off-by:
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_ecm.c | 73 +-
drivers/usb/gadget/u_ether.h |2 -
2 files changed, 1 in
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/multi.c | 40 ++--
2 files changed, 35 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadget/K
Converting rndis to the new function interface requires converting
the USB rndis' function code and its users.
This patch converts the f_rndis.c to the new function interface.
The file is now compiled into a separate usb_f_rndis.ko module.
The old function interface is provided by means of a prepro
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/nokia.c | 52 ---
2 files changed, 44 insertions(+), 9 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadge
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/ncm.c | 50 ---
2 files changed, 38 insertions(+), 13 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/multi.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/gadget/multi.c b/drivers/usb/gadget/multi.c
index 2371084..9f63fdf 100644
--- a/drivers/usb/gadget/multi.c
+++ b/d
In order to convert usb functions to the new function interface
they need to be compiled as modules. This patch creates a u_ether
module which will be used by the new functions.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/Kconfig | 10 ++
In order to prepare for the new function interface the f_mass_storage.c
needs to be compiled as a module, and so a header file will be required.
This patch factors out some code to a new f_mass_storage.h.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/f
1 - 100 of 147 matches
Mail list logo
