From: eric@eukrea.com (Eric Bénard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] otg/ulpi.c : fix register write
Date: Thu, 24 Jun 2010 16:37:14 +0200 [thread overview]
Message-ID: <4C236D9A.4030707@eukrea.com> (raw)
In-Reply-To: <4C236600.2030605@compulab.co.il>
Le 24/06/2010 16:04, Igor Grinberg a ?crit :
> ulpi_set_flags is used to set the OTG flags and not to clear them,
> also it is a static function and is not a part of struct otg_transceiver,
> so it cannot be called from outside the ulpi.c, thus after the ulpi_create,
> it is never called.
> I think, currently, this should stay as it is.
>
OK, the problem that when one flag is set, you can't clear it without
resetting the PHY.
Eric
next prev parent reply other threads:[~2010-06-24 14:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 16:43 [PATCH v2] otg/ulpi.c : fix register write Eric Bénard
2010-06-24 14:04 ` Igor Grinberg
2010-06-24 14:37 ` Eric Bénard [this message]
2010-06-27 7:42 ` Igor Grinberg
2010-06-27 14:00 ` Eric Bénard
2010-07-06 10:31 ` Igor Grinberg
2010-07-14 14:22 ` Igor Grinberg
2010-07-14 20:47 ` Greg KH
2010-07-15 5:26 ` Igor Grinberg
2010-07-15 7:20 ` Eric Bénard
2010-07-21 14:46 ` Igor Grinberg
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=4C236D9A.4030707@eukrea.com \
--to=eric@eukrea.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).