From: grinberg@compulab.co.il (Igor Grinberg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: pxa: Fix pxa3xx-u2d crash when ULPI not used
Date: Sun, 05 Sep 2010 17:31:53 +0300 [thread overview]
Message-ID: <4C83A9D9.9050803@compulab.co.il> (raw)
In-Reply-To: <AANLkTik7Hzs8OUKSL+6HRgvR1iRWg4LE_v0LMUC2VxVZ@mail.gmail.com>
On 09/05/10 16:58, Eric Miao wrote:
> On Sun, Sep 5, 2010 at 9:46 PM, Igor Grinberg <grinberg@compulab.co.il> wrote:
>> On 09/05/10 13:43, Eric Miao wrote:
>>> On Sun, Sep 5, 2010 at 4:35 PM, Igor Grinberg <grinberg@compulab.co.il> wrote:
>>> Igor,
>>>
>>> So do you this as a proper fix, or there is better way out?
>> If we want to keep it the most straight-forward way so it is fine.
>>
>> Another possible ways would be:
>>
>> 1) create a new flag, lets say PORT2_USE_U2DC in pxaohci_platform_data.
>> This is a relatively clean way of making ohci aware of
>> u2d existence at runtime and eliminates the calls to functions
>> of non-existing (not loaded) driver...
>>
>> 2) use something like:
>> struct u2d_hc_ops {
>> int (*start_hc)(...);
>> void (*stop_hc)(...);
>> }
>>
>> in board init code register the ops structure via the pxa_ohci platform data.
>>
>> This way adds some more pollution to the pxa_ohci glue with code
>> relevant only to pxa3xx, achieving the same as the 1st way, but also
>> can be useful for u2dc otg/peripheral driver (if it will come some day...).
>>
>> I'm fine with both (Marek's patch or my proposal), so tell me what
>> looks better to you.
>>
> That sounds to be a cleaner way, but may require more changes. What
> if we get this patch into -rc phase as is first, and get a cleaner patch for
> -next?
Fine with me.
--
Regards,
Igor.
next prev parent reply other threads:[~2010-09-05 14:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 20:35 [PATCH] ARM: pxa: Fix pxa3xx-u2d crash when ULPI not used Marek Vasut
2010-09-04 5:38 ` Eric Miao
2010-09-05 7:54 ` Igor Grinberg
2010-09-05 8:01 ` Marek Vasut
2010-09-05 8:16 ` Igor Grinberg
2010-09-05 8:25 ` Marek Vasut
2010-09-05 8:35 ` Igor Grinberg
2010-09-05 10:43 ` Eric Miao
2010-09-05 13:46 ` Igor Grinberg
2010-09-05 13:58 ` Eric Miao
2010-09-05 14:31 ` Igor Grinberg [this message]
2010-09-05 19:23 ` Marek Vasut
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=4C83A9D9.9050803@compulab.co.il \
--to=grinberg@compulab.co.il \
--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 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.