From: Jean Pihet <jpihet@mvista.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects (was: Re: Beagleboard rev C memory timings & suspend/resume)
Date: Wed, 3 Jun 2009 09:03:25 +0200 [thread overview]
Message-ID: <200906030903.25638.jpihet@mvista.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0906021724490.31531@utopia.booyaka.com>
Hi Paul,
OK I will rework the code and send a patch when done.
Regards,
Jean
On Wednesday 03 June 2009 01:40:13 Paul Walmsley wrote:
> Hi Jean,
>
> a minor request: it is easier to comment on these patches if they are
> included inline in the E-mail message, rather than attached. That way
> code comments can be inlined in the reply.
>
> On Tue, 26 May 2009, Jean Pihet wrote:
> > Here is a patch for the SDRC 2nd CS support. It applies on top of the
> > current pm branch.
>
> Thanks for doing this work.
>
> > I have some questions:
> > - Is it OK to copy the micron sdram params file to a new file with the 2
> > CSes params? One could use a unique file with #ifdef SDRC_SUPPORT_2_CSES.
>
> Is it possible for the SDRAM parameter files to remain unchanged, and to
> simply pass two struct omap_sdrc_params * to omap2_init_common_hw() and
> then to omap2_sdrc_init()? Boards with only CS0 in use should pass NULL
> for the second omap_sdrc_params *.
>
> So something like this (I realize the PM branch has additional parameters
> here also):
>
> void __init omap2_init_common_hw(struct omap_sdrc_params *sdrc_cs0,
> struct omap_sdrc_params *sdrc_cs1)
>
> Then:
>
> void __init omap2_sdrc_init(struct omap_sdrc_params *sdrc_cs0,
> struct omap_sdrc_params *sdrc_cs1)
>
> I would prefer that approach.
>
> It would also be good to avoid changing the SDRC CS1 parameters in the
> SRAM code if the board does not use CS1. Maybe pass in a flag that
> indicates whether CS1 is in use, and if not, avoid programming those
> registers? The (admittedly minor) overhead of loading the CS1 registers
> off the stack would be nice to avoid also.
>
> > - Does the RX51 board have 2 sdram parts? If so I need to update the
> > board file as well.
>
> Probably best if someone from Nokia handles this.
>
>
> - Paul
next prev parent reply other threads:[~2009-06-03 7:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 13:53 Beagleboard rev C memory timings & suspend/resume Jean Pihet
2009-05-06 23:39 ` Paul Walmsley
2009-05-07 11:18 ` Jean Pihet
2009-05-07 16:44 ` Jean Pihet
2009-05-07 18:59 ` Paul Walmsley
2009-05-08 7:05 ` Jean Pihet
2009-05-08 22:43 ` Paul Walmsley
2009-05-11 19:10 ` Jean Pihet
2009-05-11 20:27 ` Paul Walmsley
2009-05-26 13:27 ` [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects (was: Re: Beagleboard rev C memory timings & suspend/resume) Jean Pihet
2009-06-02 23:40 ` Paul Walmsley
2009-06-03 7:03 ` Jean Pihet [this message]
2009-06-05 15:35 ` Jean Pihet
2009-06-05 18:10 ` Paul Walmsley
2009-06-08 7:37 ` Tero.Kristo
2009-06-08 8:59 ` Jean Pihet
2009-06-08 14:59 ` Kevin Hilman
2009-06-08 17:08 ` Jean Pihet
2009-06-08 17:23 ` [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects Kevin Hilman
2009-06-09 8:14 ` Tero.Kristo
2009-06-09 8:23 ` Jean Pihet
2009-06-09 8:29 ` Tero.Kristo
2009-06-09 7:26 ` [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects (was: Re: Beagleboard rev C memory timings & suspend/resume) Paul Walmsley
2009-06-05 19:14 ` Paul Walmsley
2009-06-06 10:50 ` Grazvydas Ignotas
2009-06-08 9:02 ` Jean Pihet
2009-06-08 11:01 ` Grazvydas Ignotas
2009-06-08 17:11 ` Jean Pihet
2009-06-08 17:28 ` [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects Kevin Hilman
2009-05-07 19:18 ` Beagleboard rev C memory timings & suspend/resume Paul Walmsley
2009-05-08 8:13 ` Jean Pihet
2009-05-08 22:51 ` Paul Walmsley
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=200906030903.25638.jpihet@mvista.com \
--to=jpihet@mvista.com \
--cc=khilman@deeprootsystems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox