On Sat, Feb 11, 2017 at 12:45:58AM +0300, c400 wrote:
> sorry, got the letter branch cleaned, so haven`t seen your reply
>
> tested on 4.9.9 kernel
Has this worked on older kernels? If so, can you use 'git bisect' to
track down the offending patch?
thanks,
greg k-h
--
To unsubscribe from this
On Fri, Feb 10, 2017 at 11:46 PM, Linus Walleij
wrote:
> On Wed, Feb 8, 2017 at 9:00 PM, Hans Ulli Kroll
> wrote:
>
>> add Faraday Technology Corporation as vendor faraday for DT
>>
>> Signed-off-by: Hans Ulli Kroll
>
> Reviewed-by: Linus Walleij
>
> I think I should use this for the PCI block
Add binding doc for generic power sequence library.
Signed-off-by: Peter Chen
Acked-by: Philipp Zabel
Acked-by: Rob Herring
---
.../bindings/power/pwrseq/pwrseq-generic.txt | 48 ++
1 file changed, 48 insertions(+)
create mode 100644
Documentation/devicetree/binding
From: Arnd Bergmann
For xhci-hcd platform device, all the DMA parameters are not
configured properly, notably dma ops for dwc3 devices.
The idea here is that you pass in the parent of_node along with
the child device pointer, so it would behave exactly like the
parent already does. The differenc
From: Arnd Bergmann
For the dual role ehci fsl driver, sysdev will handle the dma
config.
Signed-off-by: Arnd Bergmann
Signed-off-by: Sriram Dash
Signed-off-by: Mathias Nyman
---
drivers/usb/host/ehci-fsl.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/h
Set the dma for ehci from sysdev. The sysdev is pointing to device that
is known to the system firmware or hardware.
Cc: Arnd Bergmann
Cc: Sriram Dash
Signed-off-by: Peter Chen
Acked-by: Alan Stern
---
drivers/usb/host/ehci-mem.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions
From: Arnd Bergmann
Set the dma for chipidea from sysdev. This is inherited from its
parent node. Also, do not set dma mask for child as it is not required
now.
Signed-off-by: Arnd Bergmann
Signed-off-by: Sriram Dash
Acked-by: Peter Chen
Signed-off-by: Mathias Nyman
---
drivers/usb/chipidea
From: Arnd Bergmann
For xhci-hcd platform device, all the DMA parameters are not
configured properly, notably dma ops for dwc3 devices. So, set
the dma for xhci from sysdev. sysdev is pointing to device that
is known to the system firmware or hardware.
Cc: Baolin Wang
Cc: Vivek Gautam
Cc: Alex
We have an well-known problem that the device needs to do some power
sequence before it can be recognized by related host, the typical
example like hard-wired mmc devices and usb devices.
This power sequence is hard to be described at device tree and handled by
related host driver, so we have crea
From: Joshua Clayton
Previously the onboard hub was made to work by treating its
reset gpio as a regulator enable.
Get rid of that kludge now that pwseq has added reset gpio support
Move pin muxing the hub reset pin into the usbh1 group
Signed-off-by: Joshua Clayton
Signed-off-by: Peter Chen
-
Some hard-wired USB devices need to do power sequence to let the
device work normally, the typical power sequence like: enable USB
PHY clock, toggle reset pin, etc. But current Linux USB driver
lacks of such code to do it, it may cause some hard-wired USB devices
works abnormal or can't be recogniz
The current dts describes USB HUB's property at USB controller's
entry, it is improper. The USB HUB should be the child node
under USB controller, and power sequence properties are under
it. Besides, using gpio pinctrl setting for USB2415's reset pin.
Signed-off-by: Peter Chen
Signed-off-by: Josh
From: Joshua Clayton
Give usb nodes #address and #size attributes, so that a child node
representing a permanently connected device such as an onboard hub may
be addressed with a attribute
Signed-off-by: Joshua Clayton
Signed-off-by: Peter Chen
---
arch/arm/boot/dts/imx6qdl.dtsi | 6 ++
Hi all,
This is a follow-up for my last power sequence framework patch set [1].
According to Rob Herring and Ulf Hansson's comments[2]. The kinds of
power sequence instances will be added at postcore_initcall, the match
criteria is compatible string first, if the compatible string is not
matched b
Add optional properties for power sequence.
Signed-off-by: Peter Chen
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/usb/usb-device.txt | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/usb/usb-device.txt
b/Documentatio
Add code comment to make it clear that the fall-through is intentional.
Read the link for more details: https://lkml.org/lkml/2017/2/9/292
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/musb/musb_core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/musb/musb_core.c b/drive
sorry, got the letter branch cleaned, so haven`t seen your reply
tested on 4.9.9 kernel
[13964.125187] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[13964.150525] DMAR: DRHD: handling fault status reg 2
[13964.150532] DMAR: [DMA Read] Request device [02:00.0] fault addr
fffb1000 [fault reason 0
On 2017-02-10 04:30, Felipe Balbi wrote:
> Hi,
>
> Greg KH writes:
>> On Thu, Feb 09, 2017 at 10:04:43AM -0800, Stefan Agner wrote:
>>> On 2017-02-01 08:59, Stefan Agner wrote:
>>> > On 2017-02-01 00:06, Greg KH wrote:
>>> >> On Tue, Jan 31, 2017 at 06:19:16PM -0800, Stefan Agner wrote:
>>> >>> C
On Friday, February 10, 2017 2:12:36 PM CET Linus Walleij wrote:
>
> > + /* Right now device-tree probed devices don't get dma_mask set.
> > +* Since shared usb code relies on it, set it here for now.
> > +* Once we have dma capability bindings this can go away.
> > +
On 02/10/2017 10:51 AM, David Miller wrote:
> From: Kalle Valo
> Date: Thu, 09 Feb 2017 16:10:06 +0200
>
>> Florian Fainelli writes:
>>
> If not, for something like this it's a must:
>
> drivers/net/wireless/ath/wil6210/cfg80211.c:24:30: error: expected ‘)’
> before ‘bool’
>
From: Kalle Valo
Date: Thu, 09 Feb 2017 16:10:06 +0200
> Florian Fainelli writes:
>
If not, for something like this it's a must:
drivers/net/wireless/ath/wil6210/cfg80211.c:24:30: error: expected ‘)’
before ‘bool’
module_param(disable_ap_sme, bool, 0444);
On Fri, Feb 10, 2017 at 07:38:04PM +0200, cristian.bir...@microchip.com wrote:
> From: Cristian Birsan
>
> This patch provides fixes for the following:
> - fifo table parameters validation against device tree values
> - coding style
> - error message display
> - Kconfig co
From: Cristian Birsan
This patch provides fixes for the following:
- fifo table parameters validation against device tree values
- coding style
- error message display
- Kconfig comments
Signed-off-by: Cristian Birsan
---
drivers/usb/gadget/udc/Kconfig
> >> --
> >> 1.7.9.5
> > Hi, Balbi and all guys,
> > Any comment for these patches? Can they be accepted?
>
> Rob had comments which you didn't reply yet. I cannot take this patchset
> yet ;-)
>
Balbi,
I look into his mail again, which was based v3, and I replied it.
He had different understandin
> >> >> Why do you need the first field? Is the 2nd field used if the 1st is 0?
> >> >> If not, then just use the presence of the property to enable or not.
> >> > The first field is one switch.
> >> > When it is 1, means undefined length INCR burst type enabled, we
> >> > can use
> >> any length l
On Tue, Jan 31, 2017 at 01:38:34AM +0800, kbuild test robot wrote:
> drivers/usb/typec/typec.c:1249:1-3: WARNING: PTR_ERR_OR_ZERO can be used
>
>
> Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
>
> Generated by: scripts/coccinelle/api/ptr_ret.cocci
>
> CC: Heikki Krogerus
> Signed
2017-02-10 14:34 GMT+01:00 Krzysztof Kozlowski :
> On Thu, Feb 09, 2017 at 11:26:48AM +0100, Richard Genoud wrote:
>> I did some tests with XU3 and XU4, playing with USB2 and USB3 quirks
>> (snps,dis_u{2,3}_susphy_quirk)
>>
>> kernel for the tests: next-20170206
>> DTBs: exynos5422-odroidxu3-lite.d
This series enables runtime PM and asynchronous resume/suspend support for
xhci-plat devices.
Changes since v1:
- Added Signed-off-by: Robert Foss
- Added proper metadata tags to series
Changes since v2:
- Added missing changelog to cover-letter
- Added error checking to pm_runtime_get_sync() c
From: Andrew Bresticker
USB host controllers can take a significant amount of time to suspend
and resume, adding several hundred miliseconds to the kernel resume
time. Since the XHCI controller has no outside dependencies (other than
clocks, which are suspended late/resumed early), allow it to su
On Thu, Feb 09, 2017 at 03:20:49PM +0100, Hans Ulli Kroll wrote:
>
> Add device tree probe for fotg2 driver
>
> v2:
> fix in wrong MODULE_DEVICE_TABLE
>
> Signed-off-by: Hans Ulli Kroll
> ---
> drivers/usb/host/fotg210-hcd.c | 19 +++
> 1 file changed, 19 insertions(+)
>
> dif
On Thu, Feb 09, 2017 at 09:56:54PM -0600, Gustavo A. R. Silva wrote:
> Add code comment to make it clear that the fall-through is intentional.
> Read the link for more details: https://lkml.org/lkml/2017/2/9/292
>
Don't need 'drivers:' in the subject.
> Signed-off-by: Gustavo A. R. Silva
> ---
On Thu, Feb 09, 2017 at 11:26:48AM +0100, Richard Genoud wrote:
> I did some tests with XU3 and XU4, playing with USB2 and USB3 quirks
> (snps,dis_u{2,3}_susphy_quirk)
>
> kernel for the tests: next-20170206
> DTBs: exynos5422-odroidxu3-lite.dtb exynos5422-odroidxu4.dtb
>
> USB devices used for t
On Wed, Feb 8, 2017 at 9:00 PM, Hans Ulli Kroll
wrote:
> Add device tree binding and DT driver support for fotg2-hcd controller
> The device is used on Gemini SoC.
All looks good to me.
If you send a patch on top of my git branch adding it to the
gemini.dtsi set as status = "disabled"; and gemi
On Wed, Feb 8, 2017 at 9:00 PM, Hans Ulli Kroll
wrote:
> This adds DT bindings for the Faraday FOTG2 host controller.
>
> Signed-off-by: Hans Ulli Kroll
Reviewed-by: Linus Walleij
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a mes
On Wed, Feb 8, 2017 at 9:00 PM, Hans Ulli Kroll
wrote:
> add Faraday Technology Corporation as vendor faraday for DT
>
> Signed-off-by: Hans Ulli Kroll
Reviewed-by: Linus Walleij
I think I should use this for the PCI block as well, looking over some
code and the root hub is using Faraday's PC
On Thu, Feb 9, 2017 at 3:20 PM, Hans Ulli Kroll
wrote:
> Add device tree probe for fotg2 driver
>
> v2:
> fix in wrong MODULE_DEVICE_TABLE
>
> Signed-off-by: Hans Ulli Kroll
Acked-by: Linus Walleij
> + /* Right now device-tree probed devices don't get dma_mask set.
> +* Since sh
Hi,
Greg KH writes:
> On Thu, Feb 09, 2017 at 10:04:43AM -0800, Stefan Agner wrote:
>> On 2017-02-01 08:59, Stefan Agner wrote:
>> > On 2017-02-01 00:06, Greg KH wrote:
>> >> On Tue, Jan 31, 2017 at 06:19:16PM -0800, Stefan Agner wrote:
>> >>> Currently qw_sign requires UTF-8 character to set, b
The adaptor on Analog Devices EVAL-ADXL362Z development board is used
to flash and debug firmware of on-board Renesas RL78/G13 MCU.
Signed-off-by: Maksim Salau
---
I have no access to such board to test the change, but the VID/PID pair
is found in same Windows driver package.
The stock firmware
On Thu, Feb 09, 2017 at 10:04:43AM -0800, Stefan Agner wrote:
> On 2017-02-01 08:59, Stefan Agner wrote:
> > On 2017-02-01 00:06, Greg KH wrote:
> >> On Tue, Jan 31, 2017 at 06:19:16PM -0800, Stefan Agner wrote:
> >>> Currently qw_sign requires UTF-8 character to set, but returns UTF-16
> >>> when
On Fri, Feb 10, 2017 at 10:41:45AM +0100, Johan Hovold wrote:
> On Thu, Feb 09, 2017 at 05:30:11PM +0100, Paul Menzel wrote:
>
> > Feb 09 17:24:59 centos7 kernel: usb 3-8: USB disconnect, device number 59
> > Feb 09 17:25:01 centos7 kernel: usb 3-8: new low-speed USB device number
> > 60 using xh
On Thu, Feb 09, 2017 at 05:30:11PM +0100, Paul Menzel wrote:
> Feb 09 17:24:59 centos7 kernel: usb 3-8: USB disconnect, device number 59
> Feb 09 17:25:01 centos7 kernel: usb 3-8: new low-speed USB device number
> 60 using xhci_hcd
> Feb 09 17:25:01 centos7 kernel: usb 3-8: New USB device found,
Hi,
Jerry Huang writes:
>> @@ struct dwc3 {
>> enum usb_phy_interface hsphy_mode;
>>
>> u32 fladj;
>> +/*
>> + * For INCR burst type.
>> + * First field: for undefined length INCR burst type enable.
>> + * Second field: for INCRx burst type enable
This patch adds a driver for configuration of the Microchip USB251xB/xBi
USB 2.0 hub controller series with USB 2.0 upstream connectivity, SMBus
configuration interface and two to four USB 2.0 downstream ports.
Furthermore add myself as a maintainer for this driver.
The datasheet can be found at
When HID device connect to the PC, HID devic driver announces which driver
is loaded with a kernel info message. In this case, hiddev's minor number
is always '0' even though hiddev's real minor number is another one.
To display hiddev with minor number asked from usb core, we need
to fill hiddev'
44 matches
Mail list logo
