[PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

Currently qw_sign requires UTF-8 character to set, but returns UTF-16 when read. This isn't obvious when simply using cat since the null characters are not visible, but hexdump unveils the true string: # echo MSFT100 > os_desc/qw_sign # hexdump -C os_desc/qw_sign 4d 00 53 00 46 00

[PATCH 2/2] fs: configfs: use hexadecimal values and new line

Other unsigned properties return hexadecimal values, follow this convention when printing b_vendor_code too. Also add newlines to the OS Descriptor support related properties, like other sysfs files use. Signed-off-by: Stefan Agner --- drivers/usb/gadget/configfs.c | 6 +++---

Re: rndis_host random MAC address

Am Freitag, den 14.04.2017, 15:51 +0700 schrieb gentoo: > I have problem with the random MAC address of rndis_host. > > Therefore I have no chance to keep permanent settings on NetworkManager > (like DNS). > > Every time I plug my phone to my computer, it get new MAC address, which > is wrong.

Re: [PATCH 2/9] usbip: vhci-hcd: Add vhci struct

Hi Oliver, > what is the motivation for this change? That is the way XHCI > does it. But why do that when you export something over > a network? Are you ever going to use both VHCIs? I, a usbip client, could use a LowSpeed device and a SuperSpeed device from usbip host/hosts at the same time.

Re: [PATCH] chipidea: Fix issue in reconnecing gadget without insmod/rmmod

On Wed, Apr 12, 2017 at 06:18:20PM +0530, Niranjan Dighe wrote: > > Hi Niranjan, > > > > When working with iAP device, there are two role-switch methods > > - Through OTG FSM, and using sysfs entries under > > /sys/bus/platform/devices/ci_hdrc.0/inputs > > but you may need to patch code to keep

rndis_host random MAC address

I have problem with the random MAC address of rndis_host. Therefore I have no chance to keep permanent settings on NetworkManager (like DNS). Every time I plug my phone to my computer, it get new MAC address, which is wrong. It would be nice, if in case of missing fixed MAC, rndis_host

Re: [PATCH 2/9] usbip: vhci-hcd: Add vhci struct

Am Freitag, den 14.04.2017, 06:34 +0800 schrieb Yuyang Du: > Hi Oliver, > > > > > what is the motivation for this change? That is the way XHCI > > does it. But why do that when you export something over > > a network? Are you ever going to use both VHCIs? > > I, a usbip client, could use a

Re: [PATCH 2/9] usbip: vhci-hcd: Add vhci struct

On Fri, Apr 14, 2017 at 11:29:14AM +0200, Oliver Neukum wrote: > > > what is the motivation for this change? That is the way XHCI > > > does it. But why do that when you export something over > > > a network? Are you ever going to use both VHCIs? > > > > I, a usbip client, could use a LowSpeed

Re: USB Type-C Port Manager API concern

On 04/14/2017 04:57 AM, Guenter Roeck wrote: ... Overall I think there is an assumption in any API that any callback functions provided in a registration call can immediately be called. Otherwise any API would be in trouble. Can you modify your code to not require the port pointer in its

Greetings.

Good Day Dearest. My name is Sarah JOHNSON I am 18 years old, the only daughter of late Mr. Raymond JOHNSON from Burkina Faso, I am contacting you to help me relocate to your country to continue my university education in your country, before my father died he gave me a deposit slip document

Re: rndis_host random MAC address

W dniu 14.04.2017 o 18:32, Oliver Neukum pisze: Am Freitag, den 14.04.2017, 15:51 +0700 schrieb gentoo: I have problem with the random MAC address of rndis_host. Therefore I have no chance to keep permanent settings on NetworkManager (like DNS). Every time I plug my phone to my computer, it

Re: rndis_host random MAC address

Am Freitag, den 14.04.2017, 15:51 +0700 schrieb gentoo: I have problem with the random MAC address of rndis_host. Therefore I have no chance to keep permanent settings on NetworkManager (like DNS). Every time I plug my phone to my computer, it get new MAC address, which is wrong. It would be

[RFC][PATCH 0/3] add EXTCON_CHG_USB_* cables to MSM USB phy

This patchset adds a way for the MSM USB phy to notify a power supply when the charging state changes. It achieves that using the extcon subsystem. The first patch makes sure msm_otg_notify_charger is called after the charger attributes have been set. The second one makes sure that function is

[RFC][PATCH 3/3] usb: phy: msm: use extcon to notify charger

Phy already keeps track of the USB charger mode it is in, that information could be useful to a power supply to let it know how much current it can draw. So in this case when DCP or CDP is set maximum current available is 1500mA, and 100mA when SDP is set. This is a bit peculiar in that this

[RFC][PATCH 2/3] usb: phy: msm: notify charger when power supply is unplugged

With the current code, msm_otg_notify_charger doesn't get called when a power supply identified as a DCP is unplugged. To work around that, update charger info and call the notify function when switching from idle to host. Signed-off-by: Damien Riegel ---

[RFC][PATCH 1/3] usb: phy: msm: notify charger after setting charger info

Move calls to msm_otg_notify_charger after attributes chg_state and chg_type have been set. That way the function can use them and not rely only on the "mA" parameter. Signed-off-by: Damien Riegel --- drivers/usb/phy/phy-msm-usb.c | 6 +++--- 1 file changed,