On Wed, 29 Aug 2018, Klaus Kusche wrote:
> Hello,
>
> On 24/08/2018 19:28, Alan Stern wrote:
> > On Fri, 24 Aug 2018, Klaus Kusche wrote:
> >> On 24/08/2018 17:39, Alan Stern wrote:
> >>> On Fri, 24 Aug 2018, Klaus Kusche wrote:
> On 24/08/2018 16:15, Alan Stern wrote:
> > On Fri, 24
On Thu, 30 Aug 2018, Andrey Konovalov wrote:
> Hi Alan,
>
> I have a few questions about gadgetfs.
>
> According to documentation usb_gadget_driver->setup "queues a response
> to ep0, or returns negative to stall".
>
> Do I understand correctly, that "stall" in this case means "retry the
>
Hi Andy,
> > Latest NVIDIA GPU cards have a Cypress CCGx Type-C controller over I2C
> > interface.
> >
> > This UCSI I2C driver uses I2C bus driver interface for communicating
> > with Type-C controller.
> >
>
> Few comments below.
>
> > +#include
> > +#include
> > +#include
> > +#include
>
Latest NVIDIA GPU card has USB Type-C interface. There is a
Type-C controller which can be accessed over I2C.
This driver adds I2C bus driver to communicate with Type-C controller.
I2C client driver will be part of USB Type-C UCSI driver.
Signed-off-by: Ajay Gupta
---
Changes from v1 -> v2
Latest NVIDIA GPU cards have a Cypress CCGx Type-C controller
over I2C interface.
This UCSI I2C driver uses I2C bus driver interface for communicating
with Type-C controller.
Signed-off-by: Ajay Gupta
---
Changes from v1 -> v2
Fixed identation in drivers/usb/typec/ucsi/Kconfig
Changes
On Wed, Aug 29, 2018 at 05:33:17PM -0700, ajayk...@gmail.com wrote:
> From: Ajay Gupta
Can you add your full name to the gmail address, too? That would make
patch processing a tad easier.
Thanks,
Wolfram
signature.asc
Description: PGP signature
On Thu, 30 Aug 2018, Faisal Mehmood wrote:
> Based on my (limited) understanding if I were to disable udev, the
> userspace should not be able to enumerate/interact with any newly
> connected device since udev handles uevents generated by kernel.
> (right?)
That's not quite right. Yes, udev
Hi Alan,
I have a few questions about gadgetfs.
According to documentation usb_gadget_driver->setup "queues a response
to ep0, or returns negative to stall".
Do I understand correctly, that "stall" in this case means "retry the
same request later" and it's unrelated to the STALL USB packet?
Is
Based on my (limited) understanding if I were to disable udev, the
userspace should not be able to enumerate/interact with any newly
connected device since udev handles uevents generated by kernel.
(right?)
So as a test, I disabled systemd-udevd and then plugged in a flash
drive. I disabled
Hi Andy,
> > Latest NVIDIA GPU card has USB Type-C interface. There is a Type-C
> > controller which can be accessed over I2C.
> >
> > This driver adds I2C bus driver to communicate with Type-C controller.
> > I2C client driver will be part of USB Type-C UCSI driver.
> >
>
> Some small comments
Hello.
FYI. I made a progress on this, but no solution yet.
>The smartphone does use HNP, it is not iPhone Carplay, correct?
At this point, I am trying to see original HNP behavior between two
pocketbeagles.
(After seeing it works, I plan to replace B-device with a phone, and so
customization
On Tue, Aug 28, 2018 at 5:09 PM Alan Stern wrote:
> There is another way: modprobe g_file_storage with appropriate
> parameters.
Yes, but I am using a composite device, with ACM and UMS, and also
g_multi (Ethernet+ACM+UMS) is not a option since my HW does not
support enough endpoints for this
Hello,
I am using USB-UART optical serial converter [1], which is based on
MCP2200.
It is connected to my RaspberryPi and the other side is connected to my
remeha
gas boiller.
My problems starts with this commit:
commit a81cf9799ad7299b03a4dff020d9685f9ac5f3e0
Author: Oliver Neukum
Date:
This reverts commit a81cf9799ad7299b03a4dff020d9685f9ac5f3e0.
The patch causes a regression, which I cannot find the reason for.
So let's revert for now, as a revert hurts only performance.
I was trying to resolve the problem with Oliver but we don't get any
conclusion
for 5 months, so I am now
On Thu, Aug 30, 2018 at 3:35 AM wrote:
>
> From: Ajay Gupta
>
> Latest NVIDIA GPU card has USB Type-C interface. There is a
> Type-C controller which can be accessed over I2C.
>
> This driver adds I2C bus driver to communicate with Type-C controller.
> I2C client driver will be part of USB
On Thu, Aug 30, 2018 at 3:36 AM wrote:
>
> From: Ajay Gupta
>
> Latest NVIDIA GPU cards have a Cypress CCGx Type-C controller
> over I2C interface.
>
> This UCSI I2C driver uses I2C bus driver interface for communicating
> with Type-C controller.
>
Few comments below.
> +#include
> +#include
On 29/08/2018 at 22:01, Rob Herring wrote:
The name is always non-NULL and then is not used anywhere in this function,
so remove it.
Indeed.
Cc: Nicolas Ferre
Acked-by: Nicolas Ferre
Cc: Felipe Balbi
Cc: Greg Kroah-Hartman
Cc: Alexandre Belloni
Cc:
Switch to bitmap_zalloc() to show clearly what we are allocating.
Besides that it returns pointer of bitmap type instead of opaque void *.
Signed-off-by: Andy Shevchenko
---
drivers/usb/wusbcore/wa-rpipe.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git
18 matches
Mail list logo