From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "Mohammed, Afzal" <afzal@ti.com>,
khilman@ti.com,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v4-alt 3/6] ARM: OMAP3: hwmod data: add gpmc
Date: Fri, 25 May 2012 10:26:59 +0300 [thread overview]
Message-ID: <20120525072659.GB6206@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1205230843260.3085@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [120523 17:55]:
> On Tue, 22 May 2012, Tony Lindgren wrote:
> >
> > Unfortunately for many of the older boards these values will probably
> > remain unknown.
> >
> > So the better approach here is to just disable frequency scaling
> > for these cases. Otherwise we'll be breaking old boards with smsc911x
> > where the timings for the FPGA controlling smsc911x are unknown.
> >
> > If we somehow manage to get those values without breaking support for
> > these boards, then yes I agree we should deprecate hardcoded and
> > bootloader values.
>
> I was thinking that if we log the register values supplied by the
> bootloader to the console, then someone can write a patch to the board
> file or DT data to set those register values explicitly in the kernel,
> once they're known. Or at least just report them to the l-o list.
>
> So then that should reduce the problem cases down to boards which no one
> reports the data to the mailing list within a few mainline kernel releases
> -- i.e., boards which are unmaintained. For those boards, I'd suggest
> that we just drop GPMC support until someone shows up who has a board and
> can test-boot it. Or just drop the board completely ;-)
OK seems fair to me. It still allows us to boot the older boards with
minimal changes (but without L3 frequency scaling).
Sounds like those registers should be dumped only if no configuration
is specified to avoid spamming the console.
Regards,
Tony
next prev parent reply other threads:[~2012-05-25 7:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 8:45 [PATCH v4-alt 0/6] GPMC driver migrate one Afzal Mohammed
2012-05-02 8:45 ` [PATCH v4-alt 1/6] ARM: OMAP2+: gpmc: driver conversion Afzal Mohammed
2012-05-02 8:46 ` [PATCH v4-alt 2/6] ARM: OMAP2+: gpmc: Adapt to HWMOD Afzal Mohammed
2012-05-02 8:46 ` [PATCH v4-alt 3/6] ARM: OMAP3: hwmod data: add gpmc Afzal Mohammed
2012-05-06 2:04 ` Paul Walmsley
2012-05-07 11:12 ` Mohammed, Afzal
2012-05-08 13:12 ` Mohammed, Afzal
2012-05-08 15:37 ` Paul Walmsley
2012-05-08 15:32 ` Paul Walmsley
2012-05-10 6:03 ` Mohammed, Afzal
2012-05-12 4:23 ` Mohammed, Afzal
2012-05-22 6:47 ` Paul Walmsley
2012-05-22 11:35 ` Mohammed, Afzal
2012-05-22 16:42 ` Tony Lindgren
2012-05-23 14:51 ` Paul Walmsley
2012-05-25 7:26 ` Tony Lindgren [this message]
2012-05-25 10:15 ` Mohammed, Afzal
2012-06-05 7:13 ` Tony Lindgren
2012-06-12 11:36 ` Mohammed, Afzal
2012-05-02 8:46 ` [PATCH v4-alt 4/6] ARM: OMAP2+: gpmc: driver migration hack Afzal Mohammed
2012-05-02 8:46 ` [PATCH v4-alt 5/6] ARM: OMAP2+: gpmc-smsc911x: Add helper for driver conversion Afzal Mohammed
2012-05-02 8:46 ` [PATCH v4-alt 6/6] ARM: OMAP2+: board omap3evm: gpmc driver adaptation Afzal Mohammed
2012-05-08 21:36 ` [PATCH v4-alt 0/6] GPMC driver migrate one Tony Lindgren
2012-05-10 6:35 ` Mohammed, Afzal
2012-05-11 20:00 ` Tony Lindgren
2012-05-14 4:59 ` Mohammed, Afzal
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=20120525072659.GB6206@atomide.com \
--to=tony@atomide.com \
--cc=afzal@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/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.