regset is a generic implementation of regdump
utility through debugfs.
Signed-off-by: Felipe Balbi
---
Hi Greg, would you take the patch below to debugfs ? I don't think debugfs
should ever change whatever's passed through struct debugfs_reg32 anyway.
struct debugfs_regset32 {
- struct d
smatch reports the following warnings:
drivers/net/can/usb/esd_usb2.c:640 esd_usb2_start() error: doing dma on the
stack (&msg)
drivers/net/can/usb/esd_usb2.c:846 esd_usb2_close() error: doing dma on the
stack (&msg)
drivers/net/can/usb/esd_usb2.c:855 esd_usb2_close() error: doing dma on the
sta
> "Dan" == Dan Carpenter writes:
Dan> The callers expect this function to return zero on success or -EIO if it
Dan> times out. The type should be int instead of unsigned short.
Dan> Signed-off-by: Dan Carpenter
Acked-by: Peter Korsgaard
Dan> diff --git a/drivers/usb/c67x00/c67x00-l
Changes from v8:
Resending this patch series after rebasing to the latest usb-next branch.
Rewording inline comments for better readability.
Removed IS_ENABLED(CONFIG_OF) as pdev->dev.of_node is enough to check for dt
support.
Using of_match_ptr to add of_match_table to platform_driver structure.
This driver uses usb_phy interface to interact with s3c-hsotg. Supports
phy_init and phy_shutdown functions to enable/disable usb phy. Support
will be extended to host controllers and more Samsung SoCs.
Signed-off-by: Praveen Paneri
Acked-by: Heiko Stuebner
Acked-by: Kyungmin Park
---
.../devi
Adding the transceiver to hsotg driver. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Praveen Paneri
Acked-by: Kyungmin Park
---
drivers/usb/gadget/s3c-hsotg.c | 37 +++--
1 files changed, 27 inserti
The code in the driver is based on the specs from ADMTek (later,
Infineon). Since i never suspend my machines this feature has not been
tested by me.
However, if the proposed patch is the right thing to do i'd be happy to
see it applied.
cheers,
Petko
On Fri, 18 Jan 2013, Ming Lei wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control module registers for doing the above task which was
previously done in omap glu
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control module registers for doing the above task which was
previously done in omap glu
Start using the control module driver for powering on the PHY and for
writing to the mailbox instead of writing to the control module
registers on their own.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/usb/omap-usb.txt |4 ++
Documentation/devicetree/bindings/
Added has_mailbox to the musb platform data to specify that omap uses
an external mailbox (in control module) to communicate with the musb
core during device connect and disconnect.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/mach-omap2/usb-musb.c |3 +++
include/linux/usb/musb.h
A seperate driver has been added to handle the usb part of control
module. A device for the above driver is created here, using the register
address information to be used by the driver for powering on the PHY and
for writing to the mailbox.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/mac
On 01/17/2013 06:59 PM, Tony Lindgren wrote:
> * Alan Stern [130117 07:19]:
>> On Thu, 17 Jan 2013, Roger Quadros wrote:
>>
>>> Let's have a single platform data structure for the OMAP's High-Speed
>>> USB host subsystem instead of having 3 separate ones i.e. one for
>>> board data, one for USB Ho
This patch series adds dt data to get MUSB working in omap4 and omap3.
Long time back a patch series with the same title was sent but only
a part of it got merged. The rest of it wasn't merged because of
adding omap control usb data to glue and usb phy.
Now there exists a separate driver for contr
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-.dts file.
The dt data specifies among others the interface type (ULPI or UTMI), mode
which is mostly OTG, power that specifies the amount of power this can supply
when in host mode.
Ac
Add omap control usb data in omap4 device tree file. This will have the
register address of registers to power on the PHY and to write to
mailbox.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap4.dtsi |8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/d
Add omap-usb2 data node in omap4 device tree file. Since omap-usb2 is
connected to ocp2scp, omap-usb2 dt data is added as a child node
of ocp2scp.
Acked-by: Felipe Balbi
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap4.dtsi |4
1 file changed, 4 insertions(+)
diff --g
On Fri, Jan 18, 2013 at 5:57 AM, Andrew Morton
wrote:
>
> Fair enough, thanks.
>
> I grabbed the patches for 3.9-rc1. It is good that the page
> allocator's newly-added test of current->flags is not on the fastpath.
>
Andrew, great thanks, :-)
Also thank Alan, Oliver, Minchan, Rafael, Greg and
On Fri, Jan 18, 2013 at 10:50:28AM +0800, Peter Chen wrote:
> +#ifdef CONFIG_PM
> +static int ci13xxx_imx_suspend(struct device *dev)
> +{
> + struct ci13xxx_imx_data *data =
> + platform_get_drvdata(to_platform_device(dev));
Is there a reason not to use dev_get_drvdata() here? Hi
Hi,
On Friday 18 January 2013 03:25 AM, Richard Genoud wrote:
Hi,
I've got an usb3.0 HDD dock ( http://www.icydock.com/goods.php?id=130
) wich uses JMicron JMS539 chipset and an USB3.0 board based on VIA
VL800 B3 ( http://www.ldlc.com/fiche/PB00130847.html )
When I plug the dock in an UBS3.0 por
Hi Chao,
You latest patches caused another breakage for x86. Please fix it asap
or I will have to drop all your changes from my pull request.
ERROR: "mv_usb2_unregister_notifier" [drivers/usb/gadget/mv_udc.ko] undefined!
ERROR: "mv_usb2_register_notifier" [drivers/usb/gadget/mv_udc.ko] undefined!
On 2013年01月16日 23:45, Alan Stern wrote:
> On Tue, 15 Jan 2013, Lan Tianyu wrote:
>
>> Hi Greg&Alan:
>> Do you have some more comments about this patchset? Thanks.
>
> I don't have any more comments at this point. It looks okay to me.
>
> Acked-by: Alan Stern
>
> By the way, have you chec
drivers/usb/gadget/u_serial.c:1291:5: sparse: symbol \
'userial_init' was not declared. Should it be static?
drivers/usb/gadget/zero.c:66:25: sparse: symbol \
'gzero_options' was not declared. Should it be static?
Reported-by: Fengguang Wu
Signed-off-by: Felipe Balbi
---
drivers
dwc3_gadget_set_ep_config expects maxburst as incremented by 1. So, by
default initialize ep->maxburst to 1 for ep0.
Signed-off-by: Pratyush Anand
---
drivers/usb/dwc3/gadget.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/g
Hi,
On Tue, Jan 15, 2013 at 02:12:51PM +0530, Kishon Vijay Abraham I wrote:
> Added a new driver for the usb part of control module. This has an API
> to power on the USB2 phy and an API to write to the mailbox depending on
> whether MUSB has to act in host mode or in device mode.
>
> Writing to
On Thu, Jan 17, 2013 at 04:44:52PM +0530, kishon wrote:
> >>@@ -171,6 +188,11 @@ static inline void devm_usb_put_phy(struct device
> >>*dev, struct usb_phy *x)
> >> {
> >> }
> >>
> >>+static inline struct usb_phy_bind *usb_bind_phy(const char *dev_name, u8
> >>index,
> >>+
On Wed, Jan 16, 2013 at 08:30:56PM +0530, Kishon Vijay Abraham I wrote:
> New platforms are being added which has multiple PHY's (of same type) and
> which has multiple USB controllers. The binding information has to be
> present in the PHY library (otg.c) in order for it to return the
> appropriat
tree: git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git gadget
head: 7620f5f22e9317ab26c0fdbdd15c5e9ed972ef89
commit: 84b140524c107fb4f4fe618509bc067245c9d878 [19/61] usb: phy: mv_usb2: add
PHY driver for marvell usb2 controller
config: make ARCH=x86_64 allmodconfig
All error/warnin
On Friday 18 January 2013 05:18 PM, Felipe Balbi wrote:
On Wed, Jan 16, 2013 at 08:30:56PM +0530, Kishon Vijay Abraham I wrote:
New platforms are being added which has multiple PHY's (of same type) and
which has multiple USB controllers. The binding information has to be
present in the PHY libra
Hi,
On Fri, Jan 18, 2013 at 03:10:42PM +0530, Kishon Vijay Abraham I wrote:
> Added a new driver for the usb part of control module. This has an API
> to power on the USB2 phy and an API to write to the mailbox depending on
> whether MUSB has to act in host mode or in device mode.
>
> Writing to
tree: git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git gadget
head: 7620f5f22e9317ab26c0fdbdd15c5e9ed972ef89
commit: 3dfa070934a431a14cf5469b4729fe17f0b87980 [29/61] usb: phy: mv_usb2_phy:
add externel chip support
config: make ARCH=x86_64 allmodconfig
Note: the balbi-usb/gadget HE
On Fri, Jan 18, 2013 at 03:10:43PM +0530, Kishon Vijay Abraham I wrote:
> A seperate driver has been added to handle the usb part of control
> module. A device for the above driver is created here, using the register
> address information to be used by the driver for powering on the PHY and
> for w
Hi,
On Fri, Jan 18, 2013 at 03:10:45PM +0530, Kishon Vijay Abraham I wrote:
> Start using the control module driver for powering on the PHY and for
> writing to the mailbox instead of writing to the control module
> registers on their own.
>
> Signed-off-by: Kishon Vijay Abraham I
> ---
> Docum
On Fri, Jan 18, 2013 at 07:48:14PM +0800, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git gadget
> head: 7620f5f22e9317ab26c0fdbdd15c5e9ed972ef89
> commit: 84b140524c107fb4f4fe618509bc067245c9d878 [19/61] usb: phy: mv_usb2:
> add PHY driver for marv
tree: git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git gadget
head: 7620f5f22e9317ab26c0fdbdd15c5e9ed972ef89
commit: 2f06f18d080955b07c05cb2792708250f1f522e4 [43/61] usb: gadget: add some
infracture to register/unregister functions
config: make ARCH=x86_64 allmodconfig
Note: the ba
On Friday 18 January 2013 16:36:29 kishon wrote:
> > Bus 001 Device 004: ID 152d:2509 JMicron Technology Corp. / JMicron
> > USA Technology Corp. JMS539 SuperSpeed SATA II 3.0G Bridge
> > Device Descriptor:
>
> You are connecting to the wrong port.
>
> Try connecting to bus2 which seems to have u
Hi,
On Friday 18 January 2013 05:29 PM, Felipe Balbi wrote:
Hi,
On Fri, Jan 18, 2013 at 03:10:42PM +0530, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB h
On Friday 18 January 2013 05:32 PM, Felipe Balbi wrote:
Hi,
On Fri, Jan 18, 2013 at 03:10:45PM +0530, Kishon Vijay Abraham I wrote:
Start using the control module driver for powering on the PHY and for
writing to the mailbox instead of writing to the control module
registers on their own.
Sign
>
> On Fri, Jan 18, 2013 at 10:50:28AM +0800, Peter Chen wrote:
> > +#ifdef CONFIG_PM
> > +static int ci13xxx_imx_suspend(struct device *dev)
> > +{
> > + struct ci13xxx_imx_data *data =
> > + platform_get_drvdata(to_platform_device(dev));
>
> Is there a reason not to use dev_get_dr
Hi,
On Fri, Jan 18, 2013 at 05:40:04PM +0530, kishon wrote:
> >>+void omap_control_usb_host_mode(struct device *dev)
> >>+{
> >>+ u32 val;
> >>+ struct omap_control_usb *control_usb = dev_get_drvdata(dev);
> >>+
> >>+ val = AVALID | VBUSVALID;
> >>+
> >>+ writel(val, control_usb->otghs_con
Both OMAP4 and 5 exhibit the same revision ID in the REVISION register
but they have different number of ports i.e. 2 and 3 respectively.
So we can't rely on REVISION register for number of ports on OMAP5
and depend on platform data (or device tree) instead.
Signed-off-by: Roger Quadros
Reviewed-
We don't need multiple aliases for the OMAP USB host clocks so remove them.
CC: Paul Walmsley
CC: Rajendra Nayak
CC: Benoit Cousson
CC: Mike Turquette
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
Acked-by: Paul Walmsley
---
arch/arm/mach-omap2/cclock44xx_data.c |7 ---
1
We split initializing revision 1 and revision 2 into different
functions. Initialization is now done dynamically so that only
the number of ports available on the system are initialized.
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
---
drivers/mfd/omap-usb-host.c | 129 ++
clk_set_parent is expected to fail on OMAP3 platforms. We don't
consider that as fatal so don't spam console.
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
---
drivers/mfd/omap-usb-host.c | 18 +-
1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/
Fixes the below build warning when driver is built-in.
drivers/mfd/omap-usb-host.c:750:12: warning:
‘usbhs_omap_remove’ defined but not used [-Wunused-function]
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
---
drivers/mfd/omap-usb-host.c |2 +-
1 files changed, 1 insertions(+), 1
We don't need multiple aliases for the OMAP USB host clocks and neither
the dummy clocks so remove them.
CC: Paul Walmsley
CC: Rajendra Nayak
CC: Benoit Cousson
CC: Mike Turquette
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
Acked-by: Paul Walmsley
---
arch/arm/mach-omap2/cclock
All ports have similarly named port clocks so we can
bunch them into a port data structure and use for loop
to enable/disable the clocks.
Dynamically allocate and get clocks based on number of ports
available on the platform
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
---
drivers/mf
The driver does not have an interrupt handler and
we don't really need a spinlock, so get rid of it.
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
---
drivers/mfd/omap-usb-host.c | 16
1 files changed, 0 insertions(+), 16 deletions(-)
diff --git a/drivers/mfd/omap-u
Enable the optional HSIC clocks (60MHz and 480MHz) for the ports
that are configured in HSIC mode.
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
---
drivers/mfd/omap-usb-host.c | 97 --
1 files changed, 83 insertions(+), 14 deletions(-)
diff -
The revision register should tell us how many ports are present.
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
---
drivers/mfd/omap-usb-host.c | 33 -
1 files changed, 28 insertions(+), 5 deletions(-)
diff --git a/drivers/mfd/omap-usb-host.c b/drivers
No need to check for missing platform data in runtime_suspend/resume
as it makes more sense to do it in the probe function.
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
---
drivers/mfd/omap-usb-tll.c | 15 +--
1 files changed, 5 insertions(+), 10 deletions(-)
diff --git
Get rid of the unnecessary missing platform data checks
in runtime_suspend/resume. We are already checking for missing
platform data in probe.
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
---
drivers/mfd/omap-usb-host.c | 10 --
1 files changed, 0 insertions(+), 10 deletions
Use devm_ variants of kzalloc and ioremap. Also clean up error path.
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
---
drivers/mfd/omap-usb-host.c | 38 +++---
1 files changed, 11 insertions(+), 27 deletions(-)
diff --git a/drivers/mfd/omap-usb-host.c
The TLL module on OMAP5 has 3 channels.
HSIC mode requires the TLL channel to be in Transparent UTMI mode.
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
---
drivers/mfd/omap-usb-tll.c | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/drivers/mfd/oma
This driver does not request any gpios so don't free them.
Fixes L3 bus error on multiple modprobe/rmmod of ehci_hcd
with ehci-omap in use.
Without this patch, EHCI will break on repeated insmod/rmmod
of ehci_hcd for all OMAP2+ platforms that use EHCI and
set 'phy_reset = true' in usbhs_omap_board
Let's have a single platform data structure for the OMAP's High-Speed
USB host subsystem instead of having 3 separate ones i.e. one for
board data, one for USB Host (UHH) module and one for USB-TLL module.
This makes the code much simpler and avoids creating multiple copies of
platform data.
CC:
Get rid of the unnecessary spin_lock_irqsave/restore() as there is
no interrupt handler for this driver. Instead we serialize access
to tll_dev using a global spinlock.
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
---
drivers/mfd/omap-usb-tll.c | 53 ++---
This is a handy macro to check if the port requires the
USB TLL module or not. Use it to Enable the TLL module and manage
the clocks.
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
---
drivers/mfd/omap-usb-tll.c | 20
1 files changed, 12 insertions(+), 8 deletions
omap_enable/disable_tll() can fail if TLL device is not
initialized. It could be due to multiple reasons and not only
due to missing platform data.
Also make local variables static and use 'struct device *'
instead of 'struct platform_device *' for global reference.
Signed-off-by: Roger Quadros
Every channel has a functional clock that is similarly named.
It makes sense to use a for loop to manage these clocks as OMAPs
can come with up to 3 channels.
Dynamically allocate and get channel clocks depending on the
number of clocks avaiable on the platform.
Signed-off-by: Roger Quadros
Revi
Fix channel count detecion for REV2. Also, don't give up
if we don't recognize the IP Revision. We assume the default
number of channels (i.e. 3) for unrecognized IPs.
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
---
drivers/mfd/omap-usb-tll.c | 20 +++-
1 files chan
Use devm_ variants of kzalloc() and ioremap(). Simplify the error path.
Signed-off-by: Roger Quadros
Reviewed-by: Felipe Balbi
---
drivers/mfd/omap-usb-tll.c | 38 --
1 files changed, 12 insertions(+), 26 deletions(-)
diff --git a/drivers/mfd/omap-usb-tll.
Hi,
This patchset addresses the following
- Consolidate USB Host platform data.
- Avoid addressing clocks one by one by name and use a for loop + bunch
of cleanups.
- Get number of channels/ports dynamically either from revision register
or from platform data. Avoids getting clocks that are n
On 01/18/2013 02:17 PM, Roger Quadros wrote:
> This driver does not request any gpios so don't free them.
> Fixes L3 bus error on multiple modprobe/rmmod of ehci_hcd
> with ehci-omap in use.
>
> Without this patch, EHCI will break on repeated insmod/rmmod
> of ehci_hcd for all OMAP2+ platforms tha
This driver does not request any gpios so don't free them.
Fixes L3 bus error on multiple modprobe/rmmod of ehci_hcd
with ehci-omap in use.
Without this patch, EHCI will break on repeated insmod/rmmod
of ehci_hcd for all OMAP2+ platforms that use EHCI and
set 'phy_reset = true' in usbhs_omap_board
2013/1/18 Oliver Neukum :
> The question is, what goes wrong, if indeed the device is SS.
>
> In this particular case a usbmon trace is likely not as useful as usually.
> Could you compile a kernel with DEBUG for USB and XHCI enabled?
no problem, I'll do that tomorrow (not at home until then).
Th
On Fri, Jan 18, 2013 at 4:53 PM, Petko Manolov wrote:
> The code in the driver is based on the specs from ADMTek (later, Infineon).
> Since i never suspend my machines this feature has not been tested by me.
>
> However, if the proposed patch is the right thing to do i'd be happy to see
> it appli
Hi,
On Tue, Dec 18, 2012 at 09:09:40PM +0530, Vivek Gautam wrote:
> This patch-set enables the samsung-usbphy driver on exynos5250,
> which enables the support for USB2 type and USB3 type phys.
> The corresponding phy driver patches are available at:
> 1) https://lkml.org/lkml/2012/12/18/201
> 2
On Fri, Jan 18, 2013 at 03:10:13PM +0200, Felipe Balbi wrote:
> Hi,
>
> On Tue, Dec 18, 2012 at 09:09:40PM +0530, Vivek Gautam wrote:
> > This patch-set enables the samsung-usbphy driver on exynos5250,
> > which enables the support for USB2 type and USB3 type phys.
> > The corresponding phy driver
On Fri, Jan 11, 2013 at 08:32:29PM +0530, Vivek Gautam wrote:
> Adding the phy driver to ehci-s5p. Keeping the platform data
> for continuing the smooth operation for boards which still uses it
>
> Signed-off-by: Vivek Gautam
> Acked-by: Jingoo Han
Missing Alan's Acked-by here.
--
balbi
sig
Hi,
On Mon, Jan 14, 2013 at 05:52:15PM +0530, Vivek Gautam wrote:
> This patch adds host phy support to samsung-usbphy driver and
> further adds support for samsung's exynos5250 usb-phy.
>
> Signed-off-by: Praveen Paneri
> Signed-off-by: Vivek Gautam
Missing Kukjim's Acked-by here
--
balbi
On 01/17/2013 06:10 PM, Alan Stern wrote:
> On Thu, 17 Jan 2013, Roger Quadros wrote:
>
>> Alan,
>>
>> What tree is your patch based off?
>
> Roughly speaking, 3.7 plus Greg KH's usb-next branch as of the 3.7
> release. This should be pretty much the same as 3.8-rc1 as far as the
> USB stack is
Hi Felipe,
On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi wrote:
> Hi,
>
> On Mon, Jan 14, 2013 at 05:52:15PM +0530, Vivek Gautam wrote:
>> This patch adds host phy support to samsung-usbphy driver and
>> further adds support for samsung's exynos5250 usb-phy.
>>
>> Signed-off-by: Praveen Paneri
On Fri, Jan 18, 2013 at 07:51:08PM +0530, Vivek Gautam wrote:
> Hi Felipe,
>
>
> On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi wrote:
> > Hi,
> >
> > On Mon, Jan 14, 2013 at 05:52:15PM +0530, Vivek Gautam wrote:
> >> This patch adds host phy support to samsung-usbphy driver and
> >> further adds
Add device driver for USB2CAN interface from "8 devices"
(http://www.8devices.com).
changes since v9:
* fixed syslog messages
* fixed crc error number
* increased MAX_RX_URBS and MAX_TX_URBS
changes since v8:
* remove all sysfs files
changes since v7:
* add sysfs documentation
* fix minor styli
Adding support for the MBIM mode in some Sierra Wireless devices.
Some Sierra Wireless firmwares support CDC MBIM but have no CDC
Union funtional descriptor. This violates the MBIM specification,
but we can easily work around the bug by looking at the Interface
Association Descriptor instead. Thi
The driver description files gives these names to the vendor specific
functions on this modem:
Diag VID_19D2&PID_0265&MI_00
NMEA VID_19D2&PID_0265&MI_01
AT cmd VID_19D2&PID_0265&MI_02
Modem VID_19D2&PID_0265&MI_03
NetVID_19D2&PID_0265&MI_04
Signed-off-by: Bjørn Mork
---
drivers/ne
HI Balbi,
On Fri, Jan 18, 2013 at 7:52 PM, Felipe Balbi wrote:
> On Fri, Jan 18, 2013 at 07:51:08PM +0530, Vivek Gautam wrote:
>> Hi Felipe,
>>
>>
>> On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi wrote:
>> > Hi,
>> >
>> > On Mon, Jan 14, 2013 at 05:52:15PM +0530, Vivek Gautam wrote:
>> >> This
Hi Alan,
On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi wrote:
> On Fri, Jan 11, 2013 at 08:32:29PM +0530, Vivek Gautam wrote:
>> Adding the phy driver to ehci-s5p. Keeping the platform data
>> for continuing the smooth operation for boards which still uses it
>>
>> Signed-off-by: Vivek Gautam
>
> On 16.01.2013 09:07, "Bernd Krumböck" wrote:
>
>> Hi Oliver!
>>
>>> When detaching the device from the CAN bus when sending/receiving CAN
traffic
>>> i got these dmesg infos:
>>>
>>> [ 960.047130] usb_8dev 2-1.4:1.0 can2: Unknown status/error message (0)
>>> [ 976.544343] usb_8dev 2-1.4:1.0 can
On Fri, Jan 18, 2013 at 02:17:08PM +0200, Roger Quadros wrote:
> + tll->ch_clk = devm_kzalloc(dev, sizeof(struct clk * [tll->nch]),
> + GFP_KERNEL);
> + if (!tll->ch_clk) {
> + ret = -ENOMEM;
> + dev_err(dev, "Couldn't allo
On Fri, Jan 18, 2013 at 02:17:09PM +0200, Roger Quadros wrote:
> +/* only PHY and UNUSED modes don't need TLL */
> +#define omap_usb_mode_needs_tll(x) ((x != OMAP_USBHS_PORT_MODE_UNUSED) &&\
> + (x != OMAP_EHCI_PORT_MODE_PHY))
Growl.
These parens do not make
On 01/18/2013 04:59 PM, Russell King - ARM Linux wrote:
> On Fri, Jan 18, 2013 at 02:17:08PM +0200, Roger Quadros wrote:
>> +tll->ch_clk = devm_kzalloc(dev, sizeof(struct clk * [tll->nch]),
>> +GFP_KERNEL);
>> +if (!tll->ch_clk) {
>> +
On Fri, Jan 18, 2013 at 07:59:52PM +0530, Vivek Gautam wrote:
> HI Balbi,
>
>
> On Fri, Jan 18, 2013 at 7:52 PM, Felipe Balbi wrote:
> > On Fri, Jan 18, 2013 at 07:51:08PM +0530, Vivek Gautam wrote:
> >> Hi Felipe,
> >>
> >>
> >> On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi wrote:
> >> > Hi,
>
On 01/18/2013 05:02 PM, Russell King - ARM Linux wrote:
> On Fri, Jan 18, 2013 at 02:17:09PM +0200, Roger Quadros wrote:
>> +/* only PHY and UNUSED modes don't need TLL */
>> +#define omap_usb_mode_needs_tll(x) ((x != OMAP_USBHS_PORT_MODE_UNUSED) &&\
>> + (x !=
On Fri, 18 Jan 2013, Venu Byravarasu wrote:
> As Tegra PHY driver needs to access one of the Host registers,
> added few APIs.
>
> Signed-off-by: Venu Byravarasu
> ---
> delta from v2:
> Renamed USB_PORTSC1 to TEGRA_USB_PORTSC1.
> Removed tegra_ehci_set_wakeon_events() and its references.
> Used
On Fri, 11 Jan 2013, Vivek Gautam wrote:
> Adding the phy driver to ehci-s5p. Keeping the platform data
> for continuing the smooth operation for boards which still uses it
>
> Signed-off-by: Vivek Gautam
> Acked-by: Jingoo Han
Acked-by: Alan Stern
--
To unsubscribe from this list: send the
On Fri, 11 Jan 2013, Vivek Gautam wrote:
> Adding the phy-driver to ohci-exynos. Keeping the platform data
> for continuing the smooth operation for boards which still uses it
>
> Signed-off-by: Vivek Gautam
> Acked-by: Jingoo Han
Acked-by: Alan Stern
--
To unsubscribe from this list: send t
On Fri, 18 Jan 2013, Vivek Gautam wrote:
> Hi Alan,
>
>
> On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi wrote:
> > On Fri, Jan 11, 2013 at 08:32:29PM +0530, Vivek Gautam wrote:
> >> Adding the phy driver to ehci-s5p. Keeping the platform data
> >> for continuing the smooth operation for boards
Usb3.0 device defines function remote wakeup which is only for interface
recipient rather than device recipient. This is different with usb2.0 device's
remote wakeup feature which is defined for device recipient. According usb3.0
spec 9.4.5, the function remote wakeup can be modified by the SetFeat
On Fri, 18 Jan 2013, Lan Tianyu wrote:
> > By the way, have you checked whether the auto-power-off mechanism works
> > correctly when you do a system suspend?
> >
> Thanks for reminder. I test this today and find an issue. If usb device
> was powered off during runtime, pm_runtime_get_sync() in
On Thu, 17 Jan 2013, Bjørn Mork wrote:
> Peter Stuge writes:
> > Alan Stern wrote:
> >> > Is this useful to anyone?
> >>
> >> In theory it would be useful to somebody developing firmware for a USB
> >> device. If only such people would test their firmwares under Linux...
> >
> > Some do. Maybe
Alan Stern wrote:
> > >> > Should we just drop those warnings?
> > >>
> > >> No opinion.
> > >
> > > I think they should stay.
> >
> > OK, but how about demoting them to debug messages instead of warnings?
>
> If you want to make that change, I don't mind.
I prefer that they stay visible by def
xhci driver divides the root hub into two logical hubs which work
respectively for usb 2.0 and usb 3.0 devices. They are independent
devices in the usb core. But in the ACPI table, it's one device node
and all usb2.0 and usb3.0 ports are under it. Binding usb port with
its acpi node needs the raw p
This patch is to bind xhci root hub usb port with its acpi node.
The port num in the acpi table matches with the sequence in the xhci
extended capabilities table. So call usb_hcd_find_raw_port_number() to
transfer hub port num into raw port number which associates with
the sequence in the xhci exte
This patch is to optimize xhci_find_realport_number(). Call
xhci_find_raw_port_number() to get real index in the HW port
status registers instead of scanning through the xHCI roothub
port array.
Signed-off-by: Lan Tianyu
---
drivers/usb/host/xhci-mem.c | 36
On 01/16/2013 06:30 AM, Venu Byravarasu wrote:
> Tegra20 USB has 3 PHY instances:
> Instance 1 and 3 are UTMI. Instance 2 is ULPI.
>
> As instance number was used to differentiate ULPI from UTMI,
> used DT param to get this info and processed accordingly.
> diff --git a/include/linux/usb/tegra_us
Hi Greg,
Here are my latest fixes for this -rc cycle. Unless something
extremely important shows up, we should be ready for a final
v3.8 ;-)
Hopefully no surprises will come.
ps: You will notice a few changes on arch/arm/mach-imx/ but they're needed to
make fsl build and work again. We _do_ have
On 01/18/2013 10:04 AM, Stephen Warren wrote:
> On 01/16/2013 06:30 AM, Venu Byravarasu wrote:
>> Tegra20 USB has 3 PHY instances:
>> Instance 1 and 3 are UTMI. Instance 2 is ULPI.
>>
>> As instance number was used to differentiate ULPI from UTMI,
>> used DT param to get this info and processed acc
On 01/18/2013 08:30 AM, Alan Stern wrote:
> On Fri, 18 Jan 2013, Venu Byravarasu wrote:
>
>> As Tegra PHY driver needs to access one of the Host registers,
>> added few APIs.
>>
>> Signed-off-by: Venu Byravarasu
>> ---
>> delta from v2:
>> Renamed USB_PORTSC1 to TEGRA_USB_PORTSC1.
>> Removed tegr
1 - 100 of 176 matches
Mail list logo
