linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: ulpi_check_integrity returning error
Date: Tue, 14 Dec 2010 17:26:22 +0100	[thread overview]
Message-ID: <877hfce2xd.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <AANLkTimUSdV-0L+BSLumTJCDeFOgYNhw6azLjWuK4uX6@mail.gmail.com> (Fabio Estevam's message of "Tue, 14 Dec 2010 14:16:32 -0200")

Fabio Estevam <festevam@gmail.com> writes:

> On Tue, Dec 14, 2010 at 1:03 PM, Arnaud Patard
> <arnaud.patard@rtp-net.org> wrote:
> ...
>>> I am curious to know if any of this boards can work in host mode OTG
>>> with current mainline kernel.
>>
>> I guess you need to configure portsc register into ulpi mode in the
>> .init function of the mxc_usbh_platform_data otherwise, you won't be
>> able to reach the ulpi.
>
> Yes, I am configuring the portsc register into ULPI mode:
>
> .portsc	= MXC_EHCI_MODE_ULPI,
>
> Code does reach ulpi read/write functions in arch/arm/plat-mxc/ulpi.c,
> but always return 0 in the reads.

Please, read again what I said. I'm not talking of .portsc but of
.init. To reach the ulpi, the portsc register should be set to ulpi mode
_before_ calling otg_init() in ehci_mxc_drv_probe() but the code is using
.portsc/setting portsc in ehci_mxc_setup() which is afaik _after_
ehci_mxc_drv_probe().


Arnaud

  reply	other threads:[~2010-12-14 16:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTinxLr10X-EBGQHdhC5JyxbJOqcUz_+UMOCo+OFA@mail.gmail.com>
     [not found] ` <4D076E49.3020805@compulab.co.il>
2010-12-14 14:47   ` ulpi_check_integrity returning error Fabio Estevam
2010-12-14 15:03     ` Arnaud Patard (Rtp)
2010-12-14 16:16       ` Fabio Estevam
2010-12-14 16:26         ` Arnaud Patard (Rtp) [this message]
2010-12-14 22:17           ` Fabio Estevam
2010-12-15  1:32             ` Fabio Estevam
2010-12-14 17:44     ` Philippe Rétornaz
2010-12-14 20:47       ` Sascha Hauer

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=877hfce2xd.fsf@lechat.rtp-net.org \
    --to=arnaud.patard@rtp-net.org \
    --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).