Hi,
On 04-03-16 05:35, Greg Kroah-Hartman wrote:
On Sat, Feb 27, 2016 at 05:58:58PM +0100, Hans de Goede wrote:
From: Reinder de Haan
At least the EHCI/OHCI found on the Allwinnner H3 SoC needs multiple
reset lines, the controller will not initialize while the reset for
Hi,
"Felipe F. Tonello" writes:
> [ text/plain ]
> Since f_midi_transmit is called by both ALSA and USB frameworks, it can
> potentially cause a race condition between both calls. This is bad because the
> way f_midi_transmit is implemented can't handle concurrent calls.
Jaret Cantu writes:
> [ text/plain ]
> The TX settings can be calibrated for particular hardware. The
> phy is reset by Linux, so this cannot be handled by the bootloader.
>
> The TRM mentions that the maximum resistance should be used for the
> DN/DP calibration in
Hi,
On 04-03-16 08:13, Yves-Alexis Perez wrote:
On mar., 2016-03-01 at 11:49 +0100, Hans de Goede wrote:
Hi,
On 01-03-16 10:42, Yves-Alexis Perez wrote:
Hi,
[sorry if this is not the right point for reporting bugs, I took the email
addresses from MAINTAINERS but please point me to the
Hi,
"Felipe F. Tonello" writes:
> [ text/plain ]
> This gadget uses a bmAttributes and MaxPower that requires the USB bus to be
> powered from the host, which is not correct because this configuration is
> device
> specific, not a USB-MIDI requirement.
>
> This patch
On mar., 2016-03-01 at 11:49 +0100, Hans de Goede wrote:
> Hi,
>
> On 01-03-16 10:42, Yves-Alexis Perez wrote:
> >
> > Hi,
> >
> > [sorry if this is not the right point for reporting bugs, I took the email
> > addresses from MAINTAINERS but please point me to the correct place if
> > needed]
>
"Felipe F. Tonello" writes:
> [ text/plain ]
> Signed-off-by: Felipe F. Tonello
no commit log == no commit
--
balbi
signature.asc
Description: PGP signature
"Felipe F. Tonello" writes:
> [ text/plain ]
> Signed-off-by: Felipe F. Tonello
no commit log == no commit
> ---
> drivers/usb/gadget/function/f_midi.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git
Hi,
"Felipe F. Tonello" writes:
> [ text/plain ]
> Patches are pretty much self-described.
>
> Patch 1 is revised from comments.
you really need to describe what you changed. This also should have v2
on subject line.
I guess it's too late to get this in v4.6 merge
On Sat, Feb 27, 2016 at 05:58:58PM +0100, Hans de Goede wrote:
> From: Reinder de Haan
>
> At least the EHCI/OHCI found on the Allwinnner H3 SoC needs multiple
> reset lines, the controller will not initialize while the reset for
> its companion is still asserted, which
On Thu, Feb 18, 2016 at 05:55:47PM +0200, Mathias Nyman wrote:
> Hi Greg
>
> A few more patches for 4.6.
> At least the first one would be important to get with the rest of the
> USB 3.1 SSP Isoc patches to 4.6
> Without it the SSP Isoc endpoint companion descriptor parsing
> may mess up the
On Fri, Mar 04, 2016 at 03:23:05AM +0100, Andrew Lunn wrote:
> On Fri, Mar 04, 2016 at 10:02:42AM +0800, Peter Chen wrote:
> > On Thu, Mar 03, 2016 at 02:54:55PM -0600, Rob Herring wrote:
> > > On Thu, Mar 3, 2016 at 4:01 AM, Peter Chen wrote:
> > > > Some hard-wired USB
On Fri, Mar 04, 2016 at 03:17:30AM +0100, Andrew Lunn wrote:
> > > > diff --git a/drivers/usb/chipidea/host.c b/drivers/usb/chipidea/host.c
> > > > index 053bac9..55120ef 100644
> > > > --- a/drivers/usb/chipidea/host.c
> > > > +++ b/drivers/usb/chipidea/host.c
> > > > @@ -109,15 +109,25 @@ static
On Fri, Mar 04, 2016 at 10:02:42AM +0800, Peter Chen wrote:
> On Thu, Mar 03, 2016 at 02:54:55PM -0600, Rob Herring wrote:
> > On Thu, Mar 3, 2016 at 4:01 AM, Peter Chen wrote:
> > > Some hard-wired USB devices need to do power sequence to let the
> > > device work normally,
> > > diff --git a/drivers/usb/chipidea/host.c b/drivers/usb/chipidea/host.c
> > > index 053bac9..55120ef 100644
> > > --- a/drivers/usb/chipidea/host.c
> > > +++ b/drivers/usb/chipidea/host.c
> > > @@ -109,15 +109,25 @@ static int host_start(struct ci_hdrc *ci)
> > > struct ehci_hcd *ehci;
> >
On Thu, Mar 03, 2016 at 01:31:56PM -0500, Alan Stern wrote:
> On Thu, 3 Mar 2016, Peter Chen wrote:
>
> > 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
On Thu, Mar 03, 2016 at 11:30:53PM +0100, Maciej S. Szmigiero wrote:
> Hi Peter,
>
> On 03.03.2016 11:01, Peter Chen wrote:
> > From: Peter Chen
> >
> > The current dts describes USB HUB's property at USB controller's
> > entry, it is improper. The USB HUB should be
On Thu, Mar 03, 2016 at 02:54:55PM -0600, Rob Herring wrote:
> On Thu, Mar 3, 2016 at 4:01 AM, Peter Chen wrote:
> > 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
On 03/04/2016 09:44 AM, Greg Kroah-Hartman wrote:
> On Fri, Mar 04, 2016 at 09:38:58AM +0800, Lu Baolu wrote:
>>
>> On 03/04/2016 12:14 AM, Greg Kroah-Hartman wrote:
>>> On Thu, Mar 03, 2016 at 02:37:42PM +0800, Lu Baolu wrote:
Several Intel PCHs and SOCs have an internal mux that is used
On Thu, Mar 03, 2016 at 03:42:47PM +0100, Andrew Lunn wrote:
> On Thu, Mar 03, 2016 at 06:01:15PM +0800, Peter Chen wrote:
> > From: Peter Chen
> >
> > Since the hcd (chipidea core device) has no device node, so
> > if we want to describe the child node under the hcd,
On Fri, Mar 04, 2016 at 09:38:58AM +0800, Lu Baolu wrote:
>
>
> On 03/04/2016 12:14 AM, Greg Kroah-Hartman wrote:
> > On Thu, Mar 03, 2016 at 02:37:42PM +0800, Lu Baolu wrote:
> >> Several Intel PCHs and SOCs have an internal mux that is used to
> >> share one USB port between device controller
On 03/04/2016 12:12 AM, Greg Kroah-Hartman wrote:
> On Thu, Mar 03, 2016 at 02:37:42PM +0800, Lu Baolu wrote:
>> Several Intel PCHs and SOCs have an internal mux that is used to
>> share one USB port between device controller and host controller.
>> The mux is handled through the Dual Role
On 03/04/2016 12:14 AM, Greg Kroah-Hartman wrote:
> On Thu, Mar 03, 2016 at 02:37:42PM +0800, Lu Baolu wrote:
>> Several Intel PCHs and SOCs have an internal mux that is used to
>> share one USB port between device controller and host controller.
>> The mux is handled through the Dual Role
On 03/04/2016 12:15 AM, Greg Kroah-Hartman wrote:
> On Thu, Mar 03, 2016 at 02:37:40PM +0800, Lu Baolu wrote:
>> +#if IS_ENABLED(CONFIG_USB_MUX)
>> +extern int usb_mux_register(struct usb_mux_dev *mux);
>> +extern int usb_mux_unregister(struct device *dev);
>> +extern struct usb_mux_dev
Thank you very much for your reply, Your reply can solve our problems, thank you
Best Regards,
Pengcheng Li
-邮件原件-
发件人: Matthew Dharm [mailto:mdharm-...@one-eyed-alien.net]
发送时间: 2016年3月3日 23:45
收件人: Lipengcheng
抄送: gre...@linuxfoundation.org; linux-usb@vger.kernel.org
主题: Re:
The
Hi Lu,
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on v4.5-rc6 next-20160303]
[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/Lu-Baolu/usb-add-support-for-Intel-dual-role
On 03/04/2016 12:10 AM, Greg Kroah-Hartman wrote:
> On Thu, Mar 03, 2016 at 02:37:40PM +0800, Lu Baolu wrote:
>> Several Intel PCHs and SOCs have an internal mux that is used to
>> share one USB port between device controller and host controller.
>>
>> A usb port mux could be abstracted as the
Hi Lu,
[auto build test WARNING on usb/usb-testing]
[also build test WARNING on v4.5-rc6 next-20160303]
[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/Lu-Baolu/usb-add-support-for-Intel-dual
Hi Peter,
On 03.03.2016 11:01, Peter Chen wrote:
> From: Peter Chen
>
> 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.
>
> Signed-off-by: Peter Chen
On Sat, Feb 27, 2016 at 05:58:59PM +0100, Hans de Goede wrote:
> At least the EHCI/OHCI found on the Allwinnner H3 SoC needs multiple
> reset lines, the controller will not initialize while the reset for
> its companion is still asserted, which means we need to de-assert
> 2 resets for the
On Sat, Feb 27, 2016 at 05:58:58PM +0100, Hans de Goede wrote:
> From: Reinder de Haan
>
> At least the EHCI/OHCI found on the Allwinnner H3 SoC needs multiple
> reset lines, the controller will not initialize while the reset for
> its companion is still asserted, which
On Sat, Feb 27, 2016 at 12:31:24PM +0200, Antti Seppälä wrote:
> Add support for Lantiq ARX and XRX SoC families to the dwc2 driver.
>
> Signed-off-by: Antti Seppälä
> ---
> Documentation/devicetree/bindings/usb/dwc2.txt | 2 ++
Acked-by: Rob Herring
>
From: Bjørn Mork
Date: Tue, 1 Mar 2016 14:31:02 +0100
> The MC74xx and EM74xx modules use different IDs by default, according
> to the Lenovo EM7455 driver for Windows.
>
> Signed-off-by: Bjørn Mork
Applied and queued up for -stable.
--
To unsubscribe from this
The TX settings can be calibrated for particular hardware. The
phy is reset by Linux, so this cannot be handled by the bootloader.
The TRM mentions that the maximum resistance should be used for the
DN/DP calibration in order to pass USB certification.
The values for the TX registers are poorly
Some devices will silently fail setup unless they are reset first.
This is necessary even if the data interface is already in
altsetting 0, which it will be when the device is probed for the
first time. Briefly toggling the altsetting forces a function
reset regardless of the initial state.
This
On Thu, Mar 3, 2016 at 4:01 AM, Peter Chen wrote:
> 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
On Thu, Mar 03, 2016 at 05:34:11PM +0100, Johan Hovold wrote:
> Hi Greg,
>
> Here's a final set of fixes for 4.5-rc.
>
> Thanks,
> Johan
>
>
> The following changes since commit fc77dbd34c5c99bce46d40a2491937c3bcbd10af:
>
> Linux 4.5-rc6 (2016-02-28 08:41:20 -0800)
>
> are available in the
On Thu, 3 Mar 2016, Peter Chen wrote:
> 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
On Thu, 3 Mar 2016, Vladimir Zapolskiy wrote:
> The change removes direct clock management from NXP LPC32xx USB OHCI
> driver done by accessing platform clock control registers, also
> after switching the platform to a common clock framework there is
> no need to look for and enable all parent
On Thu, 3 Mar 2016, yoma sophian wrote:
> hi all:
> When I porting my platform ehci driver on kernel v4.1,
> I get back trace like below without plug in any device and just insert
> usb-common.ko, usbcore.ko and ehci-hcd.ko.
> (and detail is show in the attachment)
>
> It seems caused by the PM
On Thu, 3 Mar 2016, Johan Hovold wrote:
On Wed, Mar 02, 2016 at 09:36:55AM -0800, Aaron Marburg wrote:
On Wed, 2 Mar 2016, Oliver Neukum wrote:
On Tue, 2016-03-01 at 09:54 -0800, amarb...@apl.washington.edu wrote:
From: Aaron Marburg
The USOPTL4-4P and
On Thu, 3 Mar 2016, Robert Dobrowolski wrote:
> 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 Controller,
On Thu, 3 Mar 2016, Paolo Minazzi wrote:
> Dear all,
> I have 3 wired usb optical mouse
> [1] Logitech 0x046D:0xC077
> [2] Logitech 0x046D:0xC05A
> [3] Microsoft 0x045E:0x0737
>
> I always used 3.10 kernel and all mice have the problem of
> disconnection after 62 seconds.
> I got the latest
Hi Greg,
Here's a final set of fixes for 4.5-rc.
Thanks,
Johan
The following changes since commit fc77dbd34c5c99bce46d40a2491937c3bcbd10af:
Linux 4.5-rc6 (2016-02-28 08:41:20 -0800)
are available in the git repository at:
Hi Clemens,
On 03/03/16 11:38, Clemens Ladisch wrote:
> Felipe Ferreri Tonello wrote:
>> On 02/03/16 21:09, Clemens Ladisch wrote:
>>> Felipe F. Tonello wrote:
This refactor results in a cleaner state machine code
>>>
>>> It increases the number of states, and now juggles two state
On Thu, Mar 03, 2016 at 02:37:40PM +0800, Lu Baolu wrote:
> +#if IS_ENABLED(CONFIG_USB_MUX)
> +extern int usb_mux_register(struct usb_mux_dev *mux);
> +extern int usb_mux_unregister(struct device *dev);
> +extern struct usb_mux_dev *usb_mux_get_dev(struct device *dev);
This api needs a lot of
On Thu, Mar 03, 2016 at 02:37:42PM +0800, Lu Baolu wrote:
> Several Intel PCHs and SOCs have an internal mux that is used to
> share one USB port between device controller and host controller.
> The mux is handled through the Dual Role Configuration Register.
>
> Signed-off-by: Heikki Krogerus
On Thu, Mar 03, 2016 at 02:37:42PM +0800, Lu Baolu wrote:
> Several Intel PCHs and SOCs have an internal mux that is used to
> share one USB port between device controller and host controller.
> The mux is handled through the Dual Role Configuration Register.
>
> Signed-off-by: Heikki Krogerus
On Thu, Mar 03, 2016 at 02:37:40PM +0800, Lu Baolu wrote:
> Several Intel PCHs and SOCs have an internal mux that is used to
> share one USB port between device controller and host controller.
>
> A usb port mux could be abstracted as the following elements:
> 1) mux state: HOST or PERIPHERAL;
>
On Thu, Mar 03, 2016 at 10:00:05AM +0100, Robert Dobrowolski wrote:
> Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i
> moze zawierac informacje poufne. W razie przypadkowego otrzymania tej
> wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie;
>
The delay is present because we discovered many usb-storage devices
that were not ready to accept commands immediately after insertion.
We studied the behavior of Microsoft Windows and discovered it used a
small delay before sending commands to the device, and thus we also
implemented a delay.
On Sun, Feb 21, 2016 at 10:26:35PM -0300, Emilio López wrote:
> From: Emilio López
>
> MODULE_DEVICE_TABLE() is missing, so the module isn't auto-loading on
> supported systems. This commit adds the missing line so it loads
> automatically when building it as a
On Wed, Mar 02, 2016 at 09:36:55AM -0800, Aaron Marburg wrote:
> On Wed, 2 Mar 2016, Oliver Neukum wrote:
>
> > On Tue, 2016-03-01 at 09:54 -0800, amarb...@apl.washington.edu wrote:
> >> From: Aaron Marburg
> >>
> >> The USOPTL4-4P and USOPTL4-2P USB-to-quad/dual
On 2016-03-03, Bin Liu wrote:
>> Using next-20160302 I can very reliably hit this warning on an AM335x
>> BeagleBone by playing a short audio file over USB-Audio:
>>
>> $ aplay -Dplughw:1,0 -r 44100 -c 2 -f S16_LE
>> /usr/share/sounds/alsa/Front_Center.wav
>>
>> $ aplay -l
>>
Hi Lu,
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on v4.5-rc6 next-20160303]
[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/Lu-Baolu/usb-add-support-for-Intel-dual-role
hi all:
When I porting my platform ehci driver on kernel v4.1,
I get back trace like below without plug in any device and just insert
usb-common.ko, usbcore.ko and ehci-hcd.ko.
(and detail is show in the attachment)
It seems caused by the PM related thread that is wakened up, even
there is no
Hi John,
On Thu, Mar 03, 2016 at 03:38:10PM +0100, John Ogness wrote:
> Hi Bin,
>
> Using next-20160302 I can very reliably hit this warning on an AM335x
> BeagleBone by playing a short audio file over USB-Audio:
>
> $ aplay -Dplughw:1,0 -r 44100 -c 2 -f S16_LE
>
On Thu, Mar 03, 2016 at 06:01:15PM +0800, Peter Chen wrote:
> From: Peter Chen
>
> Since the hcd (chipidea core device) has no device node, so
> if we want to describe the child node under the hcd, we had
> to put it under its parent's node (glue layer device), and
> in
Hi Bin,
Using next-20160302 I can very reliably hit this warning on an AM335x
BeagleBone by playing a short audio file over USB-Audio:
$ aplay -Dplughw:1,0 -r 44100 -c 2 -f S16_LE
/usr/share/sounds/alsa/Front_Center.wav
$ aplay -l
List of PLAYBACK Hardware Devices
card 1: Audio [USB
On Thu, Mar 03, 2016 at 01:27:56PM +, Colin King wrote:
> From: Colin Ian King
>
> Used to be allocated and required freeing, but now
> priv->mdio->irq is now a fixed sized array and should no longer be
> free'd.
>
> Issue detected using static analysis with
From: Colin Ian King
Used to be allocated and required freeing, but now
priv->mdio->irq is now a fixed sized array and should no longer be
free'd.
Issue detected using static analysis with CoverityScan
Fixes: e7f4dc3536a400 ("mdio: Move allocation of interrupts into
On Thursday 03 March 2016 21:40:23 Krzysztof Kozlowski wrote:
> >> select MFD_SYSCON
> >> diff --git a/drivers/media/platform/exynos4-is/Kconfig
> >> b/drivers/media/platform/exynos4-is/Kconfig
> >> index 57d42c6172c5..c4317b99d257 100644
> >> ---
Paolo Minazzi writes:
> [ text/plain ]
> Dear all,
> I have 3 wired usb optical mouse
> [1] Logitech 0x046D:0xC077
> [2] Logitech 0x046D:0xC05A
> [3] Microsoft 0x045E:0x0737
>
> I always used 3.10 kernel and all mice have the problem of
> disconnection after 62 seconds.
On Thursday 03 March 2016 13:27:59 Geert Uytterhoeven wrote:
> On Thu, Mar 3, 2016 at 11:55 AM, Arnd Bergmann wrote:
> > On Thursday 03 March 2016 17:03:34 Krzysztof Kozlowski wrote:
> >> index 0da40e2e4280..5c530b6b125d 100644
> >> --- a/drivers/rtc/Kconfig
> >> +++
Dear all,
I have 3 wired usb optical mouse
[1] Logitech 0x046D:0xC077
[2] Logitech 0x046D:0xC05A
[3] Microsoft 0x045E:0x0737
I always used 3.10 kernel and all mice have the problem of
disconnection after 62 seconds.
I got the latest kernel 4.5-rc3 and I have discovered about quirks and
2016-03-03 17:03 GMT+09:00 Krzysztof Kozlowski :
> The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
> direct dependencies.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/pinctrl/Kconfig | 1 +
> 1 file changed, 1
2016-03-03 17:03 GMT+09:00 Krzysztof Kozlowski :
> The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
> direct dependencies.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/pinctrl/mvebu/Kconfig | 1 +
> 1 file changed, 1
2016-03-03 17:03 GMT+09:00 Krzysztof Kozlowski :
> The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
> direct dependencies.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/soc/qcom/Kconfig | 1 +
> 1 file changed, 1
2016-03-03 17:03 GMT+09:00 Krzysztof Kozlowski :
> The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
> direct dependencies.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/staging/media/omap4iss/Kconfig | 1 +
> 1 file
2016-03-03 19:57 GMT+09:00 Arnd Bergmann :
> On Thursday 03 March 2016 17:03:35 Krzysztof Kozlowski wrote:
>> diff --git a/drivers/media/platform/Kconfig b/drivers/media/platform/Kconfig
>> index 201f5c296a95..e5931e434fa2 100644
>> --- a/drivers/media/platform/Kconfig
>> +++
2016-03-03 21:33 GMT+09:00 Sebastian Reichel :
> Hi,
>
> On Thu, Mar 03, 2016 at 12:00:14PM +0100, Arnd Bergmann wrote:
>> On Thursday 03 March 2016 17:03:37 Krzysztof Kozlowski wrote:
>> > diff --git a/drivers/power/reset/Kconfig b/drivers/power/reset/Kconfig
>> > index
2016-03-03 21:28 GMT+09:00 Arnd Bergmann :
> On Thursday 03 March 2016 21:00:57 Krzysztof Kozlowski wrote:
>> >
>> > Not user visible.
>>
>> Hmmm... you are right (here and in other patches) but why am I getting
>> all these errors:
>> warning: (ST_IRQCHIP && HIP04_ETH &&
Hi,
On Thu, Mar 03, 2016 at 12:00:14PM +0100, Arnd Bergmann wrote:
> On Thursday 03 March 2016 17:03:37 Krzysztof Kozlowski wrote:
> > diff --git a/drivers/power/reset/Kconfig b/drivers/power/reset/Kconfig
> > index 0a6408a39c66..0f34846ae80d 100644
> > --- a/drivers/power/reset/Kconfig
> > +++
On Thursday 03 March 2016 21:00:57 Krzysztof Kozlowski wrote:
> >
> > Not user visible.
>
> Hmmm... you are right (here and in other patches) but why am I getting
> all these errors:
> warning: (ST_IRQCHIP && HIP04_ETH && STMMAC_PLATFORM && DWMAC_IPQ806X
> && DWMAC_LPC18XX && DWMAC_ROCKCHIP &&
On Thu, Mar 3, 2016 at 11:57 AM, Arnd Bergmann wrote:
>> --- a/drivers/media/platform/exynos4-is/Kconfig
>> +++ b/drivers/media/platform/exynos4-is/Kconfig
>> @@ -17,6 +17,7 @@ config VIDEO_S5P_FIMC
>> tristate "S5P/EXYNOS4 FIMC/CAMIF camera interface driver"
>>
On Thu, Mar 3, 2016 at 11:55 AM, Arnd Bergmann wrote:
> On Thursday 03 March 2016 17:03:34 Krzysztof Kozlowski wrote:
>> index 0da40e2e4280..5c530b6b125d 100644
>> --- a/drivers/rtc/Kconfig
>> +++ b/drivers/rtc/Kconfig
>> @@ -1302,6 +1302,7 @@ config RTC_DRV_AT91RM9200
>> config
2016-03-03 19:50 GMT+09:00 Arnd Bergmann :
> On Thursday 03 March 2016 17:03:41 Krzysztof Kozlowski wrote:
>> Since commit c89c0114955a ("mfd: syscon: Set regmap max_register in
>> of_syscon_register") the syscon uses ioremap so it fails on COMPILE_TEST
>> without HAS_IOMEM:
>>
>>
2016-03-03 19:53 GMT+09:00 Arnd Bergmann :
> On Thursday 03 March 2016 17:03:30 Krzysztof Kozlowski wrote:
>> config ST_IRQCHIP
>> bool
>> select REGMAP
>> + depends on HAS_IOMEM# For MFD_SYSCON
>> select MFD_SYSCON
>> help
>>
Felipe Ferreri Tonello wrote:
> On 02/03/16 21:09, Clemens Ladisch wrote:
>> Felipe F. Tonello wrote:
>>> This refactor results in a cleaner state machine code
>>
>> It increases the number of states, and now juggles two state variables.
>> I cannot agree to it being cleaner.
>
> Yes, it increases
Hi Lu,
[auto build test WARNING on usb/usb-testing]
[also build test WARNING on v4.5-rc6 next-20160303]
[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/Lu-Baolu/usb-add-support-for-Intel-dual
On Thursday 03 March 2016 17:03:40 Krzysztof Kozlowski wrote:
> index 8c20ebbc049c..f759a778d606 100644
> --- a/drivers/usb/host/Kconfig
> +++ b/drivers/usb/host/Kconfig
> @@ -45,6 +45,7 @@ config USB_XHCI_PLATFORM
>
> config USB_XHCI_MTK
> tristate "xHCI support for Mediatek MT65xx"
>
On Thursday 03 March 2016 17:03:37 Krzysztof Kozlowski wrote:
> diff --git a/drivers/power/reset/Kconfig b/drivers/power/reset/Kconfig
> index 0a6408a39c66..0f34846ae80d 100644
> --- a/drivers/power/reset/Kconfig
> +++ b/drivers/power/reset/Kconfig
> @@ -141,6 +141,7 @@ config POWER_RESET_XGENE
>
On Thursday 03 March 2016 17:03:36 Krzysztof Kozlowski wrote:
> The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
> direct dependencies.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/net/ethernet/hisilicon/Kconfig | 1 +
>
On Thursday 03 March 2016 17:03:35 Krzysztof Kozlowski wrote:
> diff --git a/drivers/media/platform/Kconfig b/drivers/media/platform/Kconfig
> index 201f5c296a95..e5931e434fa2 100644
> --- a/drivers/media/platform/Kconfig
> +++ b/drivers/media/platform/Kconfig
> @@ -79,6 +79,7 @@ config
On Thursday 03 March 2016 17:03:31 Krzysztof Kozlowski wrote:
> --- a/drivers/phy/Kconfig
> +++ b/drivers/phy/Kconfig
> @@ -225,6 +225,7 @@ config PHY_MT65XX_USB3
> config PHY_HI6220_USB
> tristate "hi6220 USB PHY support"
> depends on (ARCH_HISI && ARM64) || COMPILE_TEST
> +
On Thursday 03 March 2016 17:03:34 Krzysztof Kozlowski wrote:
> index 0da40e2e4280..5c530b6b125d 100644
> --- a/drivers/rtc/Kconfig
> +++ b/drivers/rtc/Kconfig
> @@ -1302,6 +1302,7 @@ config RTC_DRV_AT91RM9200
> config RTC_DRV_AT91SAM9
> tristate "AT91SAM9 RTT as RTC"
> depends on
On Thursday 03 March 2016 17:03:30 Krzysztof Kozlowski wrote:
> config ST_IRQCHIP
> bool
> select REGMAP
> + depends on HAS_IOMEM# For MFD_SYSCON
> select MFD_SYSCON
> help
> Enables SysCfg Controlled IRQs on STi based platforms.
>
Not user
On Thursday 03 March 2016 17:03:27 Krzysztof Kozlowski wrote:
>
> diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
> index c346be650892..5927944b46e0 100644
> --- a/drivers/clocksource/Kconfig
> +++ b/drivers/clocksource/Kconfig
> @@ -239,6 +239,7 @@ config ATMEL_PIT
>
>
On Thursday 03 March 2016 17:03:29 Krzysztof Kozlowski wrote:
> diff --git a/drivers/hwspinlock/Kconfig b/drivers/hwspinlock/Kconfig
> index 73a401662853..5ab2d51dc147 100644
> --- a/drivers/hwspinlock/Kconfig
> +++ b/drivers/hwspinlock/Kconfig
> @@ -21,6 +21,7 @@ config HWSPINLOCK_OMAP
> config
On Thursday 03 March 2016 17:03:28 Krzysztof Kozlowski wrote:
> index c77f214c9466..7fbf96bff280 100644
> --- a/drivers/dma/Kconfig
> +++ b/drivers/dma/Kconfig
> @@ -290,6 +290,7 @@ config LPC18XX_DMAMUX
> bool "NXP LPC18xx/43xx DMA MUX for PL080"
> depends on ARCH_LPC18XX ||
Hi all,
I have a patch for adding device tree support for USB device [1] some
days ago, this is a follow-up to support the USB devices which need
to do some power sequence like enabling USB PHY clock, toggling reset
gpio, etc, before this device can work normal. I have seen some use
cases for it.
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
From: Peter Chen
Since the hcd (chipidea core device) has no device node, so
if we want to describe the child node under the hcd, we had
to put it under its parent's node (glue layer device), and
in the code, we need to let the hcd knows glue layer's code,
then the USB
From: Peter Chen
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.
Signed-off-by: Peter Chen
---
arch/arm/boot/dts/imx6qdl-udoo.dtsi | 35
A udc driver should set the giveback status to -ESHUTDOWN in
usb_ep_disable(). Otherwise, a gadget driver (e.g. g_serial) might
request next data wrongly and it is possible to cause kernel panic.
Signed-off-by: Yoshihiro Shimoda
---
Hi Felipe,
> From: Felipe Balbi [mailto:ba...@kernel.org]
> Sent: Thursday, March 03, 2016 6:22 PM
>
> Hi Yoshihiro,
>
> Yoshihiro Shimoda writes:
> > [ text/plain ]
> > Hi Felipe,
> >
> > Oops, I completely forgot this patch.
> > Would you review this patch?
Hello,
On Wed 02-03-16 11:00:58, Tejun Heo wrote:
> On Fri, Feb 26, 2016 at 02:19:20PM +0800, Peter Chen wrote:
> > On Thu, Feb 25, 2016 at 05:01:12PM -0500, Tejun Heo wrote:
> > > Hello, Peter.
> > >
> > > On Wed, Feb 24, 2016 at 03:24:30PM +0800, Peter Chen wrote:
> > > > > You might want to
Hi Yoshihiro,
Yoshihiro Shimoda writes:
> [ text/plain ]
> Hi Felipe,
>
> Oops, I completely forgot this patch.
> Would you review this patch? Or should I resend it?
> I confirmed that this patch could be applied on your latest
> testing/fixes branch.
I don't
Hi Simon-san,
> From: Simon Horman [mailto:horms+rene...@verge.net.au]
> Sent: Wednesday, March 02, 2016 11:17 AM
>
> Make use of ARCH_RENESAS in place of ARCH_SHMOBILE.
>
> This is part of an ongoing process to migrate from ARCH_SHMOBILE to
> ARCH_RENESAS the motivation for which being that
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 Controller, otherwise skip.
Signed-off-by: Robert Dobrowolski
1 - 100 of 121 matches
Mail list logo