On 01/25/2017 12:17 PM, Alexandre Bailon wrote:
> A pointer to musb is now present in the dma_controller structure.
> Remove the one present in tusb_omap_dma structure.
the subject line should be: usb: musb: tusb6010_omap: ...
> Signed-off-by: Alexandre Bailon
> ---
> drivers/usb/musb/tusb601
Hi,
Raz Manor writes:
> Got it. Then I'm resending the patch, and looking forward to your replay.
please read Documentation/SubmittingPatches :-)
you need a commit log, a Signed-off-by line, etc etc. Please send a
proper patch otherwise we can't apply it, sorry.
--
balbi
signature.asc
Desc
On Mon, Feb 06, 2017 at 10:14:44AM +0200, Petko Manolov wrote:
> On 17-02-05 01:30:39, Greg KH wrote:
> > On Sat, Feb 04, 2017 at 04:56:03PM +, Ben Hutchings wrote:
> > > Allocating USB buffers on the stack is not portable, and no longer
> > > works on x86_64 (with VMAP_STACK enabled as per def
Hi all,
This is a follow-up for my last power sequence framework patch set [1].
According to Rob Herring and Ulf Hansson's comments[2]. The kinds of
power sequence instances will be added at postcore_initcall, the match
criteria is compatible string first, if the compatible string is not
matched b
We have an well-known problem that the device needs to do some power
sequence before it can be recognized by related host, the typical
example like hard-wired mmc devices and usb devices.
This power sequence is hard to be described at device tree and handled by
related host driver, so we have crea
From: Arnd Bergmann
Set the dma for chipidea from sysdev. This is inherited from its
parent node. Also, do not set dma mask for child as it is not required
now.
Signed-off-by: Arnd Bergmann
Signed-off-by: Sriram Dash
Acked-by: Peter Chen
Signed-off-by: Mathias Nyman
---
drivers/usb/chipidea
Some hard-wired USB devices need to do power sequence to let the
device work normally, the typical power sequence like: enable USB
PHY clock, toggle reset pin, etc. But current Linux USB driver
lacks of such code to do it, it may cause some hard-wired USB devices
works abnormal or can't be recogniz
Add optional properties for power sequence.
Signed-off-by: Peter Chen
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/usb/usb-device.txt | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/usb/usb-device.txt
b/Documentatio
From: Arnd Bergmann
For xhci-hcd platform device, all the DMA parameters are not
configured properly, notably dma ops for dwc3 devices.
The idea here is that you pass in the parent of_node along with
the child device pointer, so it would behave exactly like the
parent already does. The differenc
Set the dma for ehci from sysdev. The sysdev is pointing to device that
is known to the system firmware or hardware.
Cc: Arnd Bergmann
Cc: Sriram Dash
Signed-off-by: Peter Chen
---
drivers/usb/host/ehci-mem.c | 38 +++---
1 file changed, 19 insertions(+), 19 del
From: Arnd Bergmann
For xhci-hcd platform device, all the DMA parameters are not
configured properly, notably dma ops for dwc3 devices. So, set
the dma for xhci from sysdev. sysdev is pointing to device that
is known to the system firmware or hardware.
Signed-off-by: Arnd Bergmann
Signed-off-by
Add binding doc for generic power sequence library.
Signed-off-by: Peter Chen
Acked-by: Philipp Zabel
Acked-by: Rob Herring
---
.../bindings/power/pwrseq/pwrseq-generic.txt | 48 ++
1 file changed, 48 insertions(+)
create mode 100644
Documentation/devicetree/binding
From: Arnd Bergmann
For the dual role ehci fsl driver, sysdev will handle the dma
config.
Signed-off-by: Arnd Bergmann
Signed-off-by: Sriram Dash
Signed-off-by: Mathias Nyman
---
drivers/usb/host/ehci-fsl.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/h
On 17-02-04 16:56:32, Ben Hutchings wrote:
> Allocating USB buffers on the stack is not portable, and no longer
> works on x86_64 (with VMAP_STACK enabled as per default).
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Ben Hutchings
> ---
> drivers/net/usb/rtl8150.c | 34 +
On 17-02-05 01:30:39, Greg KH wrote:
> On Sat, Feb 04, 2017 at 04:56:03PM +, Ben Hutchings wrote:
> > Allocating USB buffers on the stack is not portable, and no longer
> > works on x86_64 (with VMAP_STACK enabled as per default).
>
> It's never worked on other platforms, so these should go to
Due to the reference clock comes from 26M oscillator directly
on mt8173, and it is a fixed-clock in DTS which always turned
on, we ignore it before. But on some platforms, it comes
from PLL, and need be controlled, so here add it, no matter
it is a fixed-clock or not.
Signed-off-by: Chunfeng Yun
Some resources such as regulator, clock usually cause deferred
probe, get them earlier to avoid more ineffective processing.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3_plat.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/drivers/usb/m
add 26M reference clock for ssusb and xhci nodes
Signed-off-by: Chunfeng Yun
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
index 07fd2e
usually, the reference clock comes from 26M oscillator directly,
but some SoCs are not, add it for compatibility.
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c | 22 ++
drivers/usb/host/xhci-mtk.h |1 +
2 files changed, 23 insertions(+)
diff --git a/drive
Due to the reference clock comes from 26M oscillator directly
on mt8173, and it is a fixed-clock in DTS which always turned
on, we ignore it before. But on some platforms, it comes
from PLL, and need be controlled, so here add it, no matter
it is a fixed-clock or not.
Signed-off-by: Chunfeng Yun
usually, the reference clock comes from 26M oscillator directly,
but some SoCs are not, add it for compatibility.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3.h |1 +
drivers/usb/mtu3/mtu3_plat.c | 28 ++--
2 files changed, 27 insertions(+), 2 deletion
On Sat, Feb 04, 2017 at 04:00:24AM +0800, Ken Lin wrote:
> Add new USB IDs for cp2104/5 devices on Bx50v3 boards due to the design change
>
> Signed-off-by: Ken Lin
> ---
> Change in v2:
> Fix the author (From) address doesn't match the SoB issue mentioned in the
> discussion thread
Now applied
Hello again!
Thanks for the advice, but bisecting the whole tree took me quite a
while and I ended up stuck because booting on some bisect states has
led my system to run without some devices, like wireless and sound. So
I tried to bisect the sound/usb/line6 path. It turns out that this
commit is
On Mon, Feb 06, 2017 at 01:01:56PM +0300, Igor Zinovev wrote:
> Hello again!
>
> Thanks for the advice, but bisecting the whole tree took me quite a
> while and I ended up stuck because booting on some bisect states has
> led my system to run without some devices, like wireless and sound. So
> I t
On Mon, 06 Feb 2017 11:18:44 +0100,
Greg KH wrote:
>
> On Mon, Feb 06, 2017 at 01:01:56PM +0300, Igor Zinovev wrote:
> > Hello again!
> >
> > Thanks for the advice, but bisecting the whole tree took me quite a
> > while and I ended up stuck because booting on some bisect states has
> > led my sys
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb.git
pwrseq-lib
head: 06903db00af7968ff4960ab380c45a7788fee1d5
commit: 778d7e6997538601e8ad364188bf007768922bd4 [2/10] power: add power
sequence library
config: x86_64-lkp (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3
On Mon, Feb 6, 2017 at 12:01 PM, Takashi Iwai wrote:
> On Mon, 06 Feb 2017 11:18:44 +0100,
> Greg KH wrote:
>>
>> On Mon, Feb 06, 2017 at 01:01:56PM +0300, Igor Zinovev wrote:
>> > Hello again!
>> >
>> > Thanks for the advice, but bisecting the whole tree took me quite a
>> > while and I ended up
On Mon, 06 Feb 2017 12:04:29 +0100,
Andrej Kruták wrote:
>
> On Mon, Feb 6, 2017 at 12:01 PM, Takashi Iwai wrote:
> > On Mon, 06 Feb 2017 11:18:44 +0100,
> > Greg KH wrote:
> >>
> >> On Mon, Feb 06, 2017 at 01:01:56PM +0300, Igor Zinovev wrote:
> >> > Hello again!
> >> >
> >> > Thanks for the adv
On 02/05/2017 08:42 AM, Greg KH wrote:
> On Fri, Feb 03, 2017 at 11:55:24AM +0100, Richard Leitner wrote:
>> +/**
>> + * ascii2utf16le() - Helper routine for producing UTF-16LE string
>> descriptors
>> + * @s: Null-terminated ASCII (actually ISO-8859-1) string
>> + * @buf: Buffer for UTF-16LE stri
On Mon, Feb 06, 2017 at 12:19:40PM +0100, Richard Leitner wrote:
> On 02/05/2017 08:42 AM, Greg KH wrote:
> > On Fri, Feb 03, 2017 at 11:55:24AM +0100, Richard Leitner wrote:
> >> +/**
> >> + * ascii2utf16le() - Helper routine for producing UTF-16LE string
> >> descriptors
> >> + * @s: Null-termin
On 17-02-06 09:28:22, Greg KH wrote:
> On Mon, Feb 06, 2017 at 10:14:44AM +0200, Petko Manolov wrote:
> > On 17-02-05 01:30:39, Greg KH wrote:
> > > On Sat, Feb 04, 2017 at 04:56:03PM +, Ben Hutchings wrote:
> > > > Allocating USB buffers on the stack is not portable, and no longer
> > > > wor
On Mon, Feb 06, 2017 at 02:51:09PM +0200, Petko Manolov wrote:
> On 17-02-06 09:28:22, Greg KH wrote:
> > On Mon, Feb 06, 2017 at 10:14:44AM +0200, Petko Manolov wrote:
> > > Random thought: isn't it better to add the alloc/free code in
> > > usb_control_msg() and avoid code duplication all over
On Mon, Feb 06, 2017 at 02:21:24PM +0100, Johan Hovold wrote:
> On Mon, Feb 06, 2017 at 02:51:09PM +0200, Petko Manolov wrote:
> > On 17-02-06 09:28:22, Greg KH wrote:
> > > On Mon, Feb 06, 2017 at 10:14:44AM +0200, Petko Manolov wrote:
>
> > > > Random thought: isn't it better to add the alloc/fr
On Mon, Feb 06, 2017 at 02:32:23PM +0100, Johan Hovold wrote:
> On Mon, Feb 06, 2017 at 02:21:24PM +0100, Johan Hovold wrote:
> > On Mon, Feb 06, 2017 at 02:51:09PM +0200, Petko Manolov wrote:
> > > On 17-02-06 09:28:22, Greg KH wrote:
> > > > On Mon, Feb 06, 2017 at 10:14:44AM +0200, Petko Manolov
From: Petko Manolov
> Sent: 06 February 2017 12:51
...
> I suspect getting the buffer allocation in usb_control_msg() will help with
> two
> things in the same time:
>
> - allocate in DMA-able memory;
> - code reduction;
Is there code around there to do 'bounce buffer' allocation
for systems w
On Mon, Feb 06, 2017 at 10:13:47AM +0200, Peter Ujfalusi wrote:
>
>
> On 01/25/2017 12:17 PM, Alexandre Bailon wrote:
> > A pointer to musb is now present in the dma_controller structure.
> > Remove the one present in tusb_omap_dma structure.
>
> the subject line should be: usb: musb: tusb6010_o
On Wed, Jan 25, 2017 at 11:17:03AM +0100, Alexandre Bailon wrote:
> This series was "dmaengine: cppi41: Make the driver more generic".
> I have tried to separate as munch I could CPPI 4.1 MUSB driver changes.
>
> Currently, the DMA interrupt is managed by the CPPI 4.1 driver.
> The issue here is t
As string.c now provides ascii2utf16le() use it in ascii2desc() for
converting the string descriptor.
Furthermore fix checkpatch.pl issues in ascii2desc().
Signed-off-by: Richard Leitner
---
drivers/usb/core/hcd.c | 22 ++
1 file changed, 10 insertions(+), 12 deletions(-)
d
For USB string descriptors we need to convert ASCII strings to UTF16-LE.
Therefore make a simple helper function (based on ascii2desc from
drivers/usb/core/hcd.c) for that purpose.
Signed-off-by: Richard Leitner
---
include/linux/string.h | 1 +
lib/string.c | 26 +
This patch series adds a driver for configuration of the Microchip USB251xB
USB 2.0 hub controller series with USB 2.0 upstream connectivity, SMBus
configuration interface and two to four USB 2.0 downstream ports.
CHANGES v3:
- move ascii2utf16le() to lib/string.c and also use it also for
This patch adds a driver for configuration of the Microchip USB251xB/xBi
USB 2.0 hub controller series with USB 2.0 upstream connectivity, SMBus
configuration interface and two to four USB 2.0 downstream ports.
Furthermore add myself as a maintainer for this driver.
The datasheet can be found at
On Mon, 6 Feb 2017, Richard Leitner wrote:
> For USB string descriptors we need to convert ASCII strings to UTF16-LE.
> Therefore make a simple helper function (based on ascii2desc from
> drivers/usb/core/hcd.c) for that purpose.
You know, we already have utf8s_to_utf16s() in fs/nls/nls_base.c.
Interface numbers do not change when enabling alternate settings as
comment and code in this driver suggested.
Remove the confusing comment and redundant retrieval of the interface
number in probe, while simplifying and renaming the interface-number
helper.
Fixes: 4db2299da213 ("sierra: driver in
On 02/06/2017 04:12 PM, Alan Stern wrote:
> On Mon, 6 Feb 2017, Richard Leitner wrote:
>
>> For USB string descriptors we need to convert ASCII strings to UTF16-LE.
>> Therefore make a simple helper function (based on ascii2desc from
>> drivers/usb/core/hcd.c) for that purpose.
>
> You know, we a
On Mon, 6 Feb 2017, Richard Leitner wrote:
> On 02/06/2017 04:12 PM, Alan Stern wrote:
> > On Mon, 6 Feb 2017, Richard Leitner wrote:
> >
> >> For USB string descriptors we need to convert ASCII strings to UTF16-LE.
> >> Therefore make a simple helper function (based on ascii2desc from
> >> drive
On 02/06/2017 04:40 PM, Alan Stern wrote:
> On Mon, 6 Feb 2017, Richard Leitner wrote:
>> So it would be OK to include linux/nls.h and use utf8s_to_utf16s() in
>> drivers/usb/{core/hcd.c,misc/usb251xb.c}?
>
> Well, we already include linux/nls.h in drivers/usb/core/message.c and
> a few files unde
From: Ben Hutchings
> Sent: 04 February 2017 16:57
> Allocating USB buffers on the stack is not portable, and no longer
> works on x86_64 (with VMAP_STACK enabled as per default).
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Ben Hutchings
> ---
> drivers/net/usb/rtl8150.c | 34 +
On Mon, Feb 06, 2017 at 04:09:18PM +, David Laight wrote:
> From: Ben Hutchings
[...]
> > + ret = usb_control_msg(dev->udev, usb_rcvctrlpipe(dev->udev, 0),
> > + RTL8150_REQ_GET_REGS, RTL8150_REQT_READ,
> > + indx, 0, buf, size, 500);
> > + if
On Mon, Feb 06, 2017 at 04:28:14PM +0100, Johan Hovold wrote:
> Interface numbers do not change when enabling alternate settings as
> comment and code in this driver suggested.
>
> Remove the confusing comment and redundant retrieval of the interface
> number in probe, while simplifying and renami
Hello!
On 02/06/2017 05:03 PM, Richard Leitner wrote:
For USB string descriptors we need to convert ASCII strings to UTF16-LE.
Therefore make a simple helper function (based on ascii2desc from
drivers/usb/core/hcd.c) for that purpose.
Signed-off-by: Richard Leitner
[...]
diff --git a/lib/st
On Mon, Feb 06, 2017 at 05:33:29PM +0100, Greg Kroah-Hartman wrote:
> On Mon, Feb 06, 2017 at 04:28:14PM +0100, Johan Hovold wrote:
> > Interface numbers do not change when enabling alternate settings as
> > comment and code in this driver suggested.
> >
> > Remove the confusing comment and redund
While not all line6 devices currently support PCM, it causes no
harm to 'have it prepared'.
This also fixes toneport, which only has PCM - in which case
we previously skipped the USB transfer properties detection completely.
Signed-off-by: Andrej Krutak
---
sound/usb/line6/driver.c | 49 +++
From: Cristian Birsan
Signed-off-by: Cristian Birsan
---
Fixes since previous patch:
- Fix coding style
- Validate parameters againsta device tree values
- Update error message display
- Update Kconfig comments
drivers/usb/gadget/udc/Kconfig | 5 ++--
When the context is deactivated, the link_type is set to 0xff, which
triggers a warning message, and results in a wrong link status, as
the LSI is ignored.
Signed-off-by: Stefan Brüns
---
drivers/net/usb/sierra_net.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --gi
When trying to initiate a dual-stack (ipv4v6) connection, a MC7710, FW
version SWI9200X_03.05.24.00ap answers with an unsupported LSI. Add support
for this LSI.
Also the link_type should be ignored when going idle, otherwise the modem
is stuck in a bad link state.
Tested on MC7710, T-Mobile DE, APN
If a context is configured as dualstack ("IPv4v6"), the modem indicates
the context activation with a slightly different indication message.
The dual-stack indication omits the link_type (IPv4/v6) and adds
additional address fields.
IPv6 LSIs are identical to IPv4 LSIs, but have a different link ty
Hi greg k-h,
The module si2168 has been changed in Linux 4.9.*, so I only done a
diff on the module.
Don't know if the issue is on this one, could be something else.
I will try to check this out with git bisect, but I'm not an expert
and don't know stuff about hardware stuff.
This is the output o
On Mon, 06 Feb 2017 20:34:58 +0100,
Andrej Krutak wrote:
>
> While not all line6 devices currently support PCM, it causes no
> harm to 'have it prepared'.
>
> This also fixes toneport, which only has PCM - in which case
> we previously skipped the USB transfer properties detection completely.
>
On Mon, Feb 6, 2017 at 10:19 PM, Takashi Iwai wrote:
> On Mon, 06 Feb 2017 20:34:58 +0100,
> Andrej Krutak wrote:
>>
>> While not all line6 devices currently support PCM, it causes no
>> harm to 'have it prepared'.
>>
>> This also fixes toneport, which only has PCM - in which case
>> we previously
Hi Frank,
Am Montag, 6. Februar 2017, 09:40:35 CET schrieb Frank Wang:
> On 2017/2/5 17:41, Heiko Stuebner wrote:
> > Am Sonntag, 5. Februar 2017, 10:51:00 CET schrieb Frank Wang:
> >> The original posting on Jan 19th have not received any responses, so I
> >> resend them.
> >>
> >> The Current d
Hi Frank,
Am Sonntag, 5. Februar 2017, 10:51:01 CET schrieb Frank Wang:
> Originally, dwc2 just handle one clock named otg, however, it may have
> two or more clock need to manage for some new SoCs, so this adds
> change clk to clk's array of dwc2_hsotg to handle more clocks operation.
>
> Signed
If a context is configured as dualstack ("IPv4v6"), the modem indicates
the context activation with a slightly different indication message.
The dual-stack indication omits the link_type (IPv4/v6) and adds
additional address fields.
IPv6 LSIs are identical to IPv4 LSIs, but have a different link ty
When the context is deactivated, the link_type is set to 0xff, which
triggers a warning message, and results in a wrong link status, as
the LSI is ignored.
Signed-off-by: Stefan Brüns
---
drivers/net/usb/sierra_net.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --gi
When trying to initiate a dual-stack (ipv4v6) connection, a MC7710, FW
version SWI9200X_03.05.24.00ap answers with an unsupported LSI. Add support
for this LSI.
Also the link_type should be ignored when going idle, otherwise the modem
is stuck in a bad link state.
Tested on MC7710, T-Mobile DE, APN
On Thu, Jan 19, 2017 at 02:21:26PM +0200, Mathias Nyman wrote:
> Hi Greg
>
> This series by Arnd Bergmann was originally six patches, but last two of
> them were already taken to 4.10. Without the rest of them there will
> be a regression in 4.10.
>
> Original cover letter says:
>
> For xhci-hcd
On Mon, Feb 06, 2017 at 07:03:41PM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb.git
> pwrseq-lib
> head: 06903db00af7968ff4960ab380c45a7788fee1d5
> commit: 778d7e6997538601e8ad364188bf007768922bd4 [2/10] power: add power
> sequence lib
Hi Heiko, John and Greg,
On 2017/2/7 8:06, Heiko Stuebner wrote:
Hi Frank,
Am Sonntag, 5. Februar 2017, 10:51:01 CET schrieb Frank Wang:
Originally, dwc2 just handle one clock named otg, however, it may have
two or more clock need to manage for some new SoCs, so this adds
change clk to clk's a
From: Alexandre Bailon
Currently, the CPPI 4.1 driver is not completely generic and
only works on DSPS. This is because of IRQ management.
Add a callback to dma_controller that could be invoked on DMA completion
to acknowledge the IRQ.
Signed-off-by: Alexandre Bailon
Signed-off-by: Bin Liu
---
From: Alexandre Bailon
Update cppi41_dma_callback() to detect an aborted transfer.
This was not required before because cppi41_dma_callback() was only
invoked on transfer completion.
In order to make CPPI 4.1 driver more generic, cppi41_dma_callback()
will be invoked after a transfer abort in ord
Hi Greg,
This is the second musb patch set for next v4.11-rc1. This series generalize
the musb cppi driver so that it can be adopted by DA8xx glue.
We just got the dmaengine maintainer ACK'd on 6/6 so the whole series is ready
to merge. Please let me know if any change is needed.
Regards,
-Bin.
From: Alexandre Bailon
Despite the CPPI 4.1 is a generic DMA, it is tied to USB.
On the DSPS, CPPI 4.1 interrupt's registers are in USBSS (the MUSB glue).
Currently, to enable / disable and clear interrupts, the CPPI 4.1 driver
maps and accesses to USBSS's register, which making CPPI 4.1 driver n
From: Alexandre Bailon
A pointer to musb is now present in the dma_controller structure.
Remove the one present in tusb_omap_dma structure.
Signed-off-by: Alexandre Bailon
Signed-off-by: Bin Liu
---
drivers/usb/musb/tusb6010_omap.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
From: Alexandre Bailon
A pointer to musb is now present in the dma_controller structure.
Remove the one present in cppi structure.
Signed-off-by: Alexandre Bailon
Signed-off-by: Bin Liu
---
drivers/usb/musb/cppi_dma.c | 26 +-
drivers/usb/musb/cppi_dma.h | 1 -
2 file
From: Alexandre Bailon
A pointer to musb is now present in the dma_controller structure.
Remove the one present in cppi41_dma_controller structure.
Signed-off-by: Alexandre Bailon
Signed-off-by: Bin Liu
---
drivers/usb/musb/musb_cppi41.c | 29 +
1 file changed, 13
Please ignore this series of patches, due to the first version have been
merged into usb-next branch except DTS's one[PACH 4/6].
This will cause mtu3 probe failure, so I will send new patches based on
usb-next branch.
sorry
On Mon, 2017-02-06 at 17:29 +0800, Chunfeng Yun wrote:
> Due to the refer
Due to the reference clock comes from 26M oscillator directly
on mt8173, and it is a fixed-clock in DTS which always turned
on, we ignore it before. But on some platforms, it comes
from PLL, and need be controlled, so here add it, no matter
it is a fixed-clock or not.
Signed-off-by: Chunfeng Yun
Make the reference clock optional for DTS backward compatibility
and ignore the error if it does not exist.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3_plat.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/mtu3/mtu3_plat.c b/drivers/usb/mt
Make the reference clock optional for DTS backward compatibility
and ignore the error if it does not exist.
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/host/xhci-mtk.c b/drivers/usb/host
On Fri, 2017-01-27 at 14:07 -0600, Rob Herring wrote:
> On Fri, Jan 20, 2017 at 04:18:41PM +0800, Chunfeng Yun wrote:
> > add a new compatible string for "mt2712", and move reference clock
> > into each port node;
> >
> > Signed-off-by: Chunfeng Yun
> > ---
> > .../devicetree/bindings/phy/phy-mt
Hello,
> > Implementation of new connect operation. This is linked as a part of
> > usbip command. With this patch, usbip command has following
> operations.
> >
> > bind
> > unbind
> > list (local/remote)
> > attach
> > detach
> > port
> > connect ... this patch
>
> Don't include existing
Hello,
> > Implementation of new disconnect operation. This is linked as a part of
> > usbip command. With this patch, usbip command has following
> operations.
> >
> > bind
> > unbind
> > list (local/remote)
> > attach
> > detach
> > port
> > connect ... previous patch
> > disconnect ...
Hello,
> > This patch adds function and usage of new connect operation,
> disconnect
> > operation and application(vhci)-side daemon to README and manuals.
>
> This should be the first patch for the series. That would have saved
> me lot of time. Please move this patch up.
OK. I will move the do
Hello,
> > Refactoring to attach and detach operation to reuse common portion to
> > application(vhci)-side daemon.
> >
> > The new application(vhci)-side daemon executes same procedures as
> > attach and detach. Most of common code to access vhci has been
> > implemented in VHCI userspace wrapper
Hello,
> On 12/26/2016 08:18 AM, Nobuo Iwata wrote:
> > This series of patches extends number of ports limitaion in application
> > (vhci) side.
> >
>
> (...)
>
> > 5. Dependencies
> >
> > This series depends on 'usbip: exporting devices' patch set because
> > this includes changes to applicatio
Hello,
> > Dear all,
> >
> > This series of patches adds exporting device operation to USB/IP.
> >
>
> I run through most of your series and answered with couple of comments.
>
> I'm not checking all patches in detail because I see that there is a lot
> of remarks from previous series which you
85 matches
Mail list logo
