linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: amit.kucheria@linaro.org (Amit Kucheria)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] mx51: Move OTG initialisation for all boards to a single file
Date: Mon, 11 Oct 2010 13:34:30 +0300	[thread overview]
Message-ID: <AANLkTimVo8uLHq4zCskBU4C_nWYiw89BxUw2FM_p3qhQ@mail.gmail.com> (raw)
In-Reply-To: <20101007074853.GZ28242@pengutronix.de>

On Thu, Oct 7, 2010 at 10:48 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> Added Daniel to Cc as he might say something here aswell.

<snip>

> I have recently looked at the way the USB phy settings are handled on
> i.MX and it's coming to its limits. Currently the phy settings are coded
> into generic flags, passed to the usb driver which then calls
> mxc_initialize_usb_hw() which dispatches the different SoCs and translates
> the generic flags back into SoC specific ones. ?While this was doable
> until now it fails badly on i.MX51 as we see here.
> The phy settings are totally static to a given board, so we could simply
> let the board call a mx51_init_usb_phy() which gets a pointer to a
> struct with all relevant register settings. And we could pass this
> function SoC specific register settings without having to encode them
> into generic flags and decode them again later.
>
> Sascha

Sascha,

Do you think something like this will be better? It looks even more
scattered to me, the usb configuration information is scattered across
platform_data and phy_data.

Or did you want to get rid of platform_data->init too from the driver?

Regards,
Amit
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-mxc-Stop-passing-usb-phy-configuration-to-the-ehci-d.patch
Type: text/x-patch
Size: 9144 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20101011/0d8b79a1/attachment.bin>

  parent reply	other threads:[~2010-10-11 10:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07  0:57 [PATCH 0/3] mxc: mx51: Add support for efikamx nettop Amit Kucheria
2010-10-07  0:58 ` [PATCH 1/3] mx51: add support for genesi " Amit Kucheria
2010-10-07  6:55   ` Uwe Kleine-König
2010-10-07 10:31     ` Amit Kucheria
2010-10-07  0:58 ` [PATCH 2/3] mx51: efikamx: add otg support Amit Kucheria
2010-10-07  6:59   ` Uwe Kleine-König
2010-10-07 11:22   ` Sergei Shtylyov
2010-10-07  0:58 ` [PATCH 3/3] mx51: Move OTG initialisation for all boards to a single file Amit Kucheria
2010-10-07  7:08   ` Uwe Kleine-König
2010-10-07 12:04     ` Amit Kucheria
2010-10-07 12:22       ` Uwe Kleine-König
2010-10-07  7:48   ` Sascha Hauer
2010-10-07 12:03     ` Fabio Estevam
2010-10-08  8:27     ` Amit Kucheria
2010-10-11 10:34     ` Amit Kucheria [this message]
2010-10-11 13:10       ` Sascha Hauer
2010-10-11 14:08         ` Amit Kucheria

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=AANLkTimVo8uLHq4zCskBU4C_nWYiw89BxUw2FM_p3qhQ@mail.gmail.com \
    --to=amit.kucheria@linaro.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).