Hi,
W dniu 18.02.2014 10:36, Johan Hovold pisze:
On Sun, Feb 16, 2014 at 12:35:06PM +0100, Emanuel Koczwara wrote:
Hi,
I have a device (thermal printer) which communicates through rs232. It
has also usb adapter/converter build-in.
root@emanuel-laptop:/home/emanuel# lsusb
Bus 004 Device 004: I
Hi
On Sun, Feb 23, 2014 at 7:52 AM, loody wrote:
> hi David:
>
> Thanks for your suggestion.
> 2014-02-23 0:56 GMT+08:00 David Herrmann :
>> Hi
>>
>> On Sat, Feb 22, 2014 at 5:35 PM, loody wrote:
>>> hi all:
>>> is there any kernel hid module parameter or test program can
>>> temporarily not let
On Sun, Feb 23, 2014 at 06:27:17AM +, Luke-Jr wrote:
> If I understand the USB Serial code correctly, at least open devices are
> constantly polled by 2 active URBs replaced immediately upon completion,
> except when the tty layer throttles them.
It depends on the specific driver, what one a
On Sun, Feb 23, 2014 at 06:27:17AM +, Luke-Jr wrote:
> If I understand the USB Serial code correctly, at least open devices are
> constantly polled by 2 active URBs replaced immediately upon completion,
> except when the tty layer throttles them.
As Greg mentioned, it depends on what driver
On Sun, Feb 23, 2014 at 03:40:58PM +0100, Emanuel Koczwara wrote:
> W dniu 18.02.2014 10:36, Johan Hovold pisze:
> > On Sun, Feb 16, 2014 at 12:35:06PM +0100, Emanuel Koczwara wrote:
> >> I have just one problem with that device. This is typical response from
> >> the printer:
> >>
> >> 1#X0;0;0;1
On Thu, Feb 20, 2014 at 09:28:33PM +0100, Magnus wrote:
> Hi,
>
> I borrowed another converter that uses pl2303 and it worked nicely.
> This device was bought some years ago and mine is new.
>
> I have taken a picture of both devices here, its valid for a week:
> http://picpaste.com/USB_to_Serial
On Sunday, February 23, 2014 5:45:19 PM you wrote:
> In general this should not cause any problems, but for example the
> ftdi_sio driver has the low-latency flag set by default which results in
> bulk-in data (mostly empty, status-only packets) being received
> every millisecond.
>
> If the flag
[quoted lines by Luke-Jr on 2014/02/23 at 19:03 +]
>I was looking at the circumstances surrounding ftdi_sio, which uses the
>generic implementation.
>
>wouldn't it be possible to just ask less often to
>reduce the bandwidth load?
That's sort of what we do in brltty's user-space implementati
Hi,
W dniu 23.02.2014 18:58, Johan Hovold pisze:
Perhaps the printer is sending some status bytes that we shouldn't
pass to user space. Could you provide a log from when you send a
command and get a response while running with debugging enabled? You
can enable debugging with echo "module usbse
Hi,
W dniu 23.02.2014 21:10, Emanuel Koczwara pisze:
Hi,
W dniu 23.02.2014 18:58, Johan Hovold pisze:
Perhaps the printer is sending some status bytes that we shouldn't
pass to user space. Could you provide a log from when you send a
command and get a response while running with debugging ena
On Sun, Feb 23, 2014 at 09:09:53PM +0100, Emanuel Koczwara wrote:
> Hi,
>
> W dniu 23.02.2014 18:58, Johan Hovold pisze:
> > Perhaps the printer is sending some status bytes that we shouldn't
> > pass to user space. Could you provide a log from when you send a
> > command and get a response whil
On Sun, Feb 23, 2014 at 07:03:54PM +, Luke-Jr wrote:
> On Sunday, February 23, 2014 5:45:19 PM you wrote:
> > In general this should not cause any problems, but for example the
> > ftdi_sio driver has the low-latency flag set by default which results in
> > bulk-in data (mostly empty, status-on
Luke-Jr wrote:
> > And this is the way that the USB protocol works, a device can not send
> > data to the host unless it is asked for it. So the host always has to
> > ask for it.
>
> I'm aware of that - but wouldn't it be possible to just ask less often to
> reduce the bandwidth load?
It depen
On Fri, 21 Feb 2014 15:16:52 Arnd Bergmann wrote:
> On Friday 21 February 2014 17:31:29 Alistair Popple wrote:
> > +static const struct of_device_id ohci_of_match[] = {
> > + { .compatible = "usb-ohci", },
> > + {},
> > +};
> > +
> >
> > static const struct platform_device_id ohci_pla
On Fri, 21 Feb 2014 10:41:50 Alan Stern wrote:
> On Fri, 21 Feb 2014, Alistair Popple wrote:
> > Currently the ppc-of driver uses the compatibility string
> > "usb-ehci". This means platforms that use device-tree and implement an
> > EHCI compatible interface have to either use the ppc-of driver or
Hi,
W dniu 23.02.2014 21:21, Johan Hovold pisze:
You might need to mount debugfs: mount -t debugfs none
/sys/kernel/debug and make sure your kernel is compiled with
CONFIG_DYNAMIC_DEBUG (and CONFIG_DEBUG_FS) enabled. Johan -- To
unsubscribe from this list: send the line "unsubscribe linux-usb"
On Sat, Feb 22, 2014 at 05:17:58PM +0400, Alexander Shiyan wrote:
> Signed-off-by: Alexander Shiyan
> ---
> drivers/usb/chipidea/ci_hdrc_imx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/chipidea/ci_hdrc_imx.c
> b/drivers/usb/chipidea/ci_hdrc_imx.c
> ind
Hi Felipe,
Any comments for this patch?
It is related to our coming otg work, thanks.
Peter
On Fri, Feb 7, 2014 at 1:46 PM, Peter Chen wrote:
> On Fri, Jan 10, 2014 at 3:54 PM, Peter Chen wrote:
>> We already have CONFIG_USB_OTG which can cover all CONFIG_USB_OTG_FSM
>> does.
>>
>> Cc: Jun Li
The serial adds power management support for MXS PHY, it includes:
- Add one PHY API .set_wakeup, and related API implementation at mxs phy driver
- misc changes and bug fixes for mxs phy to support low power mode and wakeup.
It is based on the lastest Greg's usb-next, 3.14-rc3.
Changes for v11:
We need this to keep PHY's power on or off during the system
suspend mode. If we need to enable USB wakeup, then we
must keep PHY's power being on during the system suspend mode.
Otherwise, we need to keep PHY's power being off to save power.
Signed-off-by: Peter Chen
---
drivers/usb/phy/phy-mxs
When we need the PHY can be waken up by external signals,
we can call this API. Besides, we call mxs_phy_disconnect_line
at this API to close the connection between USB PHY and
controller, after that, the line state from controller is SE0.
Once the PHY is out of power, without calling mxs_phy_disco
It is needed by imx6 SoC series, but not for imx23 and imx28.
Signed-off-by: Peter Chen
---
drivers/usb/phy/phy-mxs-usb.c | 15 +++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/phy/phy-mxs-usb.c b/drivers/usb/phy/phy-mxs-usb.c
index d7adca3..2411e05 1
Add anatop phandle for usbphy
Signed-off-by: Peter Chen
Signed-off-by: Shawn Guo
---
arch/arm/boot/dts/imx6qdl.dtsi |2 ++
arch/arm/boot/dts/imx6sl.dtsi |2 ++
2 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/arm/boot/dts/imx6qdl.dtsi
The mxs-phy has several bugs and features at different
versions, the driver code can get it through of_device_id.data.
Signed-off-by: Peter Chen
---
drivers/usb/phy/phy-mxs-usb.c | 58 ++--
1 files changed, 49 insertions(+), 9 deletions(-)
diff --git a/driv
This API is used to set wakeup enable at PHY registers, in that
case, the PHY can be waken up from suspend due to external events,
like vbus change, dp/dm change and id change.
Signed-off-by: Peter Chen
---
include/linux/usb/phy.h | 16
1 files changed, 16 insertions(+), 0 del
Add "fsl,imx6q-usbphy" for imx6dq and imx6dl, add
"fsl,imx6sl-usbphy" for imx6sl, and "fsl,imx23-usbphy"
is still a fallback for other strings.
Signed-off-by: Peter Chen
---
Documentation/devicetree/bindings/usb/mxs-phy.txt |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --
We need to use controller id to access different register regions
for mxs phy.
Signed-off-by: Peter Chen
Signed-off-by: Shawn Guo
---
arch/arm/boot/dts/imx23.dtsi |1 +
arch/arm/boot/dts/imx28.dtsi |2 ++
2 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/i
Add anatop phandle which is used to access anatop registers to
control PHY's power and other USB operations.
Signed-off-by: Peter Chen
---
Documentation/devicetree/bindings/usb/mxs-phy.txt |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings
Two PHY bugs are fixed by IC logic, but these bits are not
enabled by default, so we enable them at driver.
The two bugs are: MXS_PHY_ABNORMAL_IN_SUSPEND and MXS_PHY_SENDING_SOF_TOO_FAST
which are described at code.
Signed-off-by: Peter Chen
---
drivers/usb/phy/phy-mxs-usb.c | 23 +
The auto setting is used to open related power and clocks
automatically after receiving wakeup signal.
With this feature, the PHY's clock and power can be recovered
correctly from low power mode, it is guaranteed by IC logic.
Signed-off-by: Peter Chen
---
drivers/usb/phy/phy-mxs-usb.c | 20 ++
Change "high speed" to "HS"
Change "non-high speed" to "FS/LS"
Implementation of notify_suspend and notify_resume will be different
according to mxs_phy_data->flags.
Signed-off-by: Peter Chen
---
drivers/usb/phy/phy-mxs-usb.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
di
It is used to access un-regulator registers according to
different controllers.
Signed-off-by: Peter Chen
---
drivers/usb/phy/phy-mxs-usb.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/phy/phy-mxs-usb.c b/drivers/usb/phy/phy-mxs-usb.c
index cb71135..3
We need to use controller id to access different register regions
for mxs phy.
Signed-off-by: Peter Chen
Signed-off-by: Shawn Guo
---
arch/arm/boot/dts/imx6qdl.dtsi |2 ++
arch/arm/boot/dts/imx6sl.dtsi |2 ++
2 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/
After clear portsc.phcd, PHY needs 200us stable time for switch
32K clock to AHB clock.
Signed-off-by: Peter Chen
---
drivers/usb/phy/phy-mxs-usb.c | 11 +++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/phy/phy-mxs-usb.c b/drivers/usb/phy/phy-mxs-usb.c
in
Понедельник, 24 февраля 2014, 10:02 +08:00 от Peter Chen
:
> On Sat, Feb 22, 2014 at 05:17:58PM +0400, Alexander Shiyan wrote:
> > Signed-off-by: Alexander Shiyan
> > ---
> > drivers/usb/chipidea/ci_hdrc_imx.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/driver
On Mon, Feb 24, 2014 at 08:32:14AM +0400, Alexander Shiyan wrote:
> Понедельник, 24 февраля 2014, 10:02 +08:00 от Peter Chen
> :
> > On Sat, Feb 22, 2014 at 05:17:58PM +0400, Alexander Shiyan wrote:
> > > Signed-off-by: Alexander Shiyan
> > > ---
> > > drivers/usb/chipidea/ci_hdrc_imx.c | 2 +-
>
Hi,
I am not very sure if this error belong to ntfs-3g or linux-usb,
but the dmesg says a lot about USB devices so I am reporting it here.
Correct me if I am wrong.
I upgraded to Linux 3.13.5 and found my USB hard disk does not work
properly. But this bug only occurs when mounting an NTFS partiti
Oh!
I am so sorry! I forgot to install ntfs-3g package!
After the installation of this package the bug exists no more!
I am really sorry for the disturbance ...
2014-02-24 15:18 GMT+08:00 Sascha Weaver :
> Hi,
>
> I am not very sure if this error belong to ntfs-3g or linux-usb,
> but the dmesg
On 2014-02-18 16:52, Felipe Balbi wrote:
On Thu, Jan 09, 2014 at 11:54:13AM +0100, Andreas Larsson wrote:
Rename struct platform_device pointers from ofdev to pdev for clarity.
Suggested by Mark Rutland.
Signed-off-by: Andreas Larsson
---
drivers/usb/gadget/gr_udc.c | 18 +-
39 matches
Mail list logo
