From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ls102xa: Fix reset hang
Date: Sat, 3 Oct 2015 11:18:26 -0400 [thread overview]
Message-ID: <20151003151826.GN3829@bill-the-cat> (raw)
In-Reply-To: <20151002144214.E7D4E382C64@gemini.denx.de>
On Fri, Oct 02, 2015 at 04:42:14PM +0200, Wolfgang Denk wrote:
> Dear Fabio,
>
> In message <1443792315-18997-1-git-send-email-festevam@gmail.com> you wrote:
> >
> ...
> > Unlike i.MX and Vybrid, the watchdog controller on LS102x is big-endian.
> ...
> > +struct watchdog_regs {
> > + u16 wcr; /* Control */
> > + u16 wsr; /* Service */
> > + u16 wrsr; /* Reset Status */
> > +};
> > +
> > +#define WCR_SRS (1 << 4)
>
> This belongs to some watchdog (or processor) related header file.
>
> As is, it duplicates code from drivers/watchdog/imx_watchdog.c which
> is something we should not do.
>
> > diff --git a/drivers/watchdog/Makefile b/drivers/watchdog/Makefile
> > index 9e9cb55..a007ae8 100644
> > --- a/drivers/watchdog/Makefile
> > +++ b/drivers/watchdog/Makefile
> > @@ -7,7 +7,7 @@
> >
> > obj-$(CONFIG_AT91SAM9_WATCHDOG) += at91sam9_wdt.o
> > obj-$(CONFIG_FTWDT010_WATCHDOG) += ftwdt010_wdt.o
> > -ifneq (,$(filter $(SOC), mx31 mx35 mx5 mx6 mx7 vf610 ls102xa))
> > +ifneq (,$(filter $(SOC), mx31 mx35 mx5 mx6 mx7 vf610))
>
> So this fixes the reset problem for now - but what happens when
> someone wants to use the watchdog for real? Will we create a copy of
> drivers/watchdog/imx_watchdog.c using big-endian accessors? This
> cannot be right?
Fabio, can you do a v2 that makes the commit message a bit clearer that
this is a temporary work-around and that a proper solution to the
underlying problem is coming? I think everyone that's reading this
thread knows this but we should make it clear to someone that just picks
up the code / commit (so maybe a comment block too) that we're making
things non-broken for the release but that's not the same thing as
making it correct for the long term. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151003/8d2a2e20/attachment-0001.sig>
next prev parent reply other threads:[~2015-10-03 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 13:25 [U-Boot] [PATCH] ls102xa: Fix reset hang Fabio Estevam
2015-10-02 14:21 ` Sinan Akman
2015-10-02 14:34 ` Fabio Estevam
2015-10-02 14:55 ` Sinan Akman
2015-10-02 14:42 ` Wolfgang Denk
2015-10-02 14:51 ` Sinan Akman
2015-10-02 15:00 ` Fabio Estevam
2015-10-03 15:18 ` Tom Rini [this message]
2015-10-07 21:43 ` Fabio Estevam
2015-10-07 21:45 ` York Sun
2015-10-07 21:47 ` Fabio Estevam
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=20151003151826.GN3829@bill-the-cat \
--to=trini@konsulko.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