Here I present the conversion of everthing that is required to provide
the equivalent of g_ncm.ko with configfs.
This is the second version of the series after discussion with Alan
and Michal's review - thank you guys.
A branch will be available here (from 24th April 2013):
git://git.infradead.or
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/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
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
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 1517652..8f675c0 100644
--- a/drivers
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
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.
On Wednesday, May 15, 2013 9:11 AM I wrote:
> Here I present the conversion of everthing that is required to provide the
> equivalent of g_ncm.ko with configfs.
>
> This is the second version of the series after discussion with Alan and
> Michal's review - thank you guys.
>
> A branch will be ava
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 15th May 2013, afternoon UTC):
git://git.infradead.org/users/kmpark/linux-samsung usb-gadget-configfs
v1..v2:
- fixed a bug resulting from the de
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
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 1b4f290..d89e1f3 100644
--- a/drivers/usb
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
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/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
Hi Peter,
On Wed, May 15, 2013 at 02:07:44AM +, Chen Peter-B29397 wrote:
>
> >
> > This patch adds iso endpoint support to the device controller.
> > It makes use of the multiplication bits in the maxpacket field
> > of the endpoint and calculates the multiplier bits for each
> > transfer d
All configuration left in d40_phy_cfg() is runtime configurable and
there is already a call into it from d40_runtime_config(), so let's
rely on that.
Acked-by: Vinod Koul
Acked-by: Arnd Bergmann
Signed-off-by: Lee Jones
---
drivers/dma/ste_dma40.c| 14 +++---
drivers/dma/ste_dma40_ll.c |
It was required to pass DMA channel configuration information to the
UART driver before the new DMA API was in place. Now that it is, and
is fully compatible with Device Tree we can stop doing that.
Reviewed-by: Linus Walleij
Signed-off-by: Lee Jones
---
arch/arm/mach-ux500/cpu-db8500.c |6
The DMA controller currently takes configuration information from
information passed though dma_channel_request(), but it shouldn't.
Using the API, the DMA channel should only be configured during
a dma_slave_config() call.
Cc: Herbert Xu
Cc: David S. Miller
Cc: Andreas Westin
Cc: linux-cry...@
Now the ux500-musb driver has been enabled for Device Tree, there is no
requirement to register it from platform code.
Acked-by: Fabio Baltieri
Signed-off-by: Lee Jones
---
arch/arm/mach-ux500/cpu-db8500.c |2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm/mach-ux500/cpu-db8500.c
We're now using the transfer direction definitions provided by the DMA
sub-system, so the home-brew ones have become obsolete.
Signed-off-by: Lee Jones
---
include/linux/platform_data/dma-ste-dma40.h | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/include/linux/pl
Some platforms have channels which are not available for normal use.
This information is currently passed though platform data in internal
BSP kernels. Once those platforms land, they'll need to configure them
appropriately, so we may as well add the infrastructure.
Cc: Vinod Koul
Cc: Dan William
Some platforms insist on obscure physical channel availability. This
information is currently passed though platform data in internal BSP
kernels. Once those platforms land, they'll need to configure them
appropriately, so we may as well add the infrastructure.
Cc: Vinod Koul
Cc: Dan Williams
Cc
The DMA platform data is now empty due to some recent refactoring,
so there is no longer a requirement to pass it though.
Acked-by: Arnd Bergmann
Signed-off-by: Lee Jones
---
arch/arm/mach-ux500/cpu-db8500.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/arm/mach-
At this moment in time the memcpy channels which can be used by the D40
are fixed, as each supported platform in Mainline uses the same ones.
However, platforms do exist which don't follow this convention, so
these will need to be tailored. Fortunately, these platforms will be DT
only, so this chan
Unsure of the author's intentions, rather than just removing the nop,
we're replacing it with a comment containing the possible intention
of the statement OR:ing with 0.
Cc: Vinod Koul
Cc: Dan Williams
Cc: Per Forlin
Cc: Rabin Vincent
Signed-off-by: Lee Jones
---
drivers/dma/ste_dma40_ll.c |
If we can ever get to a state where we can solely search for DMA channels
by name, this will almost completely alleviate the requirement to pass
copious amounts of information though platform data. Here we take the
first step towards this. The next step will be to enable Device Tree
complete with n
The aim is to make the code that little more readable.
Cc: Vinod Koul
Cc: Dan Williams
Cc: Per Forlin
Cc: Rabin Vincent
Signed-off-by: Lee Jones
---
drivers/dma/ste_dma40_ll.c | 44 ++--
1 file changed, 22 insertions(+), 22 deletions(-)
diff --git a
When a DMA client requests and configures a DMA channel, it requests
data_width in Bytes. The DMA40 driver then swiftly converts it over to
the necessary register bit value. Unfortunately, for any subsequent
calculations we have to shift '1' by the bit pattern (1 << data_width)
times to make any se
STEDMA40_*_TO_* direction definitions are identical in all but name to
the pre-defined generic DMA_*_TO_* ones. Let's make things easy by not
duplicating such things.
Cc: Vinod Koul
Cc: Dan Williams
Cc: Per Forlin
Cc: Rabin Vincent
Signed-off-by: Lee Jones
---
drivers/dma/ste_dma40.c|
STEDMA40_*_TO_* direction definitions are identical in all but name to
the pre-defined generic DMA_*_TO_* ones. Let's make things easy by not
duplicating such things.
Signed-off-by: Lee Jones
---
arch/arm/mach-ux500/board-mop500-audio.c | 12 ++--
arch/arm/mach-ux500/board-mop500-sdi.c
The aim is to make the code that little more readable.
Acked-by: Vinod Koul
Acked-by: Arnd Bergmann
Reviewed-by: Linus Walleij
Signed-off-by: Lee Jones
---
drivers/dma/ste_dma40.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/drivers/dma/ste_dma4
As promised, now all devices which resided in u8500_of_init_devices()
have been enabled for Device Tree, we can completely remove it.
Acked-by: Fabio Baltieri
Signed-off-by: Lee Jones
---
arch/arm/mach-ux500/cpu-db8500.c | 14 +-
1 file changed, 1 insertion(+), 13 deletions(-)
di
The recently DT:ed MUSB driver will require clock-name by device-name
look-up capability, until common clk has is properly supported by the
ux500 platform.
Acked-by: Linus Walleij
Acked-by: Fabio Baltieri
Signed-off-by: Lee Jones
---
arch/arm/mach-ux500/cpu-db8500.c |1 +
1 file changed, 1
This patch will allow ux500-musb to be probed and configured solely from
configuration found in Device Tree.
Cc: Felipe Balbi
Cc: Rob Herring
Cc: linux-usb@vger.kernel.org
Cc: devicetree-disc...@lists.ozlabs.org
Acked-by: Linus Walleij
Acked-by: Fabio Baltieri
Signed-off-by: Lee Jones
---
..
DMA addresses are now passed as part of the dmaengine API by invoking
dmaengine_slave_config(). So there's no requirement for the DMA40
driver to look them up in a table provided by platform data. This
method does not fit in well using Device Tree either.
Signed-off-by: Lee Jones
---
arch/arm/ma
If we fail to prepare the ux500-cryp clock before enabling it the
platform will fail to boot. Here we insure this happens.
Cc: Herbert Xu
Cc: David S. Miller
Cc: Andreas Westin
Cc: linux-cry...@vger.kernel.org
Acked-by: Ulf Hansson
Acked-by: Arnd Bergmann
Signed-off-by: Lee Jones
---
driver
DMA channel configuration information should be setup in the driver.
The Ux500 Hash driver now does this, so there's no need to send it
though here too.
Acked-by: Arnd Bergmann
Signed-off-by: Lee Jones
---
arch/arm/mach-ux500/board-mop500.c |4
1 file changed, 4 deletions(-)
diff --gi
The dma_mask will always be the same as the coherent_dma_mask, so let's
cut down on the platform_data burden and set it as such in the driver.
This also saves us from supporting it separately when we come to enable
this driver for Device Tree.
Cc: Felipe Balbi
Cc: linux-usb@vger.kernel.org
Acked-
In its current state, the ux500-musb driver uses platform data pointers
blindly with no prior checking. If no platform data pointer is passed
this will Oops the kernel. In this patch we ensure platform data and
board data are present prior to using them.
Cc: Felipe Balbi
Cc: linux-usb@vger.kernel
The MUSB HDRC configuration never changes between each of the ux500
supported platforms, so there's little point passing it though platform
data. If we set it in the driver instead, we can make good use of it
when booting with either ATAGs or Device Tree.
Cc: Felipe Balbi
Cc: linux-usb@vger.kerne
For all ux500 based platforms the maximum number of end-points are used.
Move this knowledge into the driver so we can relinquish the burden from
platform data. This also removes quite a bit of complexity from the driver
and will aid us when we come to enable the driver for Device Tree.
Cc: Felipe
These drivers are now operational and even use the latest common clk
and DMA APIs. There's no reason why we shouldn't start them up now.
Reviewed-by: Linus Walleij
Signed-off-by: Lee Jones
---
arch/arm/mach-ux500/board-mop500.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/m
The Cryp driver is currently silent and the Hash driver prints the
name of its probe function unnecessarily. Let's just put a nice
descriptive one-liner there instead.
Cc: Herbert Xu
Cc: David S. Miller
Cc: Andreas Westin
Cc: linux-cry...@vger.kernel.org
Acked-by: Arnd Bergmann
Reviewed-by: Li
DMA channel configuration information should be setup in the driver.
The Ux500 Cryp driver now does this, so there's no need to send it
though here too.
Reviewed-by: Linus Walleij
Acked-by: Arnd Bergmann
Signed-off-by: Lee Jones
---
arch/arm/mach-ux500/board-mop500.c |8
1 file ch
The DMA controller currently takes configuration information from
information passed though dma_channel_request(), but it shouldn't.
Using the API, the DMA channel should only be configured during
a dma_slave_config() call.
Cc: Herbert Xu
Cc: David S. Miller
Cc: Andreas Westin
Cc: linux-cry...@
If we fail to prepare the ux500-hash clock before enabling it the
platform will fail to boot. Here we insure this happens.
Cc: Herbert Xu
Cc: David S. Miller
Cc: Andreas Westin
Cc: linux-cry...@vger.kernel.org
Acked-by: Arnd Bergmann
Acked-by: Ulf Hansson
Signed-off-by: Lee Jones
---
driver
DMA data width and packet size information is only required at channel
configuration time. Any information passed from platform data is passed
directly to the DMA40 driver to use during channel allocation, but these
pieces of information are subsequently ignored by the driver, so we may
as well rem
'struct stedma40_half_channel_info's header comment says that it's
called 'struct stedma40_chan_cfg'. Let's straighten that out.
Signed-off-by: Lee Jones
---
include/linux/platform_data/dma-ste-dma40.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/platform_
A great deal of these patches have now been applied through various trees.
We now need to grab the attention of the outstanding DMA clients (MUSB and
Crypto) to progress.
Also, Linus could probably do with a hand from Vinod for the remaining
dmaengine patches.
Thanks in advance.
Documentation/d
During the initial setup of a logical channel, it is necessary to unmask
the GIM in order to receive generated terminal count and error interrupts.
We're separating out this required code so it will be possible to move
the remaining code in d40_phy_cfg(), which is mostly runtime configuration
into
It was required to pass DMA channel configuration information to the
MMC driver before the new DMA API was in place. Now that it is, and
is fully compatible with Device Tree we can stop doing that.
Reviewed-by: Linus Walleij
Signed-off-by: Lee Jones
---
arch/arm/mach-ux500/cpu-db8500.c |8 +
Now DMA DT bindings exist and are in use by he MMC and UART drivers, it
should be possible to remove them from the auxdata structure. However,
after doing so the drivers fail. Common clk is still reliant on the
dev_name() call to do device name matching, which will fail due to the
fact that Device
Addresses are now stored in local data structures and are easy to
obtain, thus a specialist function used to fetch them is now surplus
to requirement.
Signed-off-by: Lee Jones
---
drivers/dma/ste_dma40.c | 18 --
1 file changed, 18 deletions(-)
diff --git a/drivers/dma/ste_dma
Addresses are passed in from the client's driver via the invocation of
dmaengine_slave_config(), so there's no need to fetch them from platform
data too, hardwired or otherwise. This is a great step forward, as it
elevates a large burden from platform data in the way of a look-up
table.
Signed-off
Using the dmaengine API, allocating and configuring a channel are two
separate actions. Here we're removing logical channel configuration from
the channel allocating routines.
Cc: Vinod Koul
Cc: Dan Williams
Cc: Per Forlin
Cc: Rabin Vincent
Signed-off-by: Lee Jones
---
drivers/dma/ste_dma40.
Hi Michael & Marc,
Recently, I have worked at i.mx USB loadable module support for chipidea
driver,
it needs to write non-core register during the ci13xxx_imx remove process,
but currently, the usbmisc_imx is a driver, and it uses symbol from
ci13xxx_imx, so it will be unload first.
How about I
Peter Chen writes:
> Hi Michael & Marc,
>
> Recently, I have worked at i.mx USB loadable module support for chipidea
> driver,
> it needs to write non-core register during the ci13xxx_imx remove process,
> but currently, the usbmisc_imx is a driver, and it uses symbol from
> ci13xxx_imx, so it
On Wed, May 15, 2013 at 01:34:31PM +0300, Alexander Shishkin wrote:
> Peter Chen writes:
>
> > Hi Michael & Marc,
> >
> > Recently, I have worked at i.mx USB loadable module support for chipidea
> > driver,
> > it needs to write non-core register during the ci13xxx_imx remove process,
> > but c
Sascha Hauer writes:
> On Wed, May 15, 2013 at 01:34:31PM +0300, Alexander Shishkin wrote:
>> Peter Chen writes:
>>
>> > Hi Michael & Marc,
>> >
>> > Recently, I have worked at i.mx USB loadable module support for chipidea
>> > driver,
>> > it needs to write non-core register during the ci13x
On Wed, May 15, 2013 at 01:59:39PM +0300, Alexander Shishkin wrote:
> Sascha Hauer writes:
>
> > On Wed, May 15, 2013 at 01:34:31PM +0300, Alexander Shishkin wrote:
> >> Peter Chen writes:
> >>
> >> > Hi Michael & Marc,
> >> >
> >> > Recently, I have worked at i.mx USB loadable module support f
The current Makefile rules to build font support are messy and buggy.
Replace them by Kconfig rules:
- Introduce CONFIG_FONT_SUPPORT, which controls the building of all font
code,
- Select CONFIG_FONT_SUPPORT for all drivers that use fonts,
- Select CONFIG_FONT_8x16 for all drivers that d
On Wed 15 May 2013 13:40:50 Geert Uytterhoeven wrote:
> The current Makefile rules to build font support are messy and buggy.
> Replace them by Kconfig rules:
> - Introduce CONFIG_FONT_SUPPORT, which controls the building of all font
> code,
> - Select CONFIG_FONT_SUPPORT for all drivers th
Hello Felipe,
this is another series of updates for the ux500 specific musb drivers.
This mainly upgrade the phy-ab8500-usb driver by adding support for
clock control and new ab8500 variants, with some minor refactoring of
the existing code to better handle those.
Other patches includes some cod
From: Sakethram Bommisetti
Add an ab8500_usb_restart_phy() function called during probe to ensure
that the AB8500 USB phy is initialized properly even when a cable is
connected at probe time.
Without this fix subsequent host reconnections are not detected
properly.
Acked-by: Linus Walleij
Acke
Add an initial platform_device_id table to the ab8500-usb driver to
allow probing additional variants of the ab8500 family chips.
Acked-by: Linus Walleij
Acked-by: Maxime Coquelin
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-ab8500-usb.c | 10 --
1 file changed, 8 insertions(+
Move each chip's PHY tuning value set code to a separate function to
improve code readability.
Acked-by: Linus Walleij
Acked-by: Maxime Coquelin
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-ab8500-usb.c | 161 +--
1 file changed, 86 insertions(+), 7
Introduce a "flags" field in "struct ab8500_usb" to allow controlling
driver features and quirks depending on ab8500 chip variant and
revision.
Acked-by: Linus Walleij
Acked-by: Maxime Coquelin
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-ab8500-usb.c | 109 ++-
Add support for the ab8540 variant of the ab8500 family.
Acked-by: Linus Walleij
Acked-by: Maxime Coquelin
Cc: Avinash Kumar
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-ab8500-usb.c | 297 ++-
1 file changed, 294 insertions(+), 3 deletions(-)
dif
The driver supports both ab8500 and ab8505, but the actual phy tuning
values logic sets ab8500 values:
if (!is_ab8500_2p0_or_earlier(ab->ab8500))
which is supposed to set values for ab8500, but incorrectly results true
for ab8505 too.
Fix this by adding an additional is_ab8500(ab->ab8500) check.
Various non functional coding style fixes on ux500_dma.c and
phy-ab8500-usb.c drivers.
Acked-by: Linus Walleij
Acked-by: Maxime Coquelin
Signed-off-by: Fabio Baltieri
---
drivers/usb/musb/ux500_dma.c | 6 +++---
drivers/usb/phy/phy-ab8500-usb.c | 9 +
2 files changed, 8 insertions(
From: Mian Yousaf Kaukab
Add common clock support code for the ab8500-usb phy driver.
Acked-by: Linus Walleij
Acked-by: Maxime Coquelin
Signed-off-by: Mian Yousaf Kaukab
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-ab8500-usb.c | 14 ++
1 file changed, 14 insertions(+)
From: Mian Yousaf Kaukab
Host side dma support for ux500 is enabled by piggybacking on Inventra
dma support.
Acked-by: Linus Walleij
Signed-off-by: Mian Yousaf Kaukab
Signed-off-by: Fabio Baltieri
---
drivers/usb/musb/musb_host.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
Add support for the ab9540 variant of the ab8500 family.
Acked-by: Linus Walleij
Acked-by: Maxime Coquelin
Cc: Avinash Kumar
Cc: Thirupathi Chippakurthy
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-ab8500-usb.c | 213 +++
1 file changed, 213 inser
/drivers/net/usb/qmi_wwan.c: Added support for Cinterion's PLxx WWAN Interface
by adding QMI_FIXED_INTF with Cinterion's Vendor ID as well as Product ID and
WWAN Interface Number.
Signed-off-by: Hans-Christoph Schemmel
gemalto.com>
Signed-off-by: Christian Schmiedl gemalto.com>
---
patch is aga
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 15th May 2013, afternoon UTC):
git://git.infradead.org/users/kmpark/linux-samsung usb-gadget-configfs
This series requires the following series
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/f_obex.c | 19 ---
1 files changed, 8 insertions(+), 11 deletions(-)
diff --git a/drivers/usb/gadget/f_obex.c b/drivers/usb/gadget/f_obex.c
index 29a348a..be2d762 100644
--- a/drivers/usb/
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/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/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
---
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/Kconfig| 10 +++
drivers/usb/gadget/f_phonet.c | 56 +
2 files changed, 66 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/gadget/Kconfig b/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
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 | 54 ---
1 files changed, 0 insertions(+), 54 deletions(-)
diff --gi
The mxs-phy is missing the phy.type property, why the usb_get_phy helper
function won't be able to find it. This patch adds this missing property.
Signed-off-by: Michael Grzeschik
---
drivers/usb/phy/phy-mxs-usb.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/phy/phy-mxs-usb.c
Hello.
On 15-05-2013 16:28, Schmiedl Christian wrote:
/drivers/net/usb/qmi_wwan.c: Added support for Cinterion's PLxx WWAN Interface
by adding QMI_FIXED_INTF with Cinterion's Vendor ID as well as Product ID and
WWAN Interface Number.
Signed-off-by: Hans-Christoph Schemmel
gemalto.com>
Sign
/drivers/net/usb/qmi_wwan.c: Added support for Cinterion's PLxx WWAN Interface
by adding QMI_FIXED_INTF with Cinterion's Vendor ID as well as Product ID and
WWAN Interface Number.
Signed-off-by: Hans-Christoph Schemmel
Signed-off-by: Christian Schmiedl
---
patch is against linux-3.9
--- linux-3.
Hi,
On Tue, Apr 30, 2013 at 11:02:18PM +0400, Sergei Shtylyov wrote:
> >BTW, conversion away from iowrite32() could (should) be part of a
> >separate patch. No need to prevent this one from being applied.
> >
>
>Of course. You mean conversion to plain writel(), right?
right, "away" from iowr
Hello.
On 15-05-2013 18:01, Felipe Balbi wrote:
BTW, conversion away from iowrite32() could (should) be part of a
separate patch. No need to prevent this one from being applied.
Of course. You mean conversion to plain writel(), right?
right, "away" from iowrite32() ;-)
Well, I us
On Fri, May 03, 2013 at 11:01:33AM -0700, Tony Lindgren wrote:
> * Tony Lindgren [130503 10:55]:
> > Looks like we can get VBUS interrupt before the ID interrupt
how can this happen ? VBUS interrupt happens when you connect to a port
which is sourcing VBUS to you, while ID interrupt happens when
Hi,
On Wed, May 08, 2013 at 06:14:43PM +0200, Ben Dooks wrote:
> >>>* Ben Dooks | 2013-05-07 22:06:33 [+0200]:
> >>>
> We are using an OMAP5432 ES2.0 on an UEVM board
> and running into issues with the dwc3 usb.
> >>>
> >>>Sorry, I can't help at all. I don't have the board and I never had
On 15/05/13 15:09, Felipe Balbi wrote:
Hi,
On Wed, May 08, 2013 at 06:14:43PM +0200, Ben Dooks wrote:
* Ben Dooks | 2013-05-07 22:06:33 [+0200]:
We are using an OMAP5432 ES2.0 on an UEVM board
and running into issues with the dwc3 usb.
Sorry, I can't help at all. I don't have the board and
On Tuesday 14 May 2013, Alan Stern wrote:
> The Kconfig settings for uhci-hcd are too permissive; they allow the
> driver to be built without any bus-glue modules configured
> (USB_UHCI_HCD enabled, PCI disabled, SPARC_LEON disabled, ARCH_VT8500
> enabled, and USB_UHCI_PLATFORM disabled).
>
> This
On Tue, 14 May 2013, Sarah Sharp wrote:
> On Wed, May 15, 2013 at 04:56:00AM +0300, Xenia Ragiadakou wrote:
> > Hi Sarah,
>
> Hi Ksenia!
>
> > In xhci.c line 4665, the function dma_set_mask is used to enable
> > 64-bit DMA addressing
> > (if i understood correctly).
> >
> > However, accordingly
On 05/09/2013 11:22 PM, Svetoslav Neykov wrote:
> Hi Marc,
>
> Marc Kleine-Budde [mailto:m...@pengutronix.de] (On Thursday, March 28, 2013
> 4:16 PM)
>> On 03/28/2013 10:28 AM, Alexander Shishkin wrote:
>>> Svetoslav Neykov writes:
>>>
Convert between big-endian and little-endian format when
Hi,
On Wed, May 15, 2013 at 03:15:44PM +0100, Ben Dooks wrote:
> It seems the board is very picky about what it will play host to
> as neither of the mini-b to A adapters I have work. I am using
> a mini B to mini B cable to run the card reader.
>
> I have still got the disabl
On 15/05/13 15:30, Felipe Balbi wrote:
Hi,
On Wed, May 15, 2013 at 03:15:44PM +0100, Ben Dooks wrote:
It seems the board is very picky about what it will play host to
as neither of the mini-b to A adapters I have work. I am using
a mini B to mini B cable to run the card reader.
I have still go
Hi,
On Wed, Apr 17, 2013 at 09:22:36AM +0800, Chao Xie wrote:
> On Wed, Apr 17, 2013 at 9:17 AM, Chao Xie wrote:
> >
> > On Sun, Apr 7, 2013 at 6:29 PM, Chao Xie wrote:
> >>
> >> The patches create the mv-usb phy driver
> >>
> >>
> >> directly use devm_usb_get_phy_dev return value for error re
1 - 100 of 139 matches
Mail list logo
