From: "Pali Rohár" <pali.rohar@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Greg KH <greg@kroah.com>,
balbi@ti.com, bigeasy@linutronix.de, george.cherian@ti.com,
tony@atomide.com, varkabhadram@gmail.com,
linux-kernel@vger.kernel.org, sre@debian.org, sre@ring0.de,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, khilman@kernel.org,
aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
patrikbachan@gmail.com
Subject: Re: musb-hdrc: "Vbus off, timeout 1100 msec" message does not belong in sysfs
Date: Thu, 9 Jul 2015 23:54:36 +0200 [thread overview]
Message-ID: <201507092354.36649@pali> (raw)
In-Reply-To: <20150709214610.GA20890@amd>
[-- Attachment #1: Type: Text/Plain, Size: 2434 bytes --]
On Thursday 09 July 2015 23:46:10 Pavel Machek wrote:
> On Thu 2015-07-09 23:39:22, Pavel Machek wrote:
> > Hi!
> >
> > sysfs should contain one value per file. This one has at least two,
> > with nice english sentence as a bonus.
> >
> > root@n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/mu
> > sb-hdrc.0.auto# cat vbus
> > Vbus off, timeout 1100 msec
> >
> > :-(.
>
> Plus, documentation for this is nowhere to be seen:
>
> pavel@amd:/data/l/linux-n900$ grep -ri musb Documentation/ABI/
> pavel@amd:/data/l/linux-n900$
>
> ..which is a shame, because it is not really clear how to use this
> one:
>
> root@n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto# cat mode
> b_idle
> root@n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto# echo a_suspend > mode
> -bash: echo: write error: Invalid argument
> root@n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto# echo a > mode
> -bash: echo: write error: Invalid argument
> root@n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto# echo a_host > mode
> -bash: echo: write error: Invalid argument
> root@n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto# echo b_host > mode
> -bash: echo: write error: Invalid argument
> root@n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto# echo a_idle > mode
> -bash: echo: write error: Invalid argument
> root@n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto# echo b_wait_acon > mode
> -bash: echo: write error: Invalid argument
> root@n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto#
>
>
> Pavel
Hi!
I remember that this file is used for switching between usb peripheral
and host mode. But because n900 HW somehow broken, for usb host mode are
needed couple of "hack" patches which workaround HW bugs... This is
still not enough and "support" from userspace is needed for it too.
Kernel patches are part of Maemo kernel-power 2.6.28 version and with
package usbmode http://maemo.org/packages/view/usbmode/ is it possible
to enter usb host mode on n900 (and then connect e.g. usb stick).
And IIRC correct command is:
# echo host > mode
# echo peripheral > mode
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: pali.rohar@gmail.com (Pali Rohár)
To: linux-arm-kernel@lists.infradead.org
Subject: musb-hdrc: "Vbus off, timeout 1100 msec" message does not belong in sysfs
Date: Thu, 9 Jul 2015 23:54:36 +0200 [thread overview]
Message-ID: <201507092354.36649@pali> (raw)
In-Reply-To: <20150709214610.GA20890@amd>
On Thursday 09 July 2015 23:46:10 Pavel Machek wrote:
> On Thu 2015-07-09 23:39:22, Pavel Machek wrote:
> > Hi!
> >
> > sysfs should contain one value per file. This one has at least two,
> > with nice english sentence as a bonus.
> >
> > root at n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/mu
> > sb-hdrc.0.auto# cat vbus
> > Vbus off, timeout 1100 msec
> >
> > :-(.
>
> Plus, documentation for this is nowhere to be seen:
>
> pavel at amd:/data/l/linux-n900$ grep -ri musb Documentation/ABI/
> pavel at amd:/data/l/linux-n900$
>
> ..which is a shame, because it is not really clear how to use this
> one:
>
> root at n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto# cat mode
> b_idle
> root at n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto# echo a_suspend > mode
> -bash: echo: write error: Invalid argument
> root at n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto# echo a > mode
> -bash: echo: write error: Invalid argument
> root at n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto# echo a_host > mode
> -bash: echo: write error: Invalid argument
> root at n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto# echo b_host > mode
> -bash: echo: write error: Invalid argument
> root at n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto# echo a_idle > mode
> -bash: echo: write error: Invalid argument
> root at n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto# echo b_wait_acon > mode
> -bash: echo: write error: Invalid argument
> root at n900:/sys/devices/platform/68000000.ocp/480ab000.usb_otg_hs/musb
> -hdrc.0.auto#
>
>
> Pavel
Hi!
I remember that this file is used for switching between usb peripheral
and host mode. But because n900 HW somehow broken, for usb host mode are
needed couple of "hack" patches which workaround HW bugs... This is
still not enough and "support" from userspace is needed for it too.
Kernel patches are part of Maemo kernel-power 2.6.28 version and with
package usbmode http://maemo.org/packages/view/usbmode/ is it possible
to enter usb host mode on n900 (and then connect e.g. usb stick).
And IIRC correct command is:
# echo host > mode
# echo peripheral > mode
--
Pali Roh?r
pali.rohar at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150709/4145c2fd/attachment.sig>
next prev parent reply other threads:[~2015-07-09 21:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 21:39 musb-hdrc: "Vbus off, timeout 1100 msec" message does not belong in sysfs Pavel Machek
2015-07-09 21:46 ` Pavel Machek
2015-07-09 21:46 ` Pavel Machek
2015-07-09 21:46 ` Pavel Machek
2015-07-09 21:54 ` Pali Rohár [this message]
2015-07-09 21:54 ` Pali Rohár
2015-07-10 7:17 ` Sebastian Andrzej Siewior
2015-07-10 7:17 ` Sebastian Andrzej Siewior
2015-07-13 20:30 ` Felipe Balbi
2015-07-13 20:30 ` Felipe Balbi
2015-07-13 20:30 ` Felipe Balbi
2015-07-10 19:50 ` Felipe Balbi
2015-07-10 21:46 ` Pavel Machek
2015-07-10 23:21 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201507092354.36649@pali \
--to=pali.rohar@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=george.cherian@ti.com \
--cc=greg@kroah.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=patrikbachan@gmail.com \
--cc=pavel@ucw.cz \
--cc=sre@debian.org \
--cc=sre@ring0.de \
--cc=tony@atomide.com \
--cc=varkabhadram@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.