Hi all,
I have been struggling for the past few days to get a Tascam US-122L (USB
sound-card/midi interface) working, despite reading numerous forum
postings I have only been able to get the midi portion working.
I note that the USB descriptor seems to be corrupt. It declares 2
interfaces, but the
Since we have added otg version and HNP polling support, update
related documentation.
Signed-off-by: Peter Chen
---
Documentation/usb/chipidea.txt | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/Documentation/usb/chipidea.txt b/Documentation/usb/chipidea.txt
in
On Wed, 2016-04-13 at 08:42 +0300, Felipe Balbi wrote:
> USB3 devices, because they are much newer, have much
> less chance of having issues with larger transfers.
>
> We still keep a limit because anything above 2048
> sectors really rendered negligible speed
> improvements, so we will simply ign
Hi,
Oliver Neukum writes:
> On Wed, 2016-04-13 at 08:42 +0300, Felipe Balbi wrote:
>> USB3 devices, because they are much newer, have much
>> less chance of having issues with larger transfers.
>>
>> We still keep a limit because anything above 2048
>> sectors really rendered negligible speed
>
Hi Sergey, Xiong,
Can you try below patch?
On Montag, 11. April 2016 18:01:47 CEST Sergey Senozhatsky wrote:
> Hello,
>
> commit 7b106f2de6938c31ce5e9c86bc70ad3904666b96
> Author: Johannes Thumshirn
> Date: Tue Apr 5 11:50:44 2016 +0200
>
> scsi: Add intermediate STARGET_REMOVE state to
Simon Wood wrote:
> I have been struggling for the past few days to get a Tascam US-122L (USB
> sound-card/midi interface) working, despite reading numerous forum
> postings I have only been able to get the midi portion working.
Does it show up with "aplay -l"?
> I note that the USB descriptor se
On 11/04/16 09:41, Chunfeng Yun wrote:
A new compatible string, "mediatek,mt2701-u3phy", is added.
Signed-off-by: Chunfeng Yun
---
.../devicetree/bindings/phy/phy-mt65xx-usb.txt |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Reviewed-by: Matthias Brugger
diff --git a
Hi,
On Friday 25 March 2016 05:21 AM, David Lechner wrote:
> This is a new phy driver for the SoC USB controllers on the TI DA8xx
> family of microcontrollers. The USB 1.1 PHY is just a simple on/off.
> The USB 2.0 PHY also allows overriding the VBUS and ID pins.
>
> Signed-off-by: David Lechner
Hi,
On Monday 11 April 2016 01:11 PM, Chunfeng Yun wrote:
> A new compatible string, "mediatek,mt2701-u3phy", is added.
how about changing the commit log to something like below?
Add a new compatible string for "mt2701"
Thanks
Kishon
>
> Signed-off-by: Chunfeng Yun
> ---
> .../devicetree/bind
Hi,
On Monday 11 April 2016 01:11 PM, Chunfeng Yun wrote:
> A new compatible string, "mediatek,mt2701-u3phy", is added.
>
> Some register settings to avoid RX sensitivity level degradation
> which may arise on mt8173 platform are separated from other
> platforms.
>
> Signed-off-by: Chunfeng Yun
Hi,
On (04/13/16 10:41), Johannes Thumshirn wrote:
> Hi Sergey, Xiong,
>
> Can you try below patch?
it panics my system.
first it warn_on-s in lib/kobject.c:244
then NULL dereferences
do_scan_async
__scsi_remove_device
scsi_target_reap
device_del
dpm_sysfs_remove
sysfs_unmerge_g
Hi,
On Monday 11 April 2016 03:13 PM, Rafał Miłecki wrote:
> Northstar is a family of SoCs used in home routers. They have USB 2.0
> and 3.0 controllers with PHYs that need to be properly initialized.
> This driver provides PHY init support in a generic way and can be bound
> with an EHCI controll
On Mittwoch, 13. April 2016 23:47:04 CEST Sergey Senozhatsky wrote:
> Hi,
>
> On (04/13/16 10:41), Johannes Thumshirn wrote:
> > Hi Sergey, Xiong,
> >
> > Can you try below patch?
>
> it panics my system.
> first it warn_on-s in lib/kobject.c:244
>
> then NULL dereferences
> do_scan_async
> _
On Wed, Apr 13, 2016 at 08:44:25AM +0200, Rafał Miłecki wrote:
> Hi,
>
> I'm trying to debug some EHCI issue so I enabled debugging by adding
> ccflags-y := -DDEBUG
> to the drivers/usb/host/Makefile
>
> Some of debugging lines contain random memory, e.g.:
> ehci-platform ehci-platform.0: .|��`|�
On Wed, April 13, 2016 3:01 am, Clemens Ladisch wrote:
> Simon Wood wrote:
>
>> I have been struggling for the past few days to get a Tascam US-122L
>> (USB
>> sound-card/midi interface) working, despite reading numerous forum
>> postings I have only been able to get the midi portion working.
>
> D
On Tue, 12 Apr 2016, John Youn wrote:
> > Wait, even SuperSpeed GEN1-only devices *must* set bcdUSB to 0x0310 ? Do
> > you have a reference to that ? I find that pretty odd because this means
> > that if I take any of my USB3 devices that I already have today, and run
> > them against latest USBCV
On Wed, 13 Apr 2016, Felipe Balbi wrote:
> USB3 devices, because they are much newer, have much
> less chance of having issues with larger transfers.
>
> We still keep a limit because anything above 2048
> sectors really rendered negligible speed
> improvements, so we will simply ignore
> that. T
On Wed, 13 Apr 2016, Rafał Miłecki wrote:
> Hi,
>
> I'm trying to debug some EHCI issue so I enabled debugging by adding
> ccflags-y := -DDEBUG
> to the drivers/usb/host/Makefile
>
> Some of debugging lines contain random memory, e.g.:
> ehci-platform ehci-platform.0: .|��`|���5P5@�3�.��*�.|��o
On Wed, 2016-04-13 at 10:41 +0200, Johannes Thumshirn wrote:
> Hi Sergey, Xiong,
>
> Can you try below patch?
>
> On Montag, 11. April 2016 18:01:47 CEST Sergey Senozhatsky wrote:
> > Hello,
> >
> > commit 7b106f2de6938c31ce5e9c86bc70ad3904666b96
> > Author: Johannes Thumshirn
> > Date: Tue
Hi Dinh,
> From: Dinh Nguyen
>
> Allow for platforms that have a reset controller driver in place to bring the
> USB IP out of reset.
>
> Signed-off-by: Dinh Nguyen
> diff --git a/drivers/usb/dwc2/platform.c b/drivers/usb/dwc2/platform.c
> index 88629be..6987ef3 100644
> --- a/drivers/usb/dwc2
One more question: this issue does not occur if I intentionally do not
claim the interface via libusb_claim_interface() before requesting
streaming image data from the camera. Does this make any sense? It's to
my understanding I should always claim the interface before issuing r/w
calls to the came
Hi Greg
One tiny fix to 4.6 to make sure xhci platform devices without a platform
type don't get identified as XHCI_PLAT_TYPE_MARVELL_ARMADA (0)
Peter Griffin (1):
usb: host: xhci-plat: Make enum xhci_plat_type start at a non zero
value
drivers/usb/host/xhci-plat.h | 2 +-
1 file changed,
From: Peter Griffin
Otherwise generic-xhci and xhci-platform which have no data get wrongly
detected as XHCI_PLAT_TYPE_MARVELL_ARMADA by xhci_plat_type_is().
This fixes a regression in v4.5 for STiH407 family SoC's which use the
synopsis dwc3 IP, whereby the disable_clk error path gets taken due
On 11.04.2016 18:44, Peter Griffin wrote:
Hi Mathias,
On Fri, 25 Mar 2016, Peter Griffin wrote:
Otherwise generic-xhci and xhci-platform which have no data get wrongly
detected as XHCI_PLAT_TYPE_MARVELL_ARMADA by xhci_plat_type_is().
This fixes a regression in v4.5 for STiH407 family SoC's wh
Hi Felipe, Mathias;
I pulled a clean copy of v4.5 and applied the patch suggested by Felipe,
and the issue is no longer present. I would like to disable this
behavior via changes to my software instead of requiring customers to
build a custom kernel. What would be the ideal solution to this issue?
On Wed, 13 Apr 2016, Matthew Giassa wrote:
> Hi Felipe, Mathias;
>
> I pulled a clean copy of v4.5 and applied the patch suggested by Felipe,
> and the issue is no longer present. I would like to disable this
> behavior via changes to my software instead of requiring customers to
> build a custom
I will look into doing that. I think it would be preferable to add some
functionality to mark all devices matching a certain VendorID rather
than dumping the entire device table into `quirks.c', as I'd have to
routinely update it every time we release a new product.
In the meantime, if there's a w
On 04/13/2016 11:23 AM, Stefan Wahren wrote:
>> +hsotg->reset = devm_reset_control_get(hsotg->dev, "dwc2");
>
> shouldn't this be documented in
> Documentation/devicetree/bindings/usb/dwc2.txt ?
>
Sure, I can document it.
>> +if (IS_ERR(hsotg->reset)) {
>> +dev_info(hsotg-
On Wed, 13 Apr 2016, Matthew Giassa wrote:
> I will look into doing that. I think it would be preferable to add some
> functionality to mark all devices matching a certain VendorID rather
> than dumping the entire device table into `quirks.c', as I'd have to
> routinely update it every time we rel
On 4/13/2016 11:52 AM, Dinh Nguyen wrote:
> On 04/13/2016 11:23 AM, Stefan Wahren wrote:
>
>>> + hsotg->reset = devm_reset_control_get(hsotg->dev, "dwc2");
>>
>> shouldn't this be documented in
>> Documentation/devicetree/bindings/usb/dwc2.txt ?
>>
>
> Sure, I can document it.
>
>>> + if (I
On 4/13/2016 7:58 AM, Alan Stern wrote:
> On Tue, 12 Apr 2016, John Youn wrote:
>
>>> Wait, even SuperSpeed GEN1-only devices *must* set bcdUSB to 0x0310 ? Do
>>> you have a reference to that ? I find that pretty odd because this means
>>> that if I take any of my USB3 devices that I already have
On Wed, 13 Apr 2016, John Youn wrote:
> > Besides, this doesn't say what the version number of a non-Enhanced
> > SuperSpeed device should be. I don't see why the USBCV would conclude
> > that a non-Enhanced device needs to set the version to 0x0310.
>
> Non-Enhanced SuperSpeed (i.e. HS and lo
On 04/13/2016 08:20 AM, Kishon Vijay Abraham I wrote:
Don't prefer export symbols from PHY driver. That'll create unnecessary
dependencies between the controller and the PHY.
To see how to fix it, please see my comment for the previous version of your
patch.
Thanks
Kishon
What is the prop
On 04/01/2016 08:16 AM, Kishon Vijay Abraham I wrote:
+EXPORT_SYMBOL_GPL(da8xx_usb20_phy_set_mode);
Don't prefer export symbols from PHY driver. That'll create unnecessary
dependencies between the controller and the PHY.
I think it'll be better to create a new attribute and use it?
Just ha
commit 4e8998d462ab06900949a3099706a19177484c09
Author: Matthew
Date: Wed Apr 13 13:37:21 2016 -0700
Adding new kernel parameter that allows users to skip the check
for whether or not LPM is supported. This resolves erratic power
state changes with certain U3V machine vision cameras
On Wed, Apr 13, 2016 at 02:25:08PM -0700, Matthew Giassa wrote:
> commit 4e8998d462ab06900949a3099706a19177484c09
> Author: Matthew
> Date: Wed Apr 13 13:37:21 2016 -0700
Why is this here?
>
> Adding new kernel parameter that allows users to skip the check
> for whether or not LPM is
Thank you for the feedback Greg. This is my first attempt to submit a
kernel patch.
Is there a better approach to this? The only other option at my disposal
is to add about 200 products to the quirks.c file, and routinely update
that list as new products are released. I need to implement some mean
On Wed, Apr 13, 2016 at 02:37:35PM -0700, Matthew Giassa wrote:
> Thank you for the feedback Greg. This is my first attempt to submit a
> kernel patch.
>
> Is there a better approach to this? The only other option at my disposal
> is to add about 200 products to the quirks.c file, and routinely up
The devices support LPM and are USB3.0 certified, and they work fine in
Windows using the same Intel 8/9/10 Series USB host controllers, along
with Renesas and Fresco controllers. On Linux the devices either seize
up or slow down dramatically ever since LPM support was enabled.
I could always just
On Wed, Apr 13, 2016 at 03:21:09PM -0700, Matthew Giassa wrote:
> The devices support LPM and are USB3.0 certified, and they work fine in
> Windows using the same Intel 8/9/10 Series USB host controllers, along
> with Renesas and Fresco controllers. On Linux the devices either seize
> up or slow do
Mathias provided me with some usb device calls I could use to resolve
this in software (pm_runtime_get_xxx(), pm_runtime_put()), but I'm not
familiar with the API, so I'd need some help figure out how to get the
`struct device*' handle for my current device and issuing those calls
within my applica
From: Dinh Nguyen
Allow for platforms that have a reset controller driver in place to bring
the USB IP out of reset.
Signed-off-by: Dinh Nguyen
---
v4: use dev_dbg() if not a -EPROBE_DEFER
v3: fix compile error
v2: move to lowlevel_hw_init()
---
drivers/usb/dwc2/core.h | 1 +
drivers/usb/
From: Dinh Nguyen
Document the optional 'resets' and 'reset-names' property for the DWC2 usb
core.
Signed-off-by: Dinh Nguyen
---
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
---
Documentation/devicetree/bindings/usb/dwc2.txt | 3 +++
1 file changed, 3 i
Hi,
On Wed, 2016-04-13 at 12:00 +0200, Matthias Brugger wrote:
>
> On 11/04/16 09:41, Chunfeng Yun wrote:
> > A new compatible string, "mediatek,mt2701-u3phy", is added.
> >
> > Signed-off-by: Chunfeng Yun
> > ---
> > .../devicetree/bindings/phy/phy-mt65xx-usb.txt |4 +++-
> > 1 file
Hi,
On Wed, 2016-04-13 at 18:56 +0530, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Monday 11 April 2016 01:11 PM, Chunfeng Yun wrote:
> > A new compatible string, "mediatek,mt2701-u3phy", is added.
>
> how about changing the commit log to something like below?
> Add a new compatible string for "m
Hi,
On Wed, 2016-04-13 at 19:01 +0530, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Monday 11 April 2016 01:11 PM, Chunfeng Yun wrote:
> > A new compatible string, "mediatek,mt2701-u3phy", is added.
> >
> > Some register settings to avoid RX sensitivity level degradation
> > which may arise on mt8
On Thursday 14 April 2016, dingu...@opensource.altera.com wrote:
> @@ -337,6 +338,17 @@ static int dwc2_lowlevel_hw_init(struct dwc2_hsotg
> *hsotg)
> {
> int i, ret;
>
> + hsotg->reset = devm_reset_control_get(hsotg->dev, "dwc2");
> + if (IS_ERR(hsotg->reset)) {
> +
Hello,
On (04/13/16 08:14), James Bottomley wrote:
[..]
> How about good grief no! A device with multiple targets will get it's
> lists screwed with this
>
> The STARGET_REMOVE state you added only applies to the case we're
> trying to kill a target. In the natural operation case, which is what
Hello, Sergei,
> > From: "Du, Changbin"
> >
> > For DWC3 USB controller, the Global Debug Queue/FIFO Space Available
> > Register(GDBGFIFOSPACE) can be used to dump FIFO/Queue available
> space.
>
> Space needed before (.
Okay.
>
> > This can be used to check some special issues, like whet
你的老朋友邀你来Q群:343257759 抢红包 抢秒杀 抢vip 什么都要抢。太刺激了。不靠手气只拼手速
Hi,
Alan Stern writes:
> On Wed, 13 Apr 2016, Felipe Balbi wrote:
>
>> USB3 devices, because they are much newer, have much
>> less chance of having issues with larger transfers.
>>
>> We still keep a limit because anything above 2048
>> sectors really rendered negligible speed
>> improvements,
51 matches
Mail list logo
