From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: OTG implementation with external transceiver on PXA270
Date: Tue, 11 May 2010 14:04:22 +0800 [thread overview]
Message-ID: <AANLkTikw_VJog3nxH6lcJT4mRJbBcEju-2u6HFpdH3cv@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim7lTbhu97hy3tiSXVpkQKr5X6YpU8zSUiVarca@mail.gmail.com>
On Mon, May 10, 2010 at 9:33 AM, Sergey Lapin <slapinid@gmail.com> wrote:
> Hi, all!
>
> I try to implement external OTG transceiver on PXA270.
> I just need basic device mode at the moment.
>
> A problem is that PXA itself handles interrupt of external chip via
> UDC interrupt. But I need to read my chip-specific registers
> from there while I want to maintain pxa270_udc in a generic way
> without cluttering it with i2c calls, so I can implement it in the
> following ways:
>
> * make chip-specific data struct global (like it is in isp1301_omap.c
> and make exported function in OTG driver, enable handling of OTG interrupts
> in pxa27x_udc and call that function from there.
> * add API function like otg_handle_interrupt, enable handling of OTG interrupts
> in pxa27x_udc and call it from there. Which seems to be less messy.
>
> Any other suggestions? If that work is really being done somewhere,
> I'd like to help with testing.
>
The problem with isp1301_omap.c is that it's not separating the components
into otg controller and otg transciever, which means at the moment the quickest
way is to write something similar as isp1301_pxa27x.c, but apparently, the
optimal way in my POV is to have a good abstraction, so the OTG transceiver
and controller code can be re-used.
next prev parent reply other threads:[~2010-05-11 6:04 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 [this message]
2010-05-12 18:23 ` Robert Jarzmik
2010-05-13 14:00 ` Mark Brown
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=AANLkTikw_VJog3nxH6lcJT4mRJbBcEju-2u6HFpdH3cv@mail.gmail.com \
--to=eric.y.miao@gmail.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).