All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 3/4] MX5: Introduce a function for setting the chip select size
Date: Thu, 19 May 2011 08:49:41 -0300	[thread overview]
Message-ID: <BANLkTin1g0pipAR_D3VFqm55=ZXsLBVn_g@mail.gmail.com> (raw)
In-Reply-To: <4DD4D8DA.1030205@denx.de>

Hi Stefano,

On Thu, May 19, 2011 at 5:46 AM, Stefano Babic <sbabic@denx.de> wrote:
> On 05/18/2011 10:47 PM, Fabio Estevam wrote:
>> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
>> ---
>
> Hi Fabio,
>
>> +void set_chipselect_size(int const cs_size)
>> +{
>> + ? ? unsigned int reg;
>> + ? ? struct iomuxc *iomuxc_regs = (struct weim *)IOMUXC_BASE_ADDR;
>> + ? ? reg = readl(&iomuxc_regs->gpr1);
>> +
>> + ? ? switch (cs_size) {
>> + ? ? case CS0_128:
>> + ? ? ? ? ? ? reg &= ~0x7; ? ?/* CS0=128MB, CS1=0, CS2=0, CS3=0 */
>> + ? ? ? ? ? ? reg |= 0x5;
>> + ? ? ? ? ? ? break;
>> + ? ? case CS0_64M_CS1_64M:
>> + ? ? ? ? ? ? reg &= ~0x3F; ? /* CS0=64MB, CS1=64MB, CS2=0, CS3=0 */
>> + ? ? ? ? ? ? reg |= 0x1B;
>> + ? ? ? ? ? ? break;
>> + ? ? case CS0_64M_CS1_32M_CS2_32M:
>> + ? ? ? ? ? ? reg &= ~0x1FF; ?/* CS0=64MB, CS1=32MB, CS2=32MB, CS3=0 */
>> + ? ? ? ? ? ? reg |= 0x4B;
>> + ? ? ? ? ? ? break;
>> + ? ? case CS0_32M_CS1_32M_CS2_32M_CS3_32M:
>> + ? ? ? ? ? ? reg &= ~0xFFF; ?/* CS0=32MB, CS1=32MB, CS2=32MB, CS3=32MB */
>> + ? ? ? ? ? ? reg |= 0x249;
>> + ? ? ? ? ? ? break;
>> + ? ? default:
>> + ? ? ? ? ? ? printf("Unknown chip select size\n");
>> + ? ? ? ? ? ? break;
>> + ? ? }
>> +
>> + ? ? writel(reg, &iomuxc_regs->gpr1);
>> +}
>
> mmmhhh...it seems to me not complete, because not all combinations are
> covered.

Yes, it is complete. Only these four combinations are allowed as per
the MX53 Reference Manual.

>And setting fixed values in the switch constraints us to have
> very long defines, as CS0_32M_CS1_32M_CS2_32M_CS3_32M.

I can change the very long defines if you want.

I thought initially on doing the generic function as you described,
but then we would need to check for only the 4 valid combinations.
Then I came with this implementation that only handle the 4 possible
cases.

Let me know what you think.

Regards,

Fabio Estevam

  reply	other threads:[~2011-05-19 11:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 20:47 [U-Boot] [PATCH v3 1/4] MX5: Make the weim structure complete Fabio Estevam
2011-05-18 20:47 ` [U-Boot] [PATCH v3 2/4] MX5: Add iomux structure Fabio Estevam
2011-05-18 20:47   ` [U-Boot] [PATCH v3 3/4] MX5: Introduce a function for setting the chip select size Fabio Estevam
2011-05-18 20:47     ` [U-Boot] [PATCH v3 4/4] MX53: Add initial support for MX53ARD Fabio Estevam
2011-05-19  8:46     ` [U-Boot] [PATCH v3 3/4] MX5: Introduce a function for setting the chip select size Stefano Babic
2011-05-19 11:49       ` Fabio Estevam [this message]
2011-05-19 12:04         ` Stefano Babic
2011-05-19 19:02     ` Wolfgang Denk

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='BANLkTin1g0pipAR_D3VFqm55=ZXsLBVn_g@mail.gmail.com' \
    --to=festevam@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.