Am 31.01.2017 um 03:32 schrieb John Youn:
> On 1/28/2017 2:06 PM, Heiner Kallweit wrote:
>> Supplies for vusb_a and vusb_d are needed only on a minority of systems
>> supported by the dwc2 driver (AFAIK systems with Samsung SoCs).
>>
>> On all other systems this results in these harmless but
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I
At boot time, probe function of multiple connected devices
(proprietary devices) execute simultaneously. And because
of the following code path race condition happens:
probe->usb_register_dev->init_usb_class
Tested with these changes, and problem has been solved.
thanks,
ajay kaher
On 1/28/2017 6:21 PM, Bruno Herrera wrote:
> This patch introduces a new parameter to activate USB OTG HS/FS core embedded
> phy transceiver. The STM32F4x9 SoC uses the GGPIO register to enable the
> transceiver.
> Also add the dwc2_core_params structure for stm32f4 otg fs.
>
Could you fix the
On 1/28/2017 2:06 PM, Heiner Kallweit wrote:
> Supplies for vusb_a and vusb_d are needed only on a minority of systems
> supported by the dwc2 driver (AFAIK systems with Samsung SoCs).
>
> On all other systems this results in these harmless but annoying
> warnings:
>
> c900.usb supply vusb_d
Please disregard this email thread as this is has been identified as a
bluetooth driver issue. Email has been forward to the linux-bluetooth
email address.
On Mon, Jan 30, 2017 at 11:34 PM, Leif Liddy wrote:
> Hello,
>
> I have a Samsung ATIV Book 9 12.2 (2015) that has
Hello,
I am starting work on a board that has the Intel Skylake chipset, which has
hardware for doing USB-device.
The Intel chipset USB-device hardware is the Synopsys DesignWare Controller 3,
aka "dwc3".
The Linux source tree has code for dwc3, so I thought to try running Linux on
this
On Mon, Jan 30, 2017 at 08:03:23AM +0100, Thierry Reding wrote:
> On Mon, Jan 30, 2017 at 07:45:21AM +0100, Greg Kroah-Hartman wrote:
> > On Mon, Jan 30, 2017 at 10:36:29AM +0530, Shailendra Verma wrote:
> > > of_device_get_match_data could return NULL, and so can cause
> > > a NULL pointer
Change goto labels to meaningful names from a series of errNs.
Signed-off-by: Shuah Khan
---
Rebased to usb-next
drivers/usb/dwc3/dwc3-exynos.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/usb/dwc3/dwc3-exynos.c
This series add support of DA8xx to CPPI 4.1 driver.
As the CPPI 4.1 is now generic, we only had to add the glue for DA8xx.
This serie should applied on top of
"[PATCH v3 0/7] dmaengine: cppi41: Make CPPI 4.1 driver more generic".
Changes in v4:
- Fix the address overlaping between usb and
The DA8xx has a CPPI 4.1 DMA controller.
This is add the glue layer required to make it work on DA8xx.
Signed-off-by: Alexandre Bailon
---
drivers/dma/Kconfig | 6 +++---
drivers/dma/cppi41.c | 23 +++
2 files changed, 26 insertions(+), 3 deletions(-)
During the teardown of a RX channel, because there is only one
completion queue available for RX channel, descriptor of another
channel may be popped which will cause 2 warnings:
- the first one because we popped a wrong descriptor
(neither the channel's descriptor, nor the teardown descriptor).
This adds the CPPI 4.1 DMA controller to the USB OTG controller.
Changes since v4:
- Fix the overlaping address between usb and cppi41 nodes.
Signed-off-by: Alexandre Bailon
---
arch/arm/boot/dts/da850.dtsi | 27 ++-
1 file changed, 26
DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx CPPI 4.1 DMA controller.
Signed-off-by: Alexandre Bailon
Acked-by: Rob Herring
---
.../devicetree/bindings/usb/da8xx-usb.txt | 41 +-
1 file changed, 40 insertions(+), 1
On Monday 30 January 2017 17:17:03 Alan Stern wrote:
> On Sun, 29 Jan 2017, Pali Rohár wrote:
> > On Wednesday 11 January 2017 16:23:29 Alan Stern wrote:
> > > On Tue, 10 Jan 2017, James Bottomley wrote:
> > > > On Tue, 2017-01-10 at 16:00 -0500, Alan Stern wrote:
> > > > > In theory, I suppose we
Hi Heikki,
[auto build test WARNING on usb/usb-testing]
[also build test WARNING on v4.10-rc6 next-20170130]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Heikki-Krogerus/lib-string-add
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-off-by: Fengguang Wu
---
On Sun, 29 Jan 2017, Pali Rohár wrote:
> On Wednesday 11 January 2017 16:23:29 Alan Stern wrote:
> > On Tue, 10 Jan 2017, James Bottomley wrote:
> > > On Tue, 2017-01-10 at 16:00 -0500, Alan Stern wrote:
> > > > In theory, I suppose we could change the kernel so that it would
> > > > default to
Hi,
Felipe Balbi writes:
> Roger Quadros writes:
>>> Roger Quadros writes:
> (hmm, I didn't receive your reply in my intel inbox, only
> gmail. Odd. Replying to myself here, but it should be on your reply,
> rater).
>
>
Hi,
Roger Quadros writes:
>> Roger Quadros writes:
(hmm, I didn't receive your reply in my intel inbox, only
gmail. Odd. Replying to myself here, but it should be on your reply,
rater).
Felipe Balbi writes:
>> The
Hello.
This bug was redirected from pulseaudio bugtracker
(https://bugs.freedesktop.org/show_bug.cgi?id=99260) and from kernel
bugtracker (https://bugzilla.kernel.org/show_bug.cgi?id=191941).
When I connect my Fiio X5 II as external DAC to my PC PulseAudio hangs
(unkillable). Google knows about
On 30/01/17 14:59, Felipe Balbi wrote:
>
> Hi,
>
> Roger Quadros writes:
>>> (hmm, I didn't receive your reply in my intel inbox, only
>>> gmail. Odd. Replying to myself here, but it should be on your reply,
>>> rater).
>>>
>>> Felipe Balbi writes:
> The
Hi,
Roger Quadros writes:
>> (hmm, I didn't receive your reply in my intel inbox, only
>> gmail. Odd. Replying to myself here, but it should be on your reply,
>> rater).
>>
>> Felipe Balbi writes:
The previous commit
Make a simple helper for matching strings with sysfs
attribute files. In most parts the same as match_string(),
except sysfs_match_string() uses sysfs_streq() instead of
strcmp() for matching. This is more convenient when used
with sysfs attributes.
Signed-off-by: Heikki Krogerus
The purpose of USB Type-C connector class is to provide
unified interface for the user space to get the status and
basic information about USB Type-C connectors on a system,
control over data role swapping, and when the port supports
USB Power Delivery, also control over power role swapping
and
The USB Type-C class is meant to provide unified interface to the
userspace to present the USB Type-C ports in a system.
Changes since v15:
- "stingification" as proposed by Felipe
- Checking ARRAY_SIZE in supported_accessory_modes() as proposed by Guenter
Changes since v14:
- Fixes proposed by
This adds driver for the USB Type-C PHY on Intel WhiskeyCove
PMIC which is available on some of the Intel Broxton SoC
based platforms.
Signed-off-by: Heikki Krogerus
Reviewed-by: Mika Westerberg
Reviewed-by: Felipe Balbi
Hi,
On 27/01/17 17:47, Felipe Balbi wrote:
>
> Hi,
>
> (hmm, I didn't receive your reply in my intel inbox, only
> gmail. Odd. Replying to myself here, but it should be on your reply,
> rater).
>
> Felipe Balbi writes:
>>> The previous commit
On Mon, Jan 30, 2017 at 08:25:25AM +, Ajay Kaher wrote:
>
First off, you are sending html email, which the mailing list keeps
rejecting, why are you ignoring that?
>
> There is race condition when two USB class drivers try to call
>
> init_usb_class at the same time and leads to crash.
This patch splits the amd5536udc driver into two -- one that does
pci device registration and the other file that does the rest of
the driver tasks like the gadget/ep ops etc for Synopsys UDC.
This way of splitting helps in exporting core driver symbols which
can be used by any other platform/pci
This patch adds a struct device member to UDC data structure and
makes changes to the arguments of dev_err and dev_dbg calls so that
the debug prints work for both pci and platform devices.
Signed-off-by: Raviteja Garimella
---
The changes are being submitted as PATCH this time. Below are the
details of main changes with respect to previous RFC versions.
Changes from RFC v2:
===
Patch 1/6 now splits the driver into amd5536udc_pci_.c (which
contains only the PCI device registration part), and amd5536udc.c
Change the argument from NULL to a struct device for the
dma_pool_create call during dma init.
Signed-off-by: Raviteja Garimella
---
drivers/usb/gadget/udc/snps_udc_core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
33 matches
Mail list logo