linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: OTG implementation with external transceiver on PXA270
Date: Thu, 13 May 2010 15:00:03 +0100	[thread overview]
Message-ID: <20100513140003.GA23183@sirena.org.uk> (raw)
In-Reply-To: <87mxw5yo6e.fsf@free.fr>

On Wed, May 12, 2010 at 08:23:21PM +0200, Robert Jarzmik wrote:
> Eric Miao <eric.y.miao@gmail.com> writes:

> That seems a good idea.
> If you expand it further, you could design the full OTG framework :
>  - extend otg.c, add the OTG state machine
>  - extend otg.h and otg.c with new calls :
>    - otg_set_state()
>    - otg_get_state()
>    - otg_signal_udc()
>  - extend otg.h, with callbacks like :
>    - otg_handle_interrupt()

> Separate the isp1301 driver from pxa270. The link will be done through the OTG
> framework. Remember the pxa270 has taken the udc IO space, so no access can be
> done from the isp1301 side (it should not actually for clean separation).

> But that could be more or less what you were thinking about.

This would be really good, not just for OTG but for USB in general -
there's other devices which could make use of information like PMICs
doing regulation of power draw from/to USB.

      reply	other threads:[~2010-05-13 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10  1:33 OTG implementation with external transceiver on PXA270 Sergey Lapin
2010-05-11  6:04 ` Eric Miao
2010-05-12 18:23   ` Robert Jarzmik
2010-05-13 14:00     ` Mark Brown [this message]

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=20100513140003.GA23183@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.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).