From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/6] wdt: sunxi: Move restart code to the watchdog driver
Date: Mon, 23 Jun 2014 16:42:47 +0200 [thread overview]
Message-ID: <19870078.UBj78UMBrO@wuerfel> (raw)
In-Reply-To: <53A83A20.6090800@roeck-us.net>
On Monday 23 June 2014 07:30:56 Guenter Roeck wrote:
> On 06/23/2014 03:31 AM, Maxime Ripard wrote:
> > On Thu, May 22, 2014 at 02:12:07PM -0700, Guenter Roeck wrote:
> >> On Thu, May 22, 2014 at 10:34:44PM +0200, Maxime Ripard wrote:
> >>> On Mon, May 19, 2014 at 05:04:22PM +0200, Maxime Ripard wrote:
> >>
> >> The patches _are_ in my watchdog-next branch and get some coverage from
> >> both my auto-builders and from Fenguang's build robots, so while they are
> >> not in linux-next, they are not completely in the dark either.
> >
> > So, this patch finally didn't make it into 3.16. Great. Now, we can't
> > even reboot the boards.
> >
> > Given how it's just impossible to get something merged reliably
> > through the watchdog tree, I guess I should just start merging the
> > patches through mine?
> >
>
> You can not really blame Wim here.
>
> In this case, I suspect the major reason for not accepting the patch
> is that I tried to provide a clean method / API for "reset through watchdog
> subsystem", which went nowhere, in my understanding because someone objected
> that it would be the wrong thing to do [1] and it didn't get approval /
> acceptance from the arm maintainers. If it is wrong to reset the board
> from the watchdog subsystem in a clean way, it is for sure even more wrong
> to do it as you proposed in your patch.
>
> My conclusion therefore is that all board reset code should move back out
> of the watchdog subsystem, and that we should not accept such code in the
> future. This is not my personal preference, but I do believe that we should
> do it in a clean way or not at all.
Moved to where?
I certainly don't want it in the platform directories, and for arm64 we
intentionally don't have a place to put this stuff.
drivers/power/reset would be an option, but then we have to solve the
problem of loading two drivers for one device first.
Arnd
next prev parent reply other threads:[~2014-06-23 14:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 2:44 [PATCH v2 0/6] ARM: sunxi: Machine code cleanup Maxime Ripard
2014-05-07 2:44 ` [PATCH v2 1/6] wdt: sunxi: Move restart code to the watchdog driver Maxime Ripard
2014-05-07 21:33 ` Guenter Roeck
2014-05-15 9:11 ` Maxime Ripard
2014-05-19 15:04 ` Maxime Ripard
2014-05-22 20:34 ` Maxime Ripard
2014-05-22 20:39 ` One Thousand Gnomes
2014-05-22 20:56 ` Maxime Ripard
2014-05-22 21:12 ` Guenter Roeck
2014-05-23 8:33 ` Maxime Ripard
2014-06-23 10:31 ` Maxime Ripard
2014-06-23 14:30 ` Guenter Roeck
2014-06-23 14:42 ` Arnd Bergmann [this message]
2014-06-23 15:16 ` Guenter Roeck
2014-06-23 15:35 ` Arnd Bergmann
2014-06-23 15:40 ` Guenter Roeck
2014-06-23 15:49 ` Maxime Ripard
[not found] ` <20140623213046.GR22347@spo001.leaseweb.com>
2014-06-23 21:47 ` Guenter Roeck
2014-06-24 9:27 ` Arnd Bergmann
[not found] ` <20140623211323.GA28120@spo001.leaseweb.com>
2014-06-24 14:49 ` Maxime Ripard
2014-06-24 16:01 ` Guenter Roeck
[not found] ` <20140802080208.GA22804@spo001.leaseweb.com>
2014-08-02 15:17 ` Maxime Ripard
2014-08-02 15:45 ` Guenter Roeck
2014-05-07 2:44 ` [PATCH v2 2/6] power: reset: Add Allwinner A31 reset code Maxime Ripard
2014-05-07 2:44 ` [PATCH v2 3/6] ARM: sunxi: Remove reset code from the platform Maxime Ripard
2014-05-07 2:44 ` [PATCH v2 4/6] ARM: sunxi: Remove init_machine callback Maxime Ripard
2014-05-07 2:44 ` [PATCH v2 5/6] ARM: sunxi: Add A31 reset driver to sunxi_defconfig Maxime Ripard
2014-05-07 2:44 ` [PATCH v2 6/6] ARM: multi_v7: Add Allwinner reset drivers to multi_v7_defconfig Maxime Ripard
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=19870078.UBj78UMBrO@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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