From: Sinan Akman <sinan@writeme.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2015.10-rc4 released
Date: Wed, 30 Sep 2015 15:09:41 -0400 [thread overview]
Message-ID: <560C3375.3090209@writeme.com> (raw)
In-Reply-To: <CAOMZO5DrXwXc4KBUKTu-Yqgo4SKGi2vUy4S_tSbuYpVOCL1gLQ@mail.gmail.com>
Fabio Estevam wrote:
> On Wed, Sep 30, 2015 at 3:56 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> On Wed, Sep 30, 2015 at 3:33 PM, Sinan Akman <sinan@writeme.com> wrote:
>>
>>> Nope, AFAICS it doesn't make any difference.
>> Ok, the issue is due to endianness: on LS1021 the watchdog is
>> big-endian, so that's why we can't use clrsetbits_le16().
>>
>> Please check:
>> http://git.freescale.com/git/cgit.cgi/layerscape/ls1021a/linux.git/commit/?id=b53a344d20f6ffdc383d990a9636efb53ce272a9
>>
>> What about this?
>>
>> --- a/drivers/watchdog/imx_watchdog.c
>> +++ b/drivers/watchdog/imx_watchdog.c
>> @@ -54,8 +54,11 @@ void hw_watchdog_init(void)
>> void reset_cpu(ulong addr)
>> {
>> struct watchdog_regs *wdog = (struct watchdog_regs *)WDOG1_BASE_ADDR;
>> + int reg;
>
> ops, this should be u16 instead.
>
>> - clrsetbits_le16(&wdog->wcr, 0, WCR_WDE);
>> + reg = readw(&wdog->wcr);
>> + reg |= WCR_WDE;
>> + writew(reg, &wdog->wcr);
>>
>> writew(0x5555, &wdog->wsr);
>> writew(0xaaaa, &wdog->wsr); /* load minimum 1/2 second timeout */
>
OK, this will probably work, as I tried writew earlier and it worked,
I agree it seems an endianness issue, do we not want to address
all common accesses in a way that takes endianness into account ?
I'll test the above as well (with u16 reg) to make sure.
Regards
Sinan Akman
next prev parent reply other threads:[~2015-09-30 19:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 21:09 [U-Boot] [ANN] U-Boot v2015.10-rc4 released Tom Rini
2015-09-29 6:41 ` Wolfgang Denk
2015-09-29 15:35 ` Lukasz Majewski
2015-09-30 16:47 ` Sinan Akman
2015-09-30 17:16 ` York Sun
2015-09-30 17:22 ` Sinan Akman
2015-09-30 18:02 ` Sinan Akman
2015-09-30 18:16 ` Fabio Estevam
2015-09-30 18:33 ` Sinan Akman
2015-09-30 18:56 ` Fabio Estevam
2015-09-30 19:03 ` Fabio Estevam
2015-09-30 19:09 ` Sinan Akman [this message]
2015-09-30 19:13 ` Fabio Estevam
2015-10-01 15:19 ` [U-Boot] ls1021atwr reset issue (was [ANN] U-Boot v2015.10-rc4 released) Sinan Akman
2015-10-01 19:09 ` Fabio Estevam
2015-10-01 19:14 ` Tom Rini
2015-10-01 19:17 ` Otavio Salvador
2015-10-01 19:33 ` Sinan Akman
2015-10-01 19:38 ` Fabio Estevam
2015-10-01 19:41 ` Sinan Akman
2015-10-01 19:28 ` Sinan Akman
2015-10-01 19:36 ` Fabio Estevam
2015-10-01 14:22 ` [U-Boot] [ANN] U-Boot v2015.10-rc4 released 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=560C3375.3090209@writeme.com \
--to=sinan@writeme.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox