Hi Peter,
[auto build test ERROR on v4.5-rc7]
[also build test ERROR on next-20160324]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Peter-Chen/usb-chipidea-add-DMA-mask-configuration-API
On Tue, Mar 08, 2016 at 07:40:08PM -0800, Bjorn Andersson wrote:
> On Tue, Mar 8, 2016 at 11:52 AM, Li Yang wrote:
> > On Wed, Mar 2, 2016 at 4:59 PM, Li Yang wrote:
> >> On Mon, Feb 22, 2016 at 4:07 PM, Bjorn Andersson
> >>
musb device is allocated with PLATFORM_DEVID_AUTO, fix
incorrect lookup name in non-dt case.
This fixes issue with musb initialization on Nokia N900
in boardfile boot mode.
Signed-off-by: Ruslan Bilovol
---
drivers/phy/phy-twl4030-usb.c | 2 +-
1 file changed, 1
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
---
I made a last minute change and some
We will be adding more da8xx-specific code for phy and clocks, so it will
be better to have this in a separate file. This way we don't have a bunch
of #ifdefs for all of the da8xx stuff.
Signed-off-by: David Lechner
---
v3 changes: this is a new patch. The diff in git
The CFGCHIPn registers are used by a number of devices, so using a syscon
device to share them. The first consumer of this will by the phy-da8xx-usb
driver.
Signed-off-by: David Lechner
---
v3 changes: This is a new patch. There is one syscon device for all CFGCHIP
The da850 family of processors has an async3 clock domain that can be
muxed to either pll0_sysclk2 or pll1_sysclk2. Now that the davinci clocks
have a set_parent callback, we can use this to control the async3 mux
instead of a stand-alone function.
This adds a new async3_clk and sets the
Some clocks (such as the USB PHY clocks in DA8xx) will need to use iomem.
The davinci_common_init() function must be called before the ioremap, so
the clock init is now split out as separate function.
Signed-off-by: David Lechner
---
v3 changes: This is a new patch. It
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
---
v3 changes:
* Uses syscon device for
TI has been using the physical address in DT after the @ in device nodes.
The device tree convention is to use the same address that is used for
the reg property. This updates all davinci DT files to use the proper
convention.
Signed-off-by: David Lechner
---
v3 changes:
This is a reworking of the v2 series based of feedback and review. There were
very many suggestions, so hopefully I didn't miss any. Here are the
highlights...
New stuff:
* Fixed the davinci device tree declarations to use the preferred DT address
convention so that the items I have added can
We will be using a generic syscon device for the TI DA8XX SoC CFGCHIPx
retisters. This will be used by a number of planned drivers including a
new USB PHY driver and common clock framework drivers.
The same defines are removed from the platform_data header file since they
are now redundant and
Up to this point, the USB phy clock configuration was handled manually in
the board files and in the usb drivers. This adds proper clocks so that
the usb drivers can use clk_get and clk_enable and not have to worry about
the details. Also, the related code is removed from the board files and
Device tree binding for new phy-da8xx-usb driver.
Signed-off-by: David Lechner
---
v3 changes:
* added cfgchip info and example
* correct usage of "DA8xx"
* correct address after @
* dropped 11 before @ in usb@
.../devicetree/bindings/phy/phy-da8xx-usb.txt | 40
There is now a proper phy driver for the DA8xx SoC USB PHY. This adds the
platform device declarations needed to use it.
Signed-off-by: David Lechner
---
v3 changes:
* The declaration is now in the new usb-da8xx.c file.
arch/arm/mach-davinci/board-da830-evm.c | 28
Add a node for the new usb phy driver.
Signed-off-by: David Lechner
---
v3 changes:
* No longer needs reg property since we are now using syscon instead.
arch/arm/boot/dts/da850.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/da850.dtsi
Including mach/* is frowned upon in device drivers, so get rid of it.
This replaces usb20_clk and code that pokes CFGCHIP2 with a proper phy
driver.
Signed-off-by: David Lechner
Acked-by: Alan Stern
---
v3 changes:
* add phy_init and phy_exit
Simplify things a bit by using devm functions where possible.
Signed-off-by: David Lechner
---
v3 changes:
* Kept clk variable to minimize noise.
drivers/usb/musb/da8xx.c | 19 +--
1 file changed, 5 insertions(+), 14 deletions(-)
diff --git
Use the new phy-da8xx-usb driver to take the place of the mach code that
pokes CFGCHIP2 in the da8xx musb glue driver. This unbreaks the driver.
Signed-off-by: David Lechner
---
v3 changes:
* removed depends on BROKEN and added select PHY_DA8XX_USB to Kconfig
* Added
Add a syscon node for the SoC CFGCHIPn registers. This is needed for
the new usb phy driver.
Signed-off-by: David Lechner
---
v3 changes: This is a new patch.
arch/arm/boot/dts/da850.dtsi | 4
1 file changed, 4 insertions(+)
diff --git
Introduce a set_parent callback that will be used for mux clocks, such as
the USB PHY muxes and the async3 clock domain mux.
Signed-off-by: David Lechner
---
v3 changes: none.
arch/arm/mach-davinci/clock.c | 17 -
arch/arm/mach-davinci/clock.h | 1 +
2
udc->softconnect should be set regardless of the VBUS state, otherwise
the USB peripheral device, connected during suspend, won't be detected
since can_pullup() would return false the UDC controller won't be enabled.
Fixes: 252455c40316 (usb: gadget: fsl driver pullup fix)
Signed-off-by: Dmitry
On 3/16/2016 3:10 PM, Przemek Rudy wrote:
> The host/device mode set with dr_mode should be kept all the time,
> not being changed to OTG in gadget setup (by overriding CFGUSB_FORCEDEVMODE
> and CFGUSB_FORCEHOSTMODE bits).
>
> Signed-off-by: Przemek Rudy
> ---
>
Hi,
On 24.03.2016 09:11, Felipe Balbi wrote:
Hi,
Ivaylo Dimitrov writes:
Ivaylo Dimitrov writes:
On 16.01.2016 12:40, Ivaylo Dimitrov wrote:
Hi,
On 16.01.2016 00:48, Tony Lindgren wrote:
Hi all,
Looks like there's some issue
On 01/02/16 12:43, Martyn Welch wrote:
On 31/01/16 19:54, Johan Hovold wrote:
On Mon, Jan 18, 2016 at 02:14:37PM +, Martyn Welch wrote:
+
+/* 2 banks of GPIO - One for the pins taken from each serial
port */
+if (port_priv->bInterfaceNumber == 0 && (buf[0] & 0xFF) != 0) {
On 3/24/2016 4:32 AM, John Keeping wrote:
> Hi,
>
> I've been trying to use the uac2 gadget function on a Radxa Rock2 board
> which uses the dwc2 driver, but it seems there is a problem with
> isochronous in endpoints (out works fine).
>
> When trying to use the audio gadget no data is
On Wed, 23 Mar 2016, Alan Stern wrote:
> The usbhid driver has inconsistently duplicated code in its post-reset,
> resume, and reset-resume pathways.
>
> reset-resume doesn't check HID_STARTED before trying to
> restart the I/O queues.
>
> resume fails to clear the
On 03/24/2016 05:26 PM, Rafał Miłecki wrote:
Thanks to switching to devm_gpiod_get:
1) We don't have to pass fwnode pointer
2) We can request initial GPIO value at getting call
This was successfully tested on Netgear R6250 (BCM4708).
Signed-off-by: Rafał Miłecki
---
On 24 March 2016 at 14:58, Sergei Shtylyov
wrote:
> On 03/24/2016 08:37 AM, Rafał Miłecki wrote:
>
>> Thanks to switching to devm_gpiod_get:
>> 1) We don't have to pass fwnode pointer
>> 2) We can request initial GPIO value at getting call
>>
From: David Lechner
> Sent: 23 March 2016 18:07
> On 03/23/2016 12:21 PM, Sekhar Nori wrote:
> >> +/* DA8xx CFGCHIP2 (USB PHY Control) register bits */
> >> +#define PHYCLKGD (1 << 17)
> >> +#define VBUSSENSE (1 << 16)
> >> +#define RESET (1 << 15)
> >>
Hello.
On 03/24/2016 08:37 AM, Rafał Miłecki wrote:
Thanks to switching to devm_gpiod_get:
1) We don't have to pass fwnode pointer
2) We can request initial GPIO value at getting call
This was successfully tested on Netgear R6250 (BCM4708).
Signed-off-by: Rafał Miłecki
---
On Thu, 24 Mar 2016, Robert Dobrowolski wrote:
> From: Robert Dobrowolski
>
> On BXT platform Host Controller and Device Controller figure as
> same PCI device but with different device function. HCD should
> not pass data to Device Controller but only to
On Thu, Mar 24, 2016 at 01:34:32PM +, Ian T. Jacobsen wrote:
> [ 21.434822] BUG: unable to handle kernel NULL pointer dereference at
> 0014 [ 21.435516] IP: []
> usb_audio_probe+0x2ca/0x9a0 [snd_usb_audio]
>
> I have a PreSonus AudioBox iTwo causing this issue.
> I updated
On Thursday 24 March 2016 12:02 AM, David Lechner wrote:
> On 03/23/2016 12:29 PM, Sekhar Nori wrote:
>>
>> Alright, I guess 'can be called' in the comment should have used
>> stronger language :) How about late registration of USB clocks as I
>> suggested. It should also help consolidate code
[ 21.434822] BUG: unable to handle kernel NULL pointer dereference at
0014 [ 21.435516] IP: []
usb_audio_probe+0x2ca/0x9a0 [snd_usb_audio]
I have a PreSonus AudioBox iTwo causing this issue.
I updated from torvalds git yesterday
dmesg.output
Description: Binary data
On 22.03.2016 18:23, Oliver Neukum wrote:
I have a report of a T430 laptop needing this unless you want
shut downs turn into reboot. Is there any hope of investigating this
further at Intel, or do we go for the cautious approach?
Oliver Neukum (1):
xhci: one more quirk for PANTHERPOINT
This patch introduces the usb charger driver based on usb gadget that
makes an enhancement to a power driver. It works well in practice but
that requires a system with suitable hardware.
The basic conception of the usb charger is that, when one usb charger
is added or removed by reporting from
When the usb gadget supporting for usb charger is ready, the usb charger
should get the type by the 'get_charger_type' callback which is implemented
by the usb gadget operations, and get the usb charger pointer from struct
'usb_gadget'.
Signed-off-by: Baolin Wang
---
For supporting the usb charger, it adds the usb_charger_init() and
usb_charger_exit() functions for usb charger initialization and exit.
It will report to the usb charger when the gadget state is changed,
then the usb charger can do the power things.
Introduce a callback 'get_charger_type' which
Currently the Linux kernel does not provide any standard integration of this
feature that integrates the USB subsystem with the system power regulation
provided by PMICs meaning that either vendors must add this in their kernels
or USB gadget devices based on Linux (such as mobile phones) may not
Integrate with the newly added USB charger interface to limit the current
we draw from the USB input based on the input device configuration
identified by the USB stack, allowing us to charge more quickly from high
current inputs without drawing more current than specified from others.
Hi,
I've been trying to use the uac2 gadget function on a Radxa Rock2 board
which uses the dwc2 driver, but it seems there is a problem with
isochronous in endpoints (out works fine).
When trying to use the audio gadget no data is transferred and the other
end of the link ends up timing out.
From: Robert Dobrowolski
On BXT platform Host Controller and Device Controller figure as
same PCI device but with different device function. HCD should
not pass data to Device Controller but only to Host Controllers.
Checking if companion device is Host
From: Rafal Redzimski
Broxton B0 also requires XHCI_PME_STUCK_QUIRK.
Adding PCI device ID for Broxton B and adding to quirk.
Cc:
Signed-off-by: Rafal Redzimski
Signed-off-by: Robert Dobrowolski
Robert Dobrowolski writes:
> [ text/plain ]
> From: Rafal Redzimski
>
> Broxton B0 also requires XHCI_PME_STUCK_QUIRK.
> Adding PCI device ID for Broxton B and adding to quirk.
>
> Signed-off-by: Rafal Redzimski
Sorry, I missed the branch.
Here it is.
This patch adds DCD line support to CP210x USB serial driver.
First it enables CP210x events embedding to incoming URB's by calling:
cp210x_set_config_single(port, CP210X_EMBED_EVENTS, CP210X_ESCCHAR);
Then it parses incoming URB's via custom routine:
From: Rafal Redzimski
Broxton B0 also requires XHCI_PME_STUCK_QUIRK.
Adding PCI device ID for Broxton B and adding to quirk.
Signed-off-by: Rafal Redzimski
Signed-off-by: Robert Dobrowolski
---
Hi,
Ivaylo Dimitrov writes:
>> Ivaylo Dimitrov writes:
>>> On 16.01.2016 12:40, Ivaylo Dimitrov wrote:
Hi,
On 16.01.2016 00:48, Tony Lindgren wrote:
> Hi all,
>
> Looks like there's some issue with the USB
Hi,
On 24.03.2016 08:50, Felipe Balbi wrote:
Hi,
Ivaylo Dimitrov writes:
On 16.01.2016 12:40, Ivaylo Dimitrov wrote:
Hi,
On 16.01.2016 00:48, Tony Lindgren wrote:
Hi all,
Looks like there's some issue with the USB gadgets and configfs.
I'm seeing rmmod of
Hi,
John Youn writes:
> [ text/plain ]
> On 3/21/2016 11:40 PM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> John Youn writes:
>>> [ text/plain ]
>>> On 3/18/2016 12:17 PM, John Youn wrote:
On 3/16/2016 6:56 AM, Felipe Balbi wrote:
>
> heh,
Hi,
Ivaylo Dimitrov writes:
> On 16.01.2016 12:40, Ivaylo Dimitrov wrote:
>> Hi,
>>
>> On 16.01.2016 00:48, Tony Lindgren wrote:
>>> Hi all,
>>>
>>> Looks like there's some issue with the USB gadgets and configfs.
>>>
>>> I'm seeing rmmod of the UDC driver cause a
On 3/22/2016 12:44 PM, Doug Anderson wrote:
> John,
>
> On Tue, Mar 22, 2016 at 12:26 PM, John Youn wrote:
>> Thanks for the debug logs and everyones help.
>>
>> After reviewing with our hardware engineers, it seems this is likely
>> to do with the IDDIG debounce
52 matches
Mail list logo