On Wed, Dec 09, 2015 at 06:29:07AM +, Kuninori Morimoto wrote:
>
> Hi Simon
>
> > > > (As Sergei noted elsewhere, "renesas,rcar-usbhs" is consistent
> > > > with what I documented elsewhere in the patch)
> > >
> > > "renesas,rcar-usbhs" is better,
> > > but I guess you want to have "renesas
Hi Simon
> > > (As Sergei noted elsewhere, "renesas,rcar-usbhs" is consistent
> > > with what I documented elsewhere in the patch)
> >
> > "renesas,rcar-usbhs" is better,
> > but I guess you want to have "renesas,rcar-gen2-usbhs" ?
> >
> > My understanding is these
> >
> > * renesas,usbhs-r8
On Tue, Dec 08, 2015 at 11:04:00AM -0500, Alan Stern wrote:
> On Mon, 7 Dec 2015, Josh Triplett wrote:
>
> > > You're looking at the wrong files. The files to monitor are the ones
> > > in /sys/devices/pci:00/:00:14.0/usb2/2-3/2-3.1/2-3.1.2/power
> > > (assuming that this device really is
On Wed, Dec 09, 2015 at 04:48:47AM +, Kuninori Morimoto wrote:
>
> Hi Simon
>
> > (As Sergei noted elsewhere, "renesas,rcar-usbhs" is consistent
> > with what I documented elsewhere in the patch)
>
> "renesas,rcar-usbhs" is better,
> but I guess you want to have "renesas,rcar-gen2-usbhs" ?
Hi Simon
> (As Sergei noted elsewhere, "renesas,rcar-usbhs" is consistent
> with what I documented elsewhere in the patch)
"renesas,rcar-usbhs" is better,
but I guess you want to have "renesas,rcar-gen2-usbhs" ?
My understanding is these
* renesas,usbhs-r8a77xx# SoC specific
* renes
From: Peter Wu
Date: Tue, 8 Dec 2015 12:17:42 +0100
> When an interface is brought up which was previously suspended (via
> runtime PM), it would hang. This happens because napi_disable is called
> before napi_enable.
>
> Solve this by avoiding napi_enable in the resume during open function
> (
On Tue, Dec 08, 2015 at 02:51:51PM +0900, Simon Horman wrote:
> Simply document new compatibility string.
> As a previous patch adds a generic R-Car Gen2 compatibility string
> there appears to be no need for a driver updates.
>
> Also add names for SoCs.
>
> Signed-off-by: Simon Horman
Acked-b
On Tue, Dec 08, 2015 at 10:58:48AM +0100, Arnd Bergmann wrote:
> On Tuesday 08 December 2015 10:50:49 Philipp Zabel wrote:
> > Am Dienstag, den 08.12.2015, 09:37 +0800 schrieb Peter Chen:
> > > Add dt-binding documentation for generic onboard USB HUB.
> > >
> > > Signed-off-by: Peter Chen
> > > -
On Tue, Dec 08, 2015 at 05:35:28PM +0300, Sergei Shtylyov wrote:
> On 12/08/2015 08:51 AM, Simon Horman wrote:
>
> >Add fallback compatibility string.
> >This is in keeping with the fallback scheme being adopted wherever
> >appropriate for drivers for Renesas SoCs.
> >
> >Signed-off-by: Simon Horm
On Tue, Dec 08, 2015 at 08:32:49AM +, Kuninori Morimoto wrote:
>
> Hi Simon
>
> > > > Add fallback compatibility string.
> > > > This is in keeping with the fallback scheme being adopted wherever
> > > > appropriate for drivers for Renesas SoCs.
> > > >
> > > > Signed-off-by: Simon Horman
>
On Tue, Dec 08, 2015 at 11:07:55PM +0100, Steinar H. Gunderson wrote:
> On Tue, Dec 08, 2015 at 05:01:46PM -0500, Alan Stern wrote:
> > I don't see anything else to change. You can submit this to Greg KH
> > and add:
> >
> > Acked-by: Alan Stern
>
> Great!
>
> How do I submit? Just do git sen
On 08.12.2015 17:30, Alan Stern wrote:
> On Tue, 8 Dec 2015, Vladimir Zapolskiy wrote:
>
>> Remove mach/irq.h from the list of included headers, there is no
>> compilation dependency on this include file, the change is needed
>> to prevent a compilation failure, when mach/irq.h is removed.
>>
>> A
On Tue, Dec 08, 2015 at 05:01:46PM -0500, Alan Stern wrote:
> I don't see anything else to change. You can submit this to Greg KH
> and add:
>
> Acked-by: Alan Stern
Great!
How do I submit? Just do git send-email to some address?
Do you know what the status is for the LPM blacklisting patch
On Tue, 8 Dec 2015, Steinar H. Gunderson wrote:
> On Tue, Dec 08, 2015 at 03:26:28PM -0500, Alan Stern wrote:
> > I just noticed this -- usbm->memlist needs to be initialized before
> > dec_usb_memory_use_count() can be called. INIT_LIST_HEAD before the
> > "if" statement will fix the problem.
>
On Tue, Dec 08, 2015 at 03:26:28PM -0500, Alan Stern wrote:
> I just noticed this -- usbm->memlist needs to be initialized before
> dec_usb_memory_use_count() can be called. INIT_LIST_HEAD before the
> "if" statement will fix the problem.
Done.
> The patch could use one more ingredient. In
> in
On Mon, 7 Dec 2015, Steinar H. Gunderson wrote:
> On Mon, Dec 07, 2015 at 10:45:55AM -0500, Alan Stern wrote:
> >> Here we are. Lightly tested, I believe all comments should be addressed.
> > This looks quite good. I have only a couple of comments.
>
> Excellent. I'm sorry we've needed so many r
To prevent VBUS contention, the am335x MUSB phy senses VBUS first before
transitioning to host mode. However, for host-only mode, VBUS could be
directly tied to 5V power rail which could prevent MUSB transitions to
host mode.
This change receives dr_mode of the controller then bypass the first
VBU
Hi,
Bin Liu writes:
> Felipe,
>
> On 12/08/2015 09:05 AM, Bin Liu wrote:
>> Felipe,
>>
>> On 12/08/2015 08:59 AM, Felipe Balbi wrote:
>>>
>>> Hi,
>>>
>>> Bin Liu writes:
diff --git a/drivers/usb/Kconfig b/drivers/usb/Kconfig
index 5b625e2..b33e00b 100644
--- a/drivers/usb/Kconfig
Felipe,
On 12/08/2015 09:05 AM, Bin Liu wrote:
Felipe,
On 12/08/2015 08:59 AM, Felipe Balbi wrote:
Hi,
Bin Liu writes:
diff --git a/drivers/usb/Kconfig b/drivers/usb/Kconfig
index 5b625e2..b33e00b 100644
--- a/drivers/usb/Kconfig
+++ b/drivers/usb/Kconfig
@@ -32,7 +32,7 @@ if USB_SUPPORT
On Mon, 7 Dec 2015, Josh Triplett wrote:
> > You're looking at the wrong files. The files to monitor are the ones
> > in /sys/devices/pci:00/:00:14.0/usb2/2-3/2-3.1/2-3.1.2/power
> > (assuming that this device really is the mouse and not something else).
> > Handy shortcut link: /sys/bu
Hi Baolin,
[auto build test ERROR on balbi-usb/next]
[also build test ERROR on v4.4-rc4 next-20151208]
url:
https://github.com/0day-ci/linux/commits/Baolin-Wang/gadget-Introduce-the-usb-charger-framework/20151208-163942
base: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
On 7 December 2015 at 18:37, Peter Chen wrote:
> Current USB HUB driver lacks of platform interfaces to configure
> external signal on HUB chip, eg, the PHY input clock and gpio reset
> pin for HUB, these kinds of HUBs are usually soldered at the board,
> and they are not hot-plug USB devices.
>
>
On Tue, 8 Dec 2015, Vladimir Zapolskiy wrote:
> Remove mach/irq.h from the list of included headers, there is no
> compilation dependency on this include file, the change is needed
> to prevent a compilation failure, when mach/irq.h is removed.
>
> Additionally remove other unneeded includes.
>
On Tue, 8 Dec 2015, Pathak, Rahul (R.) wrote:
> From: Rahul Pathak
>
> Fixing coccicheck warning which recommends to use memdup_user instead
> to reimplement its code, using memdup_user simplifies the code
>
> ./drivers/usb/core/devio.c:1398:11-18: WARNING opportunity for memdup_user
>
> Chang
Hi,
Bin Liu writes:
> "This bit should be set high prior to setting bit 0 and cleared after bit > 0
> is cleared."
>
> and on the other side:
> "Both the soft_reset and soft_reset_isolation bits should be asserted
> simultaneously."
>
> The hang you saw could
Felipe,
On 12/08/2015 08:59 AM, Felipe Balbi wrote:
Hi,
Bin Liu writes:
diff --git a/drivers/usb/Kconfig b/drivers/usb/Kconfig
index 5b625e2..b33e00b 100644
--- a/drivers/usb/Kconfig
+++ b/drivers/usb/Kconfig
@@ -32,7 +32,7 @@ if USB_SUPPORT
config USB_COMMON
tristate
defau
Hi,
Bin Liu writes:
> diff --git a/drivers/usb/Kconfig b/drivers/usb/Kconfig
> index 5b625e2..b33e00b 100644
> --- a/drivers/usb/Kconfig
> +++ b/drivers/usb/Kconfig
> @@ -32,7 +32,7 @@ if USB_SUPPORT
> config USB_COMMON
> tristate
> default y
> - depends on USB || USB_GADGET ||
On 12/08/2015 08:35 AM, Felipe Balbi wrote:
Hi,
Bin Liu writes:
Felipe,
On 12/08/2015 08:20 AM, Felipe Balbi wrote:
Hi,
Gregory CLEMENT writes:
if it is the case then it didn't fix the issue I had.
I activated the following debug line:
[musb_hdrc]musb_interrupt =_ "** IRQ %s usb%04x
On 12/08/2015 08:51 AM, Simon Horman wrote:
Add fallback compatibility string.
This is in keeping with the fallback scheme being adopted wherever
appropriate for drivers for Renesas SoCs.
Signed-off-by: Simon Horman
---
Documentation/devicetree/bindings/usb/renesas_usbhs.txt | 4 ++--
drive
On Tue, Dec 08, 2015 at 12:39:12PM +, Hayes Wang wrote:
> Peter Wu [mailto:pe...@lekensteyn.nl]
> > Sent: Tuesday, December 08, 2015 7:18 PM
> >
> > When an interface is brought up which was previously suspended (via
> > runtime PM), it would hang. This happens because napi_disable is called
>
Hi,
Bin Liu writes:
> Felipe,
>
> On 12/08/2015 08:20 AM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Gregory CLEMENT writes:
>> if it is the case then it didn't fix the issue I had.
>>
>> I activated the following debug line:
>>
>> [musb_hdrc]musb_interrupt =_ "** IRQ %s usb%04x tx
Felipe,
On 12/08/2015 08:20 AM, Felipe Balbi wrote:
Hi,
Gregory CLEMENT writes:
if it is the case then it didn't fix the issue I had.
I activated the following debug line:
[musb_hdrc]musb_interrupt =_ "** IRQ %s usb%04x tx%04x rx%04x\012"
[musb_dsps]dsps_interrupt =p "usbintr (%x) epintr(%
Hello.
On 12/08/2015 01:31 AM, Hauke Mehrtens wrote:
From: Rafał Miłecki
This fixes problem with controller seeing devices only in some small
percentage of cold boots.
This quirk is also added to the platform data so we can activate it
when we register our platform driver.
Signed-off-by: Raf
Hi,
Gregory CLEMENT writes:
if it is the case then it didn't fix the issue I had.
I activated the following debug line:
[musb_hdrc]musb_interrupt =_ "** IRQ %s usb%04x tx%04x rx%04x\012"
[musb_dsps]dsps_interrupt =p "usbintr (%x) epintr(%x)\012"
But I didn
Hi,
Peter Chen writes:
>> seriously ? Is this really all ? What about that reset line below ?
>
> The clock is PHY input clock on the HUB, this clock may from SoC's
> PLL.
oh, you might have misunderstood my comment. I'm saying that there is
more than one thing you could cache in your private s
Hi Dan,
W dniu 08.12.2015 o 14:15, Dan Carpenter pisze:
Hello Andrzej Pietrasiewicz,
The patch b4b91143ec45: "usb: gadget: tcm: factor out f_tcm" from Oct
27, 2015, leads to the following static checker warning:
drivers/usb/gadget/function/f_tcm.c:1149 usbg_submit_command()
war
Hello Andrzej Pietrasiewicz,
The patch b4b91143ec45: "usb: gadget: tcm: factor out f_tcm" from Oct
27, 2015, leads to the following static checker warning:
drivers/usb/gadget/function/f_tcm.c:1149 usbg_submit_command()
warn: bool is not less than zero.
drivers/usb/gadget/function
On 01/12/15 18:31, Felipe F. Tonello wrote:
> This patch introduces pre-allocation of IN endpoint USB requests. This
> improves on latency (requires no usb request allocation on transmit) and avoid
> several potential probles on allocating too many usb requests (which involves
> DMA pool allocation
Peter Wu [mailto:pe...@lekensteyn.nl]
> Sent: Tuesday, December 08, 2015 7:18 PM
>
> When an interface is brought up which was previously suspended (via
> runtime PM), it would hang. This happens because napi_disable is called
> before napi_enable.
>
> Solve this by avoiding napi_enable in the re
From: Rahul Pathak
Fixing coccicheck warning which recommends to use memdup_user instead
to reimplement its code, using memdup_user simplifies the code
./drivers/usb/core/devio.c:1398:11-18: WARNING opportunity for memdup_user
Changes after v1: setting isopkt=NULL for proper kfree() call
Signe
Hi,
On Tue, Dec 08, 2015 at 10:17:47AM +0900, Chanwoo Choi wrote:
> I can't agree to add specific function for only one device driver.
> As I commented, it is not appropriate way.
OK, I'll prepare something else for this.
Thanks,
--
heikki
--
To unsubscribe from this list: send the line "unsu
From: Rahul Pathak
Fixing coccicheck warning which recommends to use memdup_user instead
to reimplement its code, using memdup_user simplifies the code
./drivers/usb/core/devio.c:1398:11-18: WARNING opportunity for memdup_user
Signed-off-by: Rahul Pathak
---
drivers/usb/core/devio.c | 8 +++--
On Tue, Dec 08, 2015 at 11:38:59AM +, Pathak, Rahul (R.) wrote:
> diff --git a/drivers/usb/core/devio.c b/drivers/usb/core/devio.c
> index 38ae877c..05266f0 100644
> --- a/drivers/usb/core/devio.c
> +++ b/drivers/usb/core/devio.c
> @@ -1395,11 +1395,9 @@ static int proc_do_submiturb(struct usb_
When an interface is brought up which was previously suspended (via
runtime PM), it would hang. This happens because napi_disable is called
before napi_enable.
Solve this by avoiding napi_enable in the resume during open function
(netif_running is true when open is called, IFF_UP is set after a
su
On 05.12.2015 06:02, Daniel J Blueman wrote:
On 1 December 2015 at 16:26, Mathias Nyman
wrote:
usb2 ports need to signal resume for 20ms before moving to U0 state.
Both device and host can initiate resume.
On host initated resume port is set to resume state, sleep 20ms,
and finally set port to
On Tue, Dec 08, 2015 at 03:18:59AM +, Hayes Wang wrote:
> Peter Wu
> > Sent: Tuesday, December 08, 2015 12:59 AM
> [...]
> > + if (tp->netdev->flags & IFF_UP) {
>
> Maybe you could just replace the checking of netif_running(tp->netdev)
> with this.
Simply replacing netif_run
On Tuesday 08 December 2015 10:50:49 Philipp Zabel wrote:
> Am Dienstag, den 08.12.2015, 09:37 +0800 schrieb Peter Chen:
> > Add dt-binding documentation for generic onboard USB HUB.
> >
> > Signed-off-by: Peter Chen
> > ---
> > .../bindings/usb/generic-onboard-hub.txt | 28
> > ++
Hi Peter,
Am Dienstag, den 08.12.2015, 09:37 +0800 schrieb Peter Chen:
> Add dt-binding documentation for generic onboard USB HUB.
>
> Signed-off-by: Peter Chen
> ---
> .../bindings/usb/generic-onboard-hub.txt | 28
> ++
> 1 file changed, 28 insertions(+)
> creat
On Tuesday 08 December 2015 09:37:48 Peter Chen wrote:
> +struct usb_hub_generic_data {
> + struct clk *clk;
> +};
> +
> +static int usb_hub_generic_probe(struct platform_device *pdev)
> +{
> + struct device *dev = &pdev->dev;
> + struct usb_hub_generic_platform_data *pdata = dev->plat
On Tuesday 08 December 2015 17:20:46 Peter Chen wrote:
> On Tue, Dec 08, 2015 at 12:30:59AM -0200, Fabio Estevam wrote:
> > On Mon, Dec 7, 2015 at 11:37 PM, Peter Chen
> > wrote:
> > > Add dt-binding documentation for generic onboard USB HUB.
> > >
> > > Signed-off-by: Peter Chen
> > > ---
> > >
On Tue, Dec 08, 2015 at 05:26:56PM +0800, Peter Chen wrote:
> On Tue, Dec 08, 2015 at 07:19:05AM +0100, Sascha Hauer wrote:
> > > + hub_data = devm_kzalloc(dev, sizeof(*hub_data), GFP_KERNEL);
> > > + if (!hub_data)
> > > + return -ENOMEM;
> > > +
> > > + if (dev->of_node) {
> > > +
On Tue, Dec 08, 2015 at 11:16:31AM +0800, kbuild test robot wrote:
> Hi Peter,
>
> [auto build test ERROR on usb/usb-testing]
> [also build test ERROR on v4.4-rc4 next-20151207]
>
> url:
> https://github.com/0day-ci/linux/commits/Peter-Chen/USB-add-generic-onboard-US
On Tue, Dec 08, 2015 at 07:19:05AM +0100, Sascha Hauer wrote:
> > + hub_data = devm_kzalloc(dev, sizeof(*hub_data), GFP_KERNEL);
> > + if (!hub_data)
> > + return -ENOMEM;
> > +
> > + if (dev->of_node) {
> > + struct device_node *node = dev->of_node;
> > +
> > +
On Tue, Dec 08, 2015 at 12:30:59AM -0200, Fabio Estevam wrote:
> On Mon, Dec 7, 2015 at 11:37 PM, Peter Chen wrote:
> > Add dt-binding documentation for generic onboard USB HUB.
> >
> > Signed-off-by: Peter Chen
> > ---
> > .../bindings/usb/generic-onboard-hub.txt | 28
> > +++
On Mon, Dec 07, 2015 at 08:59:19PM -0600, Felipe Balbi wrote:
>
> Hi,
>
> Peter Chen writes:
> > diff --git a/drivers/usb/misc/Makefile b/drivers/usb/misc/Makefile
> > index 45fd4ac..da52e9a 100644
> > --- a/drivers/usb/misc/Makefile
> > +++ b/drivers/usb/misc/Makefile
> > @@ -29,3 +29,4 @@ obj-
Hi Felipe,
On lun., déc. 07 2015, Felipe Balbi wrote:
> Hi,
>
> Gregory CLEMENT writes:
>> Hi Felipe,
>>
>> I am going back on this subject (again :) )
>>
>> On mar., oct. 20 2015, Gregory CLEMENT
>> wrote:
>>
>>> Hi Felipe,
>>>
>>> On lun., oct. 05 2015, Felipe Balbi wrote:
>>>
>>>
On Wed, Nov 25, 2015 at 09:54:58AM -0600, Dan Williams wrote:
> On Wed, 2015-11-25 at 13:13 +0100, M. Hrdlička wrote:
> > Hello,
> > log script told me, that I may to tell you about add this device to
> > propper linux driver.
> >
> > Device is combo USB modem Celot CTD-200, manufacturing date in
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.
Signed-off-
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 b
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
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 the
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
---
drivers/usb/gadget/charger.c
Hi Simon
> > > Add fallback compatibility string.
> > > This is in keeping with the fallback scheme being adopted wherever
> > > appropriate for drivers for Renesas SoCs.
> > >
> > > Signed-off-by: Simon Horman
> > > ---
> > (snip)
> > > + {
> > > + .compatible = "renesas,usbhs",
> > >
63 matches
Mail list logo
