On 8.04.2016 23:13, Ivaylo Dimitrov wrote:
Hi,
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.
...
(copied from "Re: [PATCH] usb: f_mass_storage: test whether thread is
r
On Tue, Apr 05, 2016 at 05:05:14PM +0300, Roger Quadros wrote:
> The OTG state machine needs a mechanism to start and
> stop the gadget controller. Add usb_gadget_start()
> and usb_gadget_stop().
>
> Introduce usb_otg_add_gadget_udc() to allow controller drivers
> to register a gadget controller t
Hi,
Grygorii Strashko writes:
> Felipe, Seems the problem might be deeper than on first look :(
>
> Lets see what grep says below. Even if we descope all SoC's drivers,
> there still will be few USB core components which manipulate with DMA
> parameters:
>
> ---
> ./drivers/usb/core/hcd.c:
On Tue, Apr 05, 2016 at 05:05:16PM +0300, Roger Quadros wrote:
> This is the a_set_b_hnp_enable flag in the OTG state machine
> diagram and must be set when the A-Host has successfully set
> the b_hnp_enable feature of the OTG-B-Peripheral attached to it.
>
> When this bit changes we kick our OTG
On Tue, Apr 05, 2016 at 05:05:07PM +0300, Roger Quadros wrote:
> The OTG core will use struct otg_hcd_ops to interface
> with the HCD controller.
>
> The main purpose of this interface is to avoid directly
> calling HCD APIs from the OTG core as they
> wouldn't be defined in the built-in symbol ta
On Mon, Apr 18, 2016 at 01:41:38PM +1000, Mike Manning wrote:
> Please find attached patch file for addition of Link G4 and Link G4+ Ecu's.
Thanks for the patch.
Try running your patch through scripts/checkpath.pl before submitting.
It would have let you know that the patch has some whitespace is
On Tue, Apr 05, 2016 at 05:05:08PM +0300, Roger Quadros wrote:
> Move otg_fsm into usb_otg and use usb_otg wherever possible
> in the usb_otg APIs.
>
> Signed-off-by: Roger Quadros
Acked-by: Peter Chen
> ---
> drivers/usb/chipidea/ci.h| 1 -
> drivers/usb/chipidea/core.c | 12 +
This patch set is based on the latest Felipe's usb.git / testing/next
branch. (The commit id = 578bfe42fc37d588effe0d9fcd5e35e10d3d2e78)
Changes from RFC:
- rebase the latest commit of Felipe's usb.git.
- revise commit log in patch 3 and 4.
About the RFC patch set:
http://thread.gmane.org/gmane
The argument of dev_err() in usb_gadget_map_request() should be dev
instead of &gadget->dev.
Fixes: 7ace8fc ("usb: gadget: udc: core: Fix argument of dma_map_single for
IOMMU")
Cc: # v4.3+
Signed-off-by: Yoshihiro Shimoda
---
drivers/usb/gadget/udc/udc-core.c | 2 +-
1 file changed, 1 insertio
If the following environment, the first argument of DMA API should
be set to a DMAC's device structure, not a udc controller's one.
- A udc controller needs an external DMAC device (like a DMA Engine).
- The external DMAC enables IOMMU.
So, this patch add usb_gadget_{un}map_request_by_dev() API
The previous code could use the first USB-DMAC with IPMMU if iommus
property was set into this device node. However, in this case, it
could not control the second USB-DMAC with IPMMU because a parameter
of IPMMU (micro-TLB id) is different with each USB-DMAC.
So, this patch uses the usb_gadget_{un
Since usbhsf_dma_{un}map() will use the "fifo" data in the near future,
this patch changes function call orfer in usbhsf_dma_prepare_push().
Signed-off-by: Yoshihiro Shimoda
---
drivers/usb/renesas_usbhs/fifo.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/driv
Since usbhsg_dma_map_ctrl() needs DMA device structure in the near future,
this patch changes arguments of dma_map_ctrl() to give such data.
(This patch is only change the argument.)
Signed-off-by: Yoshihiro Shimoda
---
drivers/usb/renesas_usbhs/fifo.c | 4 +++-
drivers/usb/renesas_usbhs/m
Hi,
Ivaylo Dimitrov writes:
> Hi,
>
> 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 warning and then reboot
Hi,
Rajesh Bhagat writes:
>>-Original Message-
>>From: Rajesh Bhagat [mailto:rajesh.bha...@nxp.com]
>>Sent: Monday, March 14, 2016 2:41 PM
>>To: ba...@ti.com
>>Cc: gre...@linuxfoundation.org; linux-usb@vger.kernel.org; linux-
>>ker...@vger.kernel.org; linux-o...@vger.kernel.org; Sriram D
Hi,
Alan Stern writes:
> On Fri, 15 Apr 2016, Felipe Balbi wrote:
>
>> Alan Stern writes:
>> > On Thu, 14 Apr 2016, Felipe Balbi wrote:
>> >
>> >> >> --- a/drivers/usb/storage/scsiglue.c
>> >> >> +++ b/drivers/usb/storage/scsiglue.c
>> >> >> @@ -127,6 +127,11 @@ static int slave_configure(struc
On Tue, Apr 05, 2016 at 05:05:09PM +0300, Roger Quadros wrote:
> This is to prevent missing symbol build error if OTG is
> enabled (built-in) and HCD core (CONFIG_USB) is module.
>
> Signed-off-by: Roger Quadros
Acked-by: Peter Chen
> ---
> drivers/usb/chipidea/otg_fsm.c | 7 +++
> dri
On Tue, Apr 05, 2016 at 05:05:11PM +0300, Roger Quadros wrote:
> Let's use CONFIG_USB_OTG as a single config option to enable
> USB OTG and the OTG FSM. This makes things a lot less confusing.
>
> Update all users of CONFIG_USB_OTG_FSM to CONFIG_USB_OTG.
>
> Signed-off-by: Roger Quadros
> ---
>
Some usb module soc implementations can support usb charger type
detection, which can be used by usb charger framework to control
the charging current. user can define the charge detection api of the
platform data if want to enable it.
There are 2 api and one flag used for it, if the usb hardware c
Some imx usb charger dectection need software implement the whole process,
during which, pull up&down DP line via usb core is required.
Signed-off-by: Li Jun
---
drivers/usb/chipidea/ci_hdrc_imx.c | 43 ++
drivers/usb/chipidea/ci_hdrc_imx.h | 3 +++
drivers/u
Some usb module implementations has functionality of detect usb charger
type, it can be used by usb charger framework to report max current drawn
from charger in different situations.
Signed-off-by: Li Jun
---
drivers/usb/chipidea/udc.c | 40
include/li
Set this property if your usb module has usb charger detect function
and you want to use it.
Signed-off-by: Li Jun
---
Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt
b/Documentat
Add imx7d usbmisc compatible string.
Signed-off-by: Li Jun
---
drivers/usb/chipidea/usbmisc_imx.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/chipidea/usbmisc_imx.c
b/drivers/usb/chipidea/usbmisc_imx.c
index 3d70712..daa7c02 100644
--- a/drivers/usb/chipidea/usbmisc_imx.
Adds imx7d usb charger detection implementation, which needs pull up
DP line before do secondary detection and pull down DP afterwards.
Signed-off-by: Li Jun
---
drivers/usb/chipidea/ci_hdrc_imx.c | 3 +-
drivers/usb/chipidea/usbmisc_imx.c | 157 +
2 files c
Hi,
Pavel Machek writes:
>> >>> +#define DEFAULT_SDP_CUR_LIMIT(500 - DEFAULT_CUR_PROTECT)
>> >>
>> >> According to the spec we should always be talking about unit loads (1
>> >> unit load is 100mA for HS/FS/LS and 150mA for SS). Also, this will not
>> >> work for SS capable ports and SS
Hi,
Pavel Machek writes:
> Hi!
>
>> > It's your HW :-) You tell me if it's really necessary. But, hey, if you
>> > get enumerated @500mA, this is the host telling you it _CAN_ give you
>> > 500mA. In that case, why wouldn't you ?
>
> Dunno, perhaps not to drain battery in host too quickly?
> Or
Hi Li,
[auto build test ERROR on peter.chen-usb/ci-for-usb-next]
[also build test ERROR on v4.6-rc4 next-20160418]
[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/Li-Jun/usb-chipidea-Add-usb
Hi Li,
[auto build test ERROR on peter.chen-usb/ci-for-usb-next]
[also build test ERROR on v4.6-rc4 next-20160418]
[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/Li-Jun/usb-chipidea-Add-usb
Hi
> -Original Message-
> From: Baolin Wang [mailto:baolin.w...@linaro.org]
> Sent: Monday, April 11, 2016 7:15 PM
> To: Jun Li
> Cc: ba...@kernel.org; gre...@linuxfoundation.org; s...@kernel.org;
> dbarysh...@gmail.com; dw...@infradead.org; peter.c...@freescale.com;
> st...@rowland.harva
Hi Li,
[auto build test WARNING on peter.chen-usb/ci-for-usb-next]
[also build test WARNING on next-20160418]
[cannot apply to v4.6-rc4]
[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/Li-Jun
Hi Li,
[auto build test ERROR on peter.chen-usb/ci-for-usb-next]
[also build test ERROR on next-20160418]
[cannot apply to v4.6-rc4]
[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/Li-Jun/usb
Hi Li,
[auto build test ERROR on peter.chen-usb/ci-for-usb-next]
[also build test ERROR on next-20160418]
[cannot apply to v4.6-rc4]
[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/Li-Jun/usb
On Mon, 2016-04-18 at 03:53 +0100, Alexey Klimov wrote:
> This patch creates new driver that supports StreamLabs usb watchdog
> device. This device plugs into 9-pin usb header and connects to
> reset pin and reset button on common PC.
>
> USB commands used to communicate with device were reverse
>
Hi Jun,
On 18 April 2016 at 16:27, Jun Li wrote:
>> >>
>> >> But another issue is some users may need to get the charger type from
>> >> power supply by "power_supply_get_property()" function, we need to
>> >> integrate with the power supply things in the usb charger framework,
>> >> not user to
Hello Peter,
I tested this on a Colibri Vybrid VF61 module with the patches applied
on top of for-next branch.
root@colibri-vf:~# uname -a
Linux colibri-vf 4.6.0-rc1-00044-gc76529e-dirty #120 Mon Apr 18 13:46:34 IST
2016 armv7l GNU/Linux
Host and client mode work only on boot up. Trying to chan
Hi Pavel,
On 04/15/2016 01:53 PM, Pavel Machek wrote:
Hi!
How about implementing patterns as a specific typer of triggers?
Let's say we have ledtrig-rgb-pattern:
Well, we'd need ledtrig-rgb-pattern-1, ledtrig-rgb-pattern-2, ... , as we
can have more than one rgb led. But yes.
Triggers can
Hi Michał,
W dniu 07.04.2016 o 18:40, Michal Nazarewicz pisze:
On Thu, 7 Apr 2016, Michal Nazarewicz wrote:
This makes me suspect it’s not possible to link a function instance to
the same configuration twice, but now that I think about it, I’m not
quite sure what would happen if one did:
Coccinelle caught this instance of us kfree()ing
devm-allocated memory. The solution is just to not
do anything in our gadget_release.
Signed-off-by: Felipe Balbi
---
drivers/usb/gadget/udc/pch_udc.c | 14 +-
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git a/drivers/usb/g
this helper will be used, initially, to dump space
of different queues and fifos in dwc3 to
debugfs. Later, it'll be used to issue remote wakeup
when we want to start a transfer and there's
something in a TX FIFO.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.c | 14 ++
drive
This helper will be used later to convert trb type
into a human-readable string for debugfs.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
index c3ea4270bf33..bbbd1789596e 100644
--- a
There's a bunch of information in the debug register
set from dwc3 which is useful in some debugging
scenarios. Let's dump them out in endpoint-specific
directories and designated files.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/debugfs.c | 302
Hi,
Here's v5 of the 2048 sector limit patch series.
Changes since v4:
- Respect possible TAPE device types quirks
Changes since v3:
- Respect USB_FL_MAX_SECTORS* if they are set for USB3 devices
Changes since v2:
- Add a patch fixing multi-line comment style
- s
USB3 devices, because they are much newer, have much
less chance of having issues with larger transfers.
We still keep a limit because anything above 2048
sectors really rendered negligible speed
improvements, so we will simply ignore
that. Transferring 1MiB should already give us
pretty good perf
Just so we have some sort of documentation as to why
we limit our Mass Storage transfers to 240 sectors,
let's update the comment to make clearer that
devices were found that would choke with larger
transfers.
While at that, also make sure to clarify that other
operating systems have similar, albe
No functional changes here, just making sure our
storage driver uses a consistent multi-line comment
style.
Signed-off-by: Felipe Balbi
---
drivers/usb/storage/alauda.c | 22 ++-
drivers/usb/storage/cypress_atacb.c| 34 ++--
drivers/usb/storage/datafab.c | 22 ++-
drive
Hi!
> >> >>> +#define DEFAULT_SDP_CUR_LIMIT(500 - DEFAULT_CUR_PROTECT)
> >> >>
> >> >> According to the spec we should always be talking about unit loads (1
> >> >> unit load is 100mA for HS/FS/LS and 150mA for SS). Also, this will not
> >> >> work for SS capable ports and SS gadgets (we h
Hi,
Pavel Machek writes:
>> > Very often, you want to charge using 1.8A from an old desktop PC.
>>
>> if that old desktop's port is not a charging port, you shouldn't be
>> allowed to do that. Not ever.
>
> Yes, Felipe just decided that I should not be able to charge my N900
> in useful way.
y
Hi!
> >> > a) you are connected to a dedicated charger
> >> >
> >> > In this case, you can get up to 2000mA depending on the charger.
> >> >
> >> > If $this charger can give you or not 2000mA is not detectable,
> >> > so what do charging ICs do ? They slowly increase the at
On Mon 2016-04-18 13:30:54, Felipe Balbi wrote:
>
> Hi,
>
> Pavel Machek writes:
> >> > Very often, you want to charge using 1.8A from an old desktop PC.
> >>
> >> if that old desktop's port is not a charging port, you shouldn't be
> >> allowed to do that. Not ever.
> >
> > Yes, Felipe just dec
Hi,
Pavel Machek writes:
> On Mon 2016-04-18 13:30:54, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Pavel Machek writes:
>> >> > Very often, you want to charge using 1.8A from an old desktop PC.
>> >>
>> >> if that old desktop's port is not a charging port, you shouldn't be
>> >> allowed to do that.
Hi,
Felipe Balbi writes:
>> But cellphone user knows what he connected his charger to, and that's
>> why it is useful to be able to lower the current. Even when you said
>> "less is just stupid" I demonstrated it is not, at least in case when
and btw, you haven't demonstrated anything. You mere
Hi!
> >> manually ??? Hell no! Charger IC should be able to do this no
> >> problem. I would be surprised if there's any charger IC out there which
> >> blindly connects a 1.8A load from the start. What these ICs do is that
> >> they slowly increment the load and check voltage level. They'll conti
I am Capt. Lawrence Tyman, an officer in US Army,and also a West Point
Graduate, serving in the Military with the 82nd Air Borne Division
Peace keeping force deployed from Afganistan to Syria.
We were moved to Syria from Iraq as the last batch just left,and i
really need your help in assisting me
On Tue, Mar 15, 2016 at 10:01:25AM +0100, Linus Walleij wrote:
> On Fri, Mar 4, 2016 at 5:19 PM, Thierry Reding
> wrote:
>
> > From: Thierry Reding
> >
> > This is an old version of the binding that isn't flexible enough to
> > describe all aspects of the XUSB pad controller. Specifically with
On Mon 2016-04-18 13:55:17, Felipe Balbi wrote:
>
> Hi,
>
> Felipe Balbi writes:
> >> But cellphone user knows what he connected his charger to, and that's
> >> why it is useful to be able to lower the current. Even when you said
> >> "less is just stupid" I demonstrated it is not, at least in c
Hi,
Pavel Machek writes:
>> >> > a) you are connected to a dedicated charger
>> >> >
>> >> > In this case, you can get up to 2000mA depending on the charger.
>> >> >
>> >> > If $this charger can give you or not 2000mA is not detectable,
>> >> > so what do charging ICs do
From: Pavel Machek
> Sent: 18 April 2016 11:40
...
> > >> > Actually, less is not stupid. Charging li-ion battery from li-ion
> > >> > battery might
> > >> > be stupid. Imagine I'm on train, with device like N900 (50% battery)
> > >> > and power bank
> > >> > (3Ah). I'm actively using the device.
Hi!
On Mon 2016-04-18 10:59:23, David Laight wrote:
> From: Pavel Machek
> > Sent: 18 April 2016 11:40
> ...
> > > >> > Actually, less is not stupid. Charging li-ion battery from li-ion
> > > >> > battery might
> > > >> > be stupid. Imagine I'm on train, with device like N900 (50% battery)
> > >
On Mon, Apr 18, 2016 at 1:12 PM, Thierry Reding
wrote:
> On Tue, Mar 15, 2016 at 10:01:25AM +0100, Linus Walleij wrote:
>> On Fri, Mar 4, 2016 at 5:19 PM, Thierry Reding
>> wrote:
>>
>> > From: Thierry Reding
>> >
>> > This is an old version of the binding that isn't flexible enough to
>> > des
On Tue, Mar 15, 2016 at 10:01:25AM +0100, Linus Walleij wrote:
> On Fri, Mar 4, 2016 at 5:19 PM, Thierry Reding
> wrote:
>
> > From: Thierry Reding
> >
> > This is an old version of the binding that isn't flexible enough to
> > describe all aspects of the XUSB pad controller. Specifically with
On Fri, Mar 04, 2016 at 05:19:34PM +0100, Thierry Reding wrote:
> From: Thierry Reding
>
> Add a new driver for the XUSB pad controller found on NVIDIA Tegra SoCs.
> This hardware block used to be exposed as a pin controller, but it turns
> out that this isn't a good fit. The new driver and DT bi
Hi,
Pavel Machek writes:
> On Mon 2016-04-18 13:55:17, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Felipe Balbi writes:
>> >> But cellphone user knows what he connected his charger to, and that's
>> >> why it is useful to be able to lower the current. Even when you said
>> >> "less is just stupid" I
On Wed, Apr 06, 2016 at 07:08:24PM +0200, Thierry Reding wrote:
[...]
> I attached what I came up with. It extends the OF PHY provider registry
> by allowing an additional node to be specified that if specified will
> serve as the parent for the child lookup (and hence overrides the
> default node
Hi,
Pavel Machek writes:
>> >> manually ??? Hell no! Charger IC should be able to do this no
>> >> problem. I would be surprised if there's any charger IC out there which
>> >> blindly connects a 1.8A load from the start. What these ICs do is that
>> >> they slowly increment the load and check v
The Link ECU is an aftermarket ECU computer for vehicles that provides full
tuning abilities as well as datalogging and displaying capabilities via the USB
to Serial adapter built into the device.
Signed-off-by: Mike Manning
---
drivers/usb/serial/cp210x.c |2 ++
1 file changed, 2 inserti
On Mon 2016-04-18 14:42:58, Felipe Balbi wrote:
>
> Hi,
>
> Pavel Machek writes:
> > On Mon 2016-04-18 13:55:17, Felipe Balbi wrote:
> >>
> >> Hi,
> >>
> >> Felipe Balbi writes:
> >> >> But cellphone user knows what he connected his charger to, and that's
> >> >> why it is useful to be able t
Hi!
> > Of course, we may do something sensible by default. But manual
> > controls should still be present. You called them "stupid" but they
> > are not.
> >
> > Note that just because you detected wall charger does not even mean
> > you are connected to wall charger. See the link below.
>
> th
Hi,
Pavel Machek writes:
>> > Of course, we may do something sensible by default. But manual
>> > controls should still be present. You called them "stupid" but they
>> > are not.
>> >
>> > Note that just because you detected wall charger does not even mean
>> > you are connected to wall charger
Hi,
Pavel Machek writes:
>> Pavel Machek writes:
>> > On Mon 2016-04-18 13:55:17, Felipe Balbi wrote:
>> >>
>> >> Hi,
>> >>
>> >> Felipe Balbi writes:
>> >> >> But cellphone user knows what he connected his charger to, and that's
>> >> >> why it is useful to be able to lower the current. Eve
Hello.
On 4/18/2016 1:09 PM, Felipe Balbi wrote:
Just so we have some sort of documentation as to why
we limit our Mass Storage transfers to 240 sectors,
let's update the comment to make clearer that
devices were found that would choke with larger
transfers.
While at that, also make sure to cl
On 04/18/2016 01:32 AM, Oliver Neukum wrote:
On Mon, 2016-04-18 at 03:53 +0100, Alexey Klimov wrote:
This patch creates new driver that supports StreamLabs usb watchdog
device. This device plugs into 9-pin usb header and connects to
reset pin and reset button on common PC.
USB commands used to
On Mon, 18 Apr 2016, Felipe Balbi wrote:
> Hi,
>
> Here's v5 of the 2048 sector limit patch series.
>
> Changes since v4:
> - Respect possible TAPE device types quirks
>
> Changes since v3:
> - Respect USB_FL_MAX_SECTORS* if they are set for USB3 devices
>
> Changes since v2:
>
On Mon, 18 Apr 2016, Peter Chen wrote:
> On Wed, Apr 06, 2016 at 09:32:22AM +0300, Roger Quadros wrote:
> > On 06/04/16 09:09, Felipe Balbi wrote:
> > >
> > > Hi,
> > >
> > > Roger Quadros writes:
> > >> diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c
> > >> index 2ca2cef..6b1930d
On Mon, 2016-04-18 at 06:57 -0700, Guenter Roeck wrote:
> On 04/18/2016 01:32 AM, Oliver Neukum wrote:
> > On Mon, 2016-04-18 at 03:53 +0100, Alexey Klimov wrote:
> >> This patch creates new driver that supports StreamLabs usb watchdog
> >> device. This device plugs into 9-pin usb header and connec
On Fri, 15 Apr 2016, Matthew Giassa wrote:
> Good afternoon Alan,
>
> Attached is the requested usbmon output. I started the camera, had a lot
> of config read/write calls complete, and was able to eventually get one
> frame of image data to be saved and rendered.
Obviously something is going on
This reverts commit 2035772010db634ec8566b658fb1cd87ec47ac77.
Commit 20357720 claims throughput improvement for MSC/UVC, but I
don't see much improvement. Following are the MSC measurement using
dd on AM335x GP EVM.
with BCD_BH:read: 14.9MB/s, write: 20.9MB/s
without BCD_BH: read: 15.2MB/s, w
Hi Greg,
Here are a couple fixes for musb for v4.6-rc5.
Tal's patch fixes a musb teardown bug which is uncovered by a g_zero
change in v4.3. HCD_BH flag does not bring any visible benefit but breaks
a few cases.
Please let me know if any change is needed.
Thanks,
-Bin.
Bin Liu (1):
Revert "u
From: Tal Shorer
Some functions, such as f_sourcesink, rely on an endpoint's desc
field during their requests' complete() callback, so clear it only
_after_ nuking all requests to avoid NULL pointer dereference.
Signed-off-by: Tal Shorer
Signed-off-by: Bin Liu
---
drivers/usb/musb/musb_gadget
On Mon, Apr 18, 2016 at 04:08:38PM +0200, Oliver Neukum wrote:
> On Mon, 2016-04-18 at 06:57 -0700, Guenter Roeck wrote:
> > On 04/18/2016 01:32 AM, Oliver Neukum wrote:
> > > On Mon, 2016-04-18 at 03:53 +0100, Alexey Klimov wrote:
> > >> This patch creates new driver that supports StreamLabs usb w
On Sun, Apr 10, 2016 at 04:35:04PM +0300, Jasem Mutlaq wrote:
> Adding VID:PID for Straizona Focusers to cp210x driver.
>
> Signed-off-by: Jasem Mutlaq
Thanks for the patch.
Try running your patch through checkpatch.pl before submitting. It would
have let you know that the patch has some white-
On Mon, Apr 18, 2016 at 03:53:36AM +0100, Alexey Klimov wrote:
> This patch creates new driver that supports StreamLabs usb watchdog
> device. This device plugs into 9-pin usb header and connects to
> reset pin and reset button on common PC.
>
> USB commands used to communicate with device were re
Hi, how are you? My name is J Eric Denials, External Financial Auditor at
Lloyds Banking Group plc., London. It is a pleasure to contact you at this time
through this medium. I have a cool and legitimate deal to do with you as you're
a foreigner, it will be mutually beneficial to both. If you’re
Add a scrollback buffers for each VGA console. The benefit is that
the scrollback history is not flushed when switching between consoles
but is persistent.
The buffers are allocated on demand when a new console is opened.
This breaks tools like clear_console that rely on flushing the
scrollback hi
Tools like clear_console rely on the fact that scrollback history is
flushed when switching back and forth between consoles.
Persistent scrollback buffers for each console breaks this, so this
patch adds a ioctl() callf for flushing the scrollback history.
Signed-off-by: Manuel Schölling
---
dri
Another attempt to add persistent scrollback buffers for all VGA consoles,
so the buffer is not flushed when swithing back and forth between consoles.
Note that breaks tools like bash's clear_console and thus might have
security implications:
clear_console relies on this 'anti-feature' of the kern
Another attempt to add persistent scrollback buffers for all VGA consoles,
so the buffer is not flushed when swithing back and forth between consoles.
Note that breaks tools like bash's clear_console and thus might have
security implications:
clear_console relies on this 'anti-feature' of the kern
Hi Manuel,
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on v4.6-rc4 next-20160418]
[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/Manuel-Sch-lling/Persistent-scrollback
Hi, how are you? My name is J Eric Denials, External Financial Auditor at
Lloyds Banking Group plc., London. It is a pleasure to contact you at this time
through this medium. I have a cool and legitimate deal to do with you as you're
a foreigner, it will be mutually beneficial to both. If you’re
tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git next
head: 761aa987a847e0e8b9a8d806f1be82217b88b0d3
commit: ff96650d99902fd63d4511e6d9047e34e6aa37f2 [26/45] usb: dwc3: get rid of
DWC3_TRB_MASK
config: i386-randconfig-r0-201616 (attached as .config)
reproduce:
git ch
* Manuel Schölling , 2016-04-18, 21:56:
To offer a way for userland tools to flush the buffer my second patch
adds a ioctl call for that.
In f8df13e0a901fe55631fed66562369b4dba40f8b, the escape sequence \e[3J
was added, which erases the whole display including the scroll-back
buffer. So the n
Hi,
On 04/12/2016 09:33 AM, Felipe Balbi wrote:
Hi,
Kirill Dronov writes:
Hi Felipe,
On 04/07/2016 08:10 AM, Felipe Balbi wrote:
Hi,
Kirill Dronov writes:
I'm working on USB device bringup on Intel E3800 – based board. DWC3
core configured as DRD in device mode. The only connected device p
Hi,
I recently bought an MCS7715 USB-attached parallel port,[1] but there
seem to be a couple of problems using it with Linux:
1. The lp, parport, and parport_pc kernel modules are not loaded when
the device is plugged in.
2. After manually loading the kernel modules, /dev/lp0 is not deleted
when
On Mon, Apr 18, 2016 at 06:11:51PM -0600, Alex Henrie wrote:
> Hi,
>
> I recently bought an MCS7715 USB-attached parallel port,[1] but there
> seem to be a couple of problems using it with Linux:
>
> 1. The lp, parport, and parport_pc kernel modules are not loaded when
> the device is plugged in.
On Mon, Apr 18, 2016 at 10:11:29AM -0400, Alan Stern wrote:
> On Mon, 18 Apr 2016, Peter Chen wrote:
>
> > On Wed, Apr 06, 2016 at 09:32:22AM +0300, Roger Quadros wrote:
> > > On 06/04/16 09:09, Felipe Balbi wrote:
> > > >
> > > > Hi,
> > > >
> > > > Roger Quadros writes:
> > > >> diff --git a/
On Mon, Apr 18, 2016 at 02:36:06PM +0530, maitysancha...@gmail.com wrote:
> Hello Peter,
>
> I tested this on a Colibri Vybrid VF61 module with the patches applied
> on top of for-next branch.
>
> root@colibri-vf:~# uname -a
> Linux colibri-vf 4.6.0-rc1-00044-gc76529e-dirty #120 Mon Apr 18 13:46:
95 matches
Mail list logo
