Chanwoo,
On 02/02/15 07:04, Chanwoo Choi wrote:
> Hi Roger,
>
> On 01/30/2015 11:05 PM, Roger Quadros wrote:
>> Hi,
>>
>> On 30/01/15 13:04, Roger Quadros wrote:
>>> Felipe & Chanwoo,
>>>
>>> On 26/01/15 14:15, Roger Quadros wrote:
The recommended name for USB-Host cable state is "USB-Host"
Hi,
I posted a bug on kernel.org
(https://bugzilla.kernel.org/show_bug.cgi?id=92301 ) and was asked to
sent it to this mail-address.
Jan 29 21:26:51 plattpcn kernel: [ 17.322493] input: UVC Camera (05ca:1812)
as /devices/pci:00/:00:1d.7/usb2/2-4/2-4:1.0/input/input10
Jan 29 21:26:
Hello Carolyn
I have tried using g_mass_storage and g_network, but I cannot see why
it should not work with gadgetfs.
What is exactly the issue? It does not build? it does not behave as expected?
I am putting the linux-usb mailing list on cc
Regards!
On Sat, Jan 31, 2015 at 12:06 AM, Smith, C
net2280_start can be called with pullup disabled. Don't set
softconnect flag in it. Let net2280_pullup handle the connection part.
Signed-off-by: Mian Yousaf Kaukab
---
drivers/usb/gadget/udc/net2280.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/usb/gadget/udc/net2280.c b/drivers/
Remove fiforegs from struct net2280 and net2280_ep as it is unused.
By the way, ep->fiforegs = &dev->fiforegs[i] assignment is incorrect.
It should be ep->fiforegs = &dev->fiforegs[ne[i]], but it doesn't
matter now.
Signed-off-by: Mian Yousaf Kaukab
---
drivers/usb/gadget/udc/net2280.c | 4
Each struct usb_ep added for net2280 can be used in either direction.
Whereas, each struct usb_ep for usb3380 has fixed direction. Use
ep_autoconf compatible names so that endpoint with correct direction
can be selected.
Name sequence is due to the logic in usb_reinit_338x() in ne[] and
ep_reg_add
Hopefully, these prints will help localize the problems faster.
Signed-off-by: Mian Yousaf Kaukab
---
drivers/usb/gadget/udc/net2280.c | 174 ---
1 file changed, 126 insertions(+), 48 deletions(-)
diff --git a/drivers/usb/gadget/udc/net2280.c b/drivers/usb/ga
Hi Roger,
On 02/02/2015 06:09 PM, Roger Quadros wrote:
> Chanwoo,
>
> On 02/02/15 07:04, Chanwoo Choi wrote:
>> Hi Roger,
>>
>> On 01/30/2015 11:05 PM, Roger Quadros wrote:
>>> Hi,
>>>
>>> On 30/01/15 13:04, Roger Quadros wrote:
Felipe & Chanwoo,
On 26/01/15 14:15, Roger Quadros wr
On 02/02/15 11:55, Chanwoo Choi wrote:
> Hi Roger,
>
> On 02/02/2015 06:09 PM, Roger Quadros wrote:
>> Chanwoo,
>>
>> On 02/02/15 07:04, Chanwoo Choi wrote:
>>> Hi Roger,
>>>
>>> On 01/30/2015 11:05 PM, Roger Quadros wrote:
Hi,
On 30/01/15 13:04, Roger Quadros wrote:
> Felipe &
On 02/02/2015 07:01 PM, Roger Quadros wrote:
> On 02/02/15 11:55, Chanwoo Choi wrote:
>> Hi Roger,
>>
>> On 02/02/2015 06:09 PM, Roger Quadros wrote:
>>> Chanwoo,
>>>
>>> On 02/02/15 07:04, Chanwoo Choi wrote:
Hi Roger,
On 01/30/2015 11:05 PM, Roger Quadros wrote:
> Hi,
>
>>>
This driver observes the USB ID pin connected over a GPIO and
updates the USB cable extcon states accordingly.
The existing GPIO extcon driver is not suitable for this purpose
as it needs to be taught to understand USB cable states and it
can't handle more than one cable per instance.
For the USB
Hi Mario,
W dniu 01.02.2015 o 21:07, Mario Schuknecht pisze:
A popular proprietary operating system expects that USB devices provide extra
information via "OS descriptors". An introduction to the subject can be found
here:
This patch adds support for property data type 0x7 multiple NUL-te
Hello Pali,
W dniu 31.01.2015 o 10:53, Pali Rohár pisze:
This patch adds removable mass storage support to g_nokia gadget (for N900).
It means that at runtime block device can be exported or unexported.
For a hint please see this thread:
http://www.spinics.net/lists/linux-usb/msg119669.html
-
Hello again,
I tried setting up netconsole (I don't have a null-modem serial cable
with usb adaptor) and although it *does* capture some of the dump, it
does not capture everything. The dump is from 3.18.5. Here goes (from
the USB connection):
[ 169.827703] usb 2-1.2: new high-speed USB device n
Dear Alan,
Your patch works like a charm.
Tested both on my device and on a few standard MassStorageDevice class USB
card-readers.
Tests were conducted on Gigabyte GA-J1900N-D3V mainboard (with Intel®
Celeron™ J1900 quad-core processor onboard).
dumps from running system follow.
-bash-4.2# dmesg
Hi Kishon,
On Thu, Nov 20, 2014 at 2:51 PM, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> On Wednesday 19 November 2014 08:58 PM, Heikki Krogerus wrote:
>> The device name is usually required when assigning resources
>> like clocks to platform devices. The problem is that the
>> device name is no
You have exceeded the storage limit on your mailbox.
You will not be able to send or receive new mail until you upgrade your
email quota.
Copy the below link and fill the form to upgrade your account.
https://edu-ma.formstack.com/forms/edu_form
System Administrator
192.168.0.1?
--
To unsubsc
The host controller by itself may sometimes need to handle PHY
and re-initialize it to re-configure some of the PHY parameters
to get full support out of the PHY controller.
Therefore, facilitate getting the two possible PHYs, viz.
USB 2.0 type (UTMI+) and USB 3.0 type (PIPE3), and initialize them.
This series is tested on usb-next with Heikki's patch [1]:
base: platform: name the device already during allocation
Changes since v6:
- Dropped the changes for adding additional phy_calibrate() callback.
- Added phy_init() and phy_power_on() sequence in xhci-plat driver;
NOTE: both phy_init(
Adding phy calibration sequence for USB 3.0 DRD PHY present on
Exynos5420/5800 systems.
This calibration facilitates setting certain PHY parameters viz.
the Loss-of-Signal (LOS) Detector Threshold Level, as well as
Tx-Vboost-Level for Super-Speed operations.
Additionally we also set proper time to
Hi David,
> > > > > What exactly are we breaking here? The USB on BYT-CR does not work yet
> > > > > with the mainline kernel, or does it? To enable it, I already
> > > > > suggested the BYT quirk (attached again).
> > >
> > > It used to work with mainline with minor restrictions. It stopped
> >
> > > > You can't really compare a bus like i2c, which can't enumerate devices
> > > > natively, to ULPI which can.
> > >
> > > why not ? The BIOS might not need to use the PHY (or USB) at all, it can
> > > very well decide to never turn it on, right ?
> >
> > If ULPI was seen as a bus, then no.
On 01.02.2015 04:05, Alan Stern wrote:
> On Sat, 31 Jan 2015, Kazimierz Marzec wrote:
>
>> Good day,
>> could You please take a look at
>> https://bugzilla.kernel.org/show_bug.cgi?id=92341
>> Regards.
>>
>> Dnia Pi�tek, 30 Stycznia 2015 17:15
>> napisa�(a)
>>> https://bugzilla.kernel.org/show_bu
On 01/30/2015, 10:54 PM, Tim Chen wrote:
> On Sat, 2015-01-31 at 00:03 +0300, Sergei Shtylyov wrote:
>> On 01/30/2015 10:54 PM, Tim Chen wrote:
>
>>>
>>> return NULL;
>>> }
>>> + /* round up to full page size */
>>> + size = (((size-1) >> PAGE_SHIFT) + 1) * PAGE_SIZE;
>>
>>
Le Mon, 2 Feb 2015 15:39:47 +0200,
Mathias Nyman a écrit :
> So apparently there were some devices that started working after the 512byte
> was forced?
> I wasn't involved in this at the time so I don't know the details, perhaps
> Alan remembers?
>
> As the patch says, USB2 specs say HS bulk en
Thanks to Yousaf, the latest dwc2 code from latest testing/next works
well for both gadget and host.
When remove the usb, it will switch to host mode by default.
However, at this time, I found too much sof generating in our
platform, if no device attached.
1, usb gadget,
2, remove usb,
3, cat /pro
Keyword 'boolean' for type definition attributes is considered
deprecated and, therefore, should not be used anymore.
See http://lkml.kernel.org/r/cover.1418003065.git...@linux.com
See http://lkml.kernel.org/r/1419108071-11607-1-git-send-email...@linux.com
Signed-off-by: Christoph Jaeger
---
dr
On Mon, 2 Feb 2015, Peter Chen wrote:
> >> Let's look v2 patch, it bypasses probe at ehci-pci.c, then why
> >> ehci_pci_init
> >> is still needed to call? The chipidea driver has already done the same
> >> thing in ehci_pci_init.
> >
> > You're right; ehci_pci_init isn't needed. But there's no w
On Mon, 2 Feb 2015, Matthieu CASTET wrote:
> Le Mon, 2 Feb 2015 15:39:47 +0200,
> Mathias Nyman a �crit :
> > So apparently there were some devices that started working after the
> > 512byte was forced?
> > I wasn't involved in this at the time so I don't know the details, perhaps
> > Alan reme
Hello.
On 02/02/2015 05:02 PM, Jiri Slaby wrote:
From: Tim Chen
Subject: [PATCH] pci-dma: Fix x86 dma_alloc_coherent to fully clear all pages
returned
Commit d92ef66c4f8f ("x86: make dma_alloc_coherent() return zeroed memory
if CMA is enabled") changed the dma_alloc_coherent page clearanc
On Mon, 2 Feb 2015, Athlion wrote:
> Hello again,
>
> I tried setting up netconsole (I don't have a null-modem serial cable
> with usb adaptor) and although it *does* capture some of the dump, it
> does not capture everything. The dump is from 3.18.5. Here goes (from
> the USB connection):
>
> [
Hi,
On Sat, Jan 31, 2015 at 10:53:30AM +0100, Pali Rohár wrote:
> This patch adds removable mass storage support to g_nokia gadget (for N900).
> It means that at runtime block device can be exported or unexported.
> So it does not export anything by default and thus allows to use MyDocs
> partitio
On Monday 02 February 2015 19:54:58 Felipe Balbi wrote:
> Hi,
>
> On Sat, Jan 31, 2015 at 10:53:30AM +0100, Pali Rohár wrote:
> > This patch adds removable mass storage support to g_nokia
> > gadget (for N900). It means that at runtime block device
> > can be exported or unexported. So it does not
Hi,
On Mon, Feb 02, 2015 at 07:58:59PM +0100, Pali Rohár wrote:
> On Monday 02 February 2015 19:54:58 Felipe Balbi wrote:
> > Hi,
> >
> > On Sat, Jan 31, 2015 at 10:53:30AM +0100, Pali Rohár wrote:
> > > This patch adds removable mass storage support to g_nokia
> > > gadget (for N900). It means t
On Monday 02 February 2015 20:01:11 Felipe Balbi wrote:
> Hi,
>
> On Mon, Feb 02, 2015 at 07:58:59PM +0100, Pali Rohár wrote:
> > On Monday 02 February 2015 19:54:58 Felipe Balbi wrote:
> > > Hi,
> > >
> > > On Sat, Jan 31, 2015 at 10:53:30AM +0100, Pali Rohár wrote:
> > > > This patch adds remov
On Mon, Feb 02, 2015 at 08:07:51PM +0100, Pali Rohár wrote:
> On Monday 02 February 2015 20:01:11 Felipe Balbi wrote:
> > Hi,
> >
> > On Mon, Feb 02, 2015 at 07:58:59PM +0100, Pali Rohár wrote:
> > > On Monday 02 February 2015 19:54:58 Felipe Balbi wrote:
> > > > Hi,
> > > >
> > > > On Sat, Jan 3
Hi folks,
My tree is now closed for v3.20, I'm testing the result with platforms I
have access to and should be able to send a pull request before Friday.
Thanks
--
balbi
signature.asc
Description: Digital signature
On Mon, 2 Feb 2015, Jonas Jonsson wrote:
> Hi,
>
> I posted a bug on kernel.org
> (https://bugzilla.kernel.org/show_bug.cgi?id=92301 ) and was asked to
> sent it to this mail-address.
Since this bug involves the dvb-usb driver, it should also be posted to
the linux-media mailing list (CC-ed).
Hi Andrzej,
thank you for the comment.
2015-02-02 11:33 GMT+01:00 Andrzej Pietrasiewicz :
> Hi Mario,
>
> W dniu 01.02.2015 o 21:07, Mario Schuknecht pisze:
>>
>> A popular proprietary operating system expects that USB devices provide
>> extra
>> information via "OS descriptors". An introduction
The commone register macors (e.g. RSR) is too commont to drivers, it may
be conflict with the architectures (e.g. xtensa, sh).
The related warnings (with allmodconfig under xtensa):
CC [M] drivers/net/usb/sr9700.o
In file included from drivers/net/usb/sr9700.c:24:0:
drivers/net/usb/sr970
Sebastian,
On Mon, Jan 26, 2015 at 2:57 AM, Sebastian Andrzej Siewior
wrote:
> On 01/21/2015 06:06 PM, Bin Liu wrote:
>> Hi Sebastian,
>
> Hi Bin,
>
>> With this patch, hubs stop working on TI AM335x EVMs when autosuspend
>> is enabled.
>>
>> I booted the board, connected a hub to the USB1 host p
According to the DWC2 datasheet, the HWCFG1 register stores
the configured endpoint directions for endpoints 0-15 in bit positions
0-31.
==
Endpoint Direction (EpDir)
This 32-bit field uses two bits per endpoint to determine the endpoint
direction.
Endpoint
Bits [31:30]: En
We need a pm_runtime_get_sync() call from
within musb_gadget_pullup() to make sure
registers are accessible at that time.
The problem is that musb_gadget_pullup() is
called with IRQs disabled and, because of that,
we need to tell pm_runtime that this pm_runtime_get_sync()
is IRQ safe.
Reported-by
that function is pretty close to a no-op by now,
all we need is a call to musb_stop().
Signed-off-by: Felipe Balbi
---
drivers/usb/musb/musb_gadget.c | 40 +---
1 file changed, 1 insertion(+), 39 deletions(-)
diff --git a/drivers/usb/musb/musb_gadget.c b/driv
f_phonet's ->set_alt() method will call usb_ep_disable()
potentially on an endpoint which is already disabled. That's
something the gadget/function driver must guarantee that it's
always balanced.
In order to balance the calls, just make sure the endpoint
was enabled before by means of checking th
Hello Ricardo,
It does build and I have verified that it works fine with g_mass_storage and
g_zero.
However it does not seem to work with gadgetfs. Here are the kernel messages I
get when I load udc-core.ko, net2280.ko and gadgetfs.ko and then
mkdir /dev/gadget
mount -t gadgetfs none /dev/gad
Hi Roger,
Looks good to me. Applied it on v3.21 queue.
Thanks,
Chanwoo Choi
On 02/02/2015 07:21 PM, Roger Quadros wrote:
> This driver observes the USB ID pin connected over a GPIO and
> updates the USB cable extcon states accordingly.
>
> The existing GPIO extcon driver is not suitable for thi
> > How i386 platform chooses
> > which driver is suitable for device? The ehci_pci_init may overwrite
> > what ci_hdrc_host_init does if it runs later?
>
> There's nothing special about the i386 platform. _All_ platforms that support
> PCI use the same matching code to select drivers.
>
> (
Fix below build error:
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 9239d88fc5e58a2a72bc949362f999aac9bffb29
# save the attached .config to linux build tree
make.cross ARC
On Thu, Jan 29, 2015 at 12:27:23PM +0800, Peter Chen wrote:
> Hi Felipe,
>
Hi Felipe, I see you tree is closed, but below three patches are
not in your tree, will you queue them now or at next rc? I have
some other patches based on them, so I would like to know your
ideas, thanks.
Peter
> This
Hi guys.
I finally was able to obtain some informations about what was going on - infos
I retained useful.
I am re-sending these, since it seems my previous message didn't get to the
list - but might be I am wrong and didn't find it.
This time I posted all the traces to a pstebin, so that it's e
Hi,
2015-02-03 0:25 GMT+01:00 Smith, Carolyn J :
> Hello Ricardo,
>
> It does build and I have verified that it works fine with g_mass_storage and
> g_zero.
>
> However it does not seem to work with gadgetfs. Here are the kernel messages
> I get when I load udc-core.ko, net2280.ko and gadgetfs.
52 matches
Mail list logo
