All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vikram Narayanan <vikram186@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx6: Avoid writing to read-only bits in imximage.cfg
Date: Wed, 13 Jun 2012 23:10:06 +0530	[thread overview]
Message-ID: <4FD8D076.9020804@gmail.com> (raw)
In-Reply-To: <201206131915.46468.marex@denx.de>

Hello Marek,

On 6/13/2012 10:45 PM, Marek Vasut wrote:
> Dear Vikram Narayanan,
>
>> Hello Marek,
>>
>> On 6/13/2012 5:57 PM, Marek Vasut wrote:
>>> Dear Vikram Narayanan,
>>>
>>>> If in case this is valid according to the latest datasheet, ignore this
>>>> patch.
>>>>
>>>> --
>>>> According to REV C manual, the register IOMUXC_IOMUXC_GPR4 has
>>>> bits 4 and 5 read-only and the value is always set as zero.
>>>> So write '0' to these bits instead of writing '1'.
>>>
>>> I'm acking this as writing 0 to read-only bits is the only rightous thing
>>> to do. btw. how did you find this? Good catch, praise on you :-)
>> :
>> :)
>>
>> In the middle of writing a imximage.cfg file for a custom mx6 board.
>
> So it did manifest somehow?

Still in progress. :)

Regards,
Vikram

  reply	other threads:[~2012-06-13 17:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 14:50 [U-Boot] [PATCH] mx6: Avoid writing to read-only bits in imximage.cfg Vikram Narayanan
2012-06-12 15:05 ` Dirk Behme
2012-06-13  2:55   ` Liu Hui-R64343
2012-06-13 11:18     ` Marek Vasut
2012-06-13 11:28       ` Fabio Estevam
2012-06-13 11:31       ` Liu Hui-R64343
2012-06-13 12:24         ` Marek Vasut
2012-06-13 13:15           ` Liu Hui-R64343
2012-06-13 13:21             ` Marek Vasut
2012-06-13 12:27 ` Marek Vasut
2012-06-13 16:38   ` Vikram Narayanan
2012-06-13 17:15     ` Marek Vasut
2012-06-13 17:40       ` Vikram Narayanan [this message]
2012-06-15 14:27 ` Stefano Babic

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=4FD8D076.9020804@gmail.com \
    --to=vikram186@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.