On Fri, Mar 15, 2013 at 12:37:01PM +0200, Felipe Balbi wrote:
Hi,
On Fri, Mar 15, 2013 at 06:04:08PM +0800, Peter Chen wrote:
On Fri, Mar 15, 2013 at 09:51:29AM +0200, Felipe Balbi wrote:
that's all wrong and needs to be fixed. UDC-core has to be the central
point for all these
My laptop is an Acer 1810T. I see this error message each boot.
Kind regards
Thomas
Jiri Kosina jkos...@suse.cz schrieb:
On Fri, 15 Mar 2013, Jiri Kosina wrote:
I have the same problem on my Lenovo T500. I think the graphics card is
involved.
This laptop has hybrid graphics - one
The origianl understanding of clock is wrong. The UDC controller
only have one clock input.
Passing clock name by pdata is wrong. The clock is defined by device
iteself.
Signed-off-by: Chao Xie chao@marvell.com
---
drivers/usb/gadget/mv_udc.h |3 +--
drivers/usb/gadget/mv_udc_core.c
The origianl understanding of clock is wrong. The OTG controller
only have one clock input.
Passing clock name by pdata is wrong. The clock is defined by device
iteself.
Signed-off-by: Chao Xie chao@marvell.com
---
drivers/usb/otg/mv_otg.c | 28 +++-
The origianl understanding of clock is wrong. The EHCI controller
only have one clock input.
Passing clock name by pdata is wrong. The clock is defined by device
iteself.
Signed-off-by: Chao Xie chao@marvell.com
---
drivers/usb/host/ehci-mv.c | 35 ++-
1
Using pdata to pass clock name is not correct.
Directly get clock from usb drivers.
Signed-off-by: Chao Xie chao@marvell.com
---
include/linux/platform_data/mv_usb.h |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/include/linux/platform_data/mv_usb.h
The clock is defined by device, so the driver knows how many
clocks needed by the device.
The orignal way that passing the clock name by pdata is not correct.
The following patches fix it.
Chao Xie (6):
usb: gadget: mv_udc_core: remove unused clock
usb: otg: mv_otg: remove unused clock
usb:
The clock name will directly get by driver. Removing
the name from pdata.
Signed-off-by: Chao Xie chao@marvell.com
---
arch/arm/mach-mmp/aspenite.c |6 --
1 files changed, 0 insertions(+), 6 deletions(-)
diff --git a/arch/arm/mach-mmp/aspenite.c b/arch/arm/mach-mmp/aspenite.c
index
The clock name will directly get by driver. Removing
the name from pdata.
Signed-off-by: Chao Xie chao@marvell.com
---
arch/arm/mach-mmp/ttc_dkb.c |6 --
1 files changed, 0 insertions(+), 6 deletions(-)
diff --git a/arch/arm/mach-mmp/ttc_dkb.c b/arch/arm/mach-mmp/ttc_dkb.c
index
Hi,
On Fri, Mar 15, 2013 at 03:12:08PM -0600, Stephen Warren wrote:
On 03/15/2013 03:12 AM, Felipe Balbi wrote:
PHY layer no longer returns NULL, we must
switch from IS_ERR_OR_NULL() to IS_ERR().
This change will definitely conflict with some Tegra EHCI/USB-PHY
changes that Venu plans to
On Fri, Mar 15, 2013 at 09:37:36PM +0530, kishon wrote:
On Friday 15 March 2013 08:09 PM, Felipe Balbi wrote:
From: Kishon Vijay Abraham I kis...@ti.com
musb does not use DMA buffer for ep0 but it uses the same giveback
function *musb_g_giveback* for all endpoints (*musb_g_ep0_giveback*
On Fri, Mar 15, 2013 at 08:47:39AM -0700, Greg KH wrote:
On Fri, Mar 15, 2013 at 04:37:56PM +0100, Jiri Kosina wrote:
On Fri, 15 Mar 2013, Greg KH wrote:
I have the same problem on my Lenovo T500. I think the graphics card
is
involved.
This laptop has hybrid
with the latest udc_start/udc_stop conversion,
too much code was deleted which ended up creating
a regression in net2272 and net2280 drivers.
To fix the regression we revert one hunk of the
original commits.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/net2272.c | 7 +++
On 21:16 Fri 08 Mar , Greg Kroah-Hartman wrote:
On Fri, Mar 08, 2013 at 11:56:26PM +0400, Sergei Shtylyov wrote:
Hello.
On 08-03-2013 16:53, oskar.and...@sonymobile.com wrote:
From: Truls Bengtsson truls.bengts...@sonymobile.com
The udc_irq service runs the
On Sunday 17 March 2013 21:00:06 Bjørn Mork wrote:
Aleksander Morgado:
We do really need max message size for MBIM; and as you say, it may be
good to have the max message size info also for QMI, so the new ioctl
seems a good addition. So +1 from my side, for what it's worth.
Dan
Hi,
On Mon, Mar 18, 2013 at 01:50:55PM +0530, kishon wrote:
@@ -141,7 +141,7 @@ static inline void map_dma_buffer(struct musb_request
*request,
static inline void unmap_dma_buffer(struct musb_request *request,
struct musb *musb)
{
- if
On Fri, Mar 08, 2013 at 05:56:11PM +0200, Felipe Balbi wrote:
Hi,
On Fri, Mar 08, 2013 at 08:37:00PM +0800, Peter Chen wrote:
On Fri, Mar 08, 2013 at 01:30:52PM +0200, Felipe Balbi wrote:
this method will be used to enable or disable
the charge pump.
Whenever we have DRD
On Monday 18 March 2013 02:12 PM, Felipe Balbi wrote:
Hi,
On Mon, Mar 18, 2013 at 01:50:55PM +0530, kishon wrote:
@@ -141,7 +141,7 @@ static inline void map_dma_buffer(struct musb_request
*request,
static inline void unmap_dma_buffer(struct musb_request *request,
On Mon, Mar 18, 2013 at 02:17:52PM +0530, kishon wrote:
On Monday 18 March 2013 02:12 PM, Felipe Balbi wrote:
Hi,
On Mon, Mar 18, 2013 at 01:50:55PM +0530, kishon wrote:
@@ -141,7 +141,7 @@ static inline void map_dma_buffer(struct
musb_request *request,
static inline void
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
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
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig|1 +
drivers/usb/gadget/mass_storage.c | 118 +++-
2 files changed, 76 insertions(+), 43 deletions(-)
diff
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
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/ncm.c | 50 ---
2 files changed, 38 insertions(+), 13 deletions(-)
diff --git
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
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 andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/cdc2.c | 57 +++
2 files changed, 42 insertions(+), 16 deletions(-)
diff --git
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
There are no old function interface users left, so the old interface
can be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_ncm.c | 81 +-
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/ether.c | 44 ++--
2 files changed, 39 insertions(+), 6 deletions(-)
diff --git
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/ether.c | 43 +--
2 files changed, 38 insertions(+), 6 deletions(-)
diff --git
In order to convert to configfs the USB functions need to be converted
to the new interface from Sebastian, which also requires turning them
into separate modules. Some of these modules will consist of just
one object file, e.g. f_ncm.o. But some of the modules will eventually
consist of more than
This is a continuation of this thread:
http://www.spinics.net/lists/linux-usb/msg78189.html
The prerequisite for providing the configfs interface for USB gadgets and
all their users is converting them to the new function interface from Sebastian.
This patch series serves the purpose stated
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/g_ffs.c | 75 ++-
2 files changed, 67 insertions(+), 9 deletions(-)
diff --git
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 andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/nokia.c | 52 ---
2 files changed, 44 insertions(+), 9 deletions(-)
diff --git
There are no old function interface users left, so the old interface
can be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_ecm.c | 73 +-
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
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
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
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/multi.c | 40 ++--
2 files changed, 35 insertions(+), 6 deletions(-)
diff --git
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/g_ffs.c | 36 +---
2 files changed, 34 insertions(+), 3 deletions(-)
diff --git
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:
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/ether.c | 39 ---
2 files changed, 37 insertions(+), 3 deletions(-)
diff --git
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 andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |6 --
drivers/usb/gadget/Makefile |4 +---
2 files
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/g_ffs.c | 51 +--
2 files changed, 49 insertions(+), 3 deletions(-)
diff --git
There are no old function interface users left, so the old interface
can be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_rndis.c | 69 --
There are no old function interface users left, so the old interface
can be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_fs.c | 70 -
1 files
Converting f_serial to the new function interface requires converting
the f_serial's function code and its users.
This patch converts the f_serial.c to the new function interface.
The file is now compiled into a separate usb_f_serial.ko module.
The old function interface is provided by means of
There are no old function interface users left, so the old interface
can be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_serial.c | 46 -
1 files
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
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/serial.c | 25 +++--
2 files changed, 8 insertions(+), 18 deletions(-)
diff --git
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/nokia.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/gadget/nokia.c b/drivers/usb/gadget/nokia.c
index 5b98239..a466f4d
Locally specified prototypes allow ccg stay insensible to changes
in mainline.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/staging/ccg/f_fs.c | 29 -
1 files changed, 28 insertions(+),
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/g_ffs.c | 142 +--
2 files changed, 110 insertions(+), 33 deletions(-)
diff --git
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
There are no old function interface users left, so the old interface
can be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_subset.c | 59 +
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/ether.c | 41 -
2 files changed, 37 insertions(+), 5 deletions(-)
diff --git
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/multi.c | 41 +++--
2 files changed, 36 insertions(+), 6 deletions(-)
diff --git
There are no old function interface users left, so the old interface
can be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_eem.c | 57 --
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
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/multi.c | 69 +++-
2 files changed, 50 insertions(+), 20 deletions(-)
diff --git
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
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 andrze...@samsung.com
Signed-off-by: Kyungmin Park
On Fri, 15 Mar 2013, Yinghai Lu wrote:
Just a datapoint -- I have put a trivial debugging patch in place, and it
reveals that nobody cared for irq 16 happens long after last
I915_WRITE(GMBUS4 + reg_offset, 0);
has been performed in gmbus_wait_hw_status(). On the other hand, if
Without this memory barrier, the file-storage thread may fail to
escape from the following while loop, because it may observe new
common-thread_wakeup_needed and old bh-state which are updated by
the callback functions.
/* Wait for the CBW to arrive */
while (bh-state !=
On Monday, March 18, 2013 10:09 AM I wrote:
Subject: [PATCH v4 00/46] Towards configfs - usb functions conversion to
the new interface
snip
The prerequisite for providing the configfs interface for USB gadgets and
all their users is converting them to the new function interface from
Hi,
I tried to modify fusbh200 hcd driver following ehci-platform.c.
However, the register definition of fusbh200 is partially incompatible
to ehci. For fusbh200, only the elements between command and
async_next in struct ehci_regs are consistent with ehci which means
it would cause copious
Hi,
(don't top-post)
On Mon, Mar 18, 2013 at 06:06:18PM +0800, Yuan-Hsin Chen wrote:
Hi,
I tried to modify fusbh200 hcd driver following ehci-platform.c.
However, the register definition of fusbh200 is partially incompatible
to ehci. For fusbh200, only the elements between command and
Hello.
On 18-03-2013 12:19, Felipe Balbi wrote:
with the latest udc_start/udc_stop conversion,
too much code was deleted which ended up creating
a regression in net2272 and net2280 drivers.
To fix the regression we revert one hunk of the
original commits.
Signed-off-by: Felipe Balbi
On Monday, March 18, 2013 10:09 AM I wrote:
Subject: [PATCH v4 00/46] Towards configfs - usb functions conversion to
the new interface
snip
The prerequisite for providing the configfs interface for USB gadgets and
all their users is converting them to the new function interface from
On Mon, Mar 18, 2013 at 12:41:53PM +0100, Andrzej Pietrasiewicz wrote:
On Monday, March 18, 2013 10:09 AM I wrote:
Subject: [PATCH v4 00/46] Towards configfs - usb functions conversion to
the new interface
snip
The prerequisite for providing the configfs interface for USB
Hi,
On Mon, Mar 18, 2013 at 10:23:32AM +0100, Andrzej Pietrasiewicz wrote:
The prerequisite for providing the configfs interface for USB gadgets and
all their users is converting them to the new function interface from
Sebastian.
This patch series serves the purpose stated above for
On Fri, 2013-03-15 at 16:20 +0100, Johan Hovold wrote:
Either way, this series moves the wake-up from the individual driver's
port remove to usb-serial disconnect and before unregistering the device
from the bus.
However, looking at this again now, I realise that the wake up must be
done in
The existing Tegra USB bindings have a few issues:
1) Many properties are documented as being part of the EHCI controller
node, yet they apply more to the PHY device. They should be moved.
2) Some registers in PHY1 are shared with PHY3, and hence PHY3 needs a
reg entry to point at PHY1's
As GPIO information is avail through DT, used it to get Tegra ULPI
reset GPIO number. Added a new member to tegra_usb_phy structure to
store this number.
Signed-off-by: Venu Byravarasu vbyravar...@nvidia.com
---
drivers/usb/phy/tegra_usb_phy.c | 25 +++--
Registered tegra USB PHY as a separate platform driver.
To synchronize host controller and PHY initialization, used deferred
probe mechanism. As PHY should be initialized before EHCI starts running,
deferred probe of Tegra EHCI driver till PHY probe gets completed.
Got rid of instance number
This patch updates all Tegra board files so that they contain all the
properties required by the updated USB DT binding. Note that this patch
only adds the new properties and does not yet remove the old properties,
in order to maintain bisectability. The old properties will be removed
once the
Added a new PHY mode to support OTG.
Obtained Tegra USB PHY mode using DT property.
Signed-off-by: Venu Byravarasu vbyravar...@nvidia.com
---
drivers/usb/host/ehci-tegra.c |3 +--
drivers/usb/phy/tegra_usb_phy.c | 13 +++--
include/linux/usb/tegra_usb_phy.h |3 ++-
3
In case if clk_get_sys fails, return correct error value provided by
the API.
Signed-off-by: Venu Byravarasu vbyravar...@nvidia.com
---
drivers/usb/phy/tegra_usb_phy.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/phy/tegra_usb_phy.c
As part of this series, apart from patch containing changes to register TEGRA
USB PHY driver as platform driver, prepared below patches:
1. Re-arranging adding new DT properties.
2. Getting various params from DT properties added.
3. code clean up.
Venu Byravarasu (7):
ARM: tegra: finalize USB
Use usbhs_init_phys() to register the PHY's VCC and RESET
regulators and the NOP PHY device.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c | 32 +-
1 files changed, 22 insertions(+), 10 deletions(-)
diff --git
This helper allows board support code to add the PHY's
VCC and RESET regulators which are GPIO controlled as well
as the NOP PHY device.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/usb-host.c | 177 +++-
arch/arm/mach-omap2/usb.h |
Hi Tony,
I've revised the patches based on your comments. For now I've just
adapted Panda and Beagleboard.
If this looks OK then I can adapt the other boards as well.
cheers,
-roger
Roger Quadros (4):
usb: phy: nop: Add some parameters to platform data
ARM: OMAP2+: omap-usb-host: Add
Use usbhs_init_phys() to register the PHY's VCC and RESET
regulators and the NOP PHY device.
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.
Signed-off-by: Roger Quadros
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
Hello.
On 18-03-2013 16:29, Venu Byravarasu wrote:
As GPIO information is avail through DT, used it to get Tegra ULPI
reset GPIO number. Added a new member to tegra_usb_phy structure to
store this number.
Signed-off-by: Venu Byravarasu vbyravar...@nvidia.com
---
On Thu, Mar 07, 2013 at 11:54:03PM +0100, Michael Grzeschik wrote:
Hey Alex,
On Thu, Jan 24, 2013 at 11:42:53AM +0200, Alexander Shishkin wrote:
Peter Chen peter.c...@freescale.com writes:
On Tue, Nov 27, 2012 at 05:16:55PM +0100, Michael Grzeschik wrote:
Nearly every SoC from
This device has an odd HID entry and causes a 10 second delay in boot.
Add this device to the quirks list with HID_QUIRK_NO_INIT_REPORTS.
This fixes Red Hat bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=806587
Signed-off-by: Josh Boyer jwbo...@redhat.com
---
drivers/hid/hid-ids.h
This keyboard backlight device causes a 10 second delay to boot. Add it
to the quirk list with HID_QUIRK_NO_INIT_REPORTS.
This fixes Red Hat bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=907221
Signed-off-by: Josh Boyer jwbo...@redhat.com
---
drivers/hid/hid-ids.h | 3 +++
Hi,
On Fri, Mar 15, 2013 at 8:58 AM, Jingoo Han jg1@samsung.com wrote:
On Friday, March 15, 2013 12:16 PM, Doug Anderson wrote:
The ehci_vbus_gpio is requested but never freed. This can cause
problems with deferred probes and would cause problems if
s5p_ehci_remove was ever called.
On Mon, Mar 18 2013, UCHINO Satoshi wrote:
Without this memory barrier, the file-storage thread may fail to
escape from the following while loop, because it may observe new
common-thread_wakeup_needed and old bh-state which are updated by
the callback functions.
/* Wait for the CBW to
On Mon, 18 Mar 2013, Josh Boyer wrote:
This device has an odd HID entry
I can't really say I understand this portion of the changelog.
I will rephrase it a little bit and apply, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the
On Mon, 18 Mar 2013, Josh Boyer wrote:
This keyboard backlight device causes a 10 second delay to boot. Add it
to the quirk list with HID_QUIRK_NO_INIT_REPORTS.
Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a
On Mon, 18 Mar 2013, Felipe Balbi wrote:
On Mon, Mar 18, 2013 at 06:06:18PM +0800, Yuan-Hsin Chen wrote:
Hi,
I tried to modify fusbh200 hcd driver following ehci-platform.c.
However, the register definition of fusbh200 is partially incompatible
to ehci. For fusbh200, only the elements
On Mon, Mar 18, 2013 at 02:52:32PM +0100, Jiri Kosina wrote:
On Mon, 18 Mar 2013, Josh Boyer wrote:
This device has an odd HID entry
I can't really say I understand this portion of the changelog.
I just took it from what Hans said in the bug. I believe I might have
misunderstood.
I
On Fri, Mar 08, 2013 at 05:54:37PM +0200, Alexander Shishkin wrote:
Michael Grzeschik m.grzesc...@pengutronix.de writes:
A static count of transfer descriptors was used everywhere in the driver
with the fixed number 4. This patch adds a define, named TD_COUNT, and
replaces all users of
From: Du Xing duxing2...@gmail.com
In skel_read,the reader blocked in wait_for_completion before submit bulk in
urb.
Using processed_urb is for retaining the completion in the case that
previous interruptible wait in skel_read was interrupted and complete before
next skel_read.
Replacing
On Mon, 18 Mar 2013, Noone Nowhere wrote:
I can't fix the block count issue. That's not a bug in the program;
it's a bug somewhere else.
Who can fix it? Should we test another stick?
That depends on where the bug is. If it is in the stick then testing
a different brand of flash drive
On Mon, Mar 18, 2013 at 09:28:07AM +0100, oskar.and...@sonymobile.com wrote:
On 21:16 Fri 08 Mar , Greg Kroah-Hartman wrote:
On Fri, Mar 08, 2013 at 11:56:26PM +0400, Sergei Shtylyov wrote:
Hello.
On 08-03-2013 16:53, oskar.and...@sonymobile.com wrote:
From: Truls Bengtsson
On 03/18/2013 02:02 AM, Felipe Balbi wrote:
Hi,
On Fri, Mar 15, 2013 at 03:12:08PM -0600, Stephen Warren wrote:
On 03/15/2013 03:12 AM, Felipe Balbi wrote:
PHY layer no longer returns NULL, we must switch from
IS_ERR_OR_NULL() to IS_ERR().
This change will definitely conflict with some
1 - 100 of 166 matches
Mail list logo
