All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Lech Perczak <lech.perczak@gmail.com>
Cc: linux-mips@vger.kernel.org, John Crispin <john@phrozen.org>,
	Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH] MIPS: ath79: drop _machine_restart again
Date: Tue, 11 Jan 2022 16:18:17 +0100	[thread overview]
Message-ID: <20220111151817.GA11006@alpha.franken.de> (raw)
In-Reply-To: <20220110224844.2329275-1-lech.perczak@gmail.com>

On Mon, Jan 10, 2022 at 11:48:44PM +0100, Lech Perczak wrote:
> Commit 81424d0ad0d4 ("MIPS: ath79: Use the reset controller to restart
> OF machines") removed setup of _machine_restart on OF machines to use
> reset handler in reset controller driver.
> While removing remnants of non-OF machines in commit 3a77e0d75eed
> ("MIPS: ath79: drop machfiles"), this was introduced again, making it
> impossible to use additional restart handlers registered through device
> tree. Drop setting _machine_restart altogether, and ath79_restart
> function, which is no longer used after this.
> 
> Fixes: 3a77e0d75eed ("MIPS: ath79: drop machfiles")
> Cc: John Crispin <john@phrozen.org>
> Cc: Florian Fainelli <f.fainelli@gmail.com>
> Signed-off-by: Lech Perczak <lech.perczak@gmail.com>
> ---
> 
> Side note: a lot of code, that was previously encompassed by
> "if (mips_machtype != ATH79_MACH_GENERIC_OF) {...} " seems to be
> unnecessary at the time of dropping the non-OF machine definitions.
> However it was retained for some reason, and I see a lot of references
> to it by the drivers. OTOH, OF part of ath79 platform - basically whole ath79
> target of OpenWrt works well without this code in 19.07 release, using 4.14.y
> tree, on which the bug I'm fixing here is absent as well.
> 
> I tested this change on several devices:
> TP-Link TL-WDR4300, TP-Link Archer C7v2, Meraki MR18 using OF,
> and on ZTE MF286 - using OF as well - which is the very reason I discovered
> this issue, as it requires registration of  gpio-restart handler,
> ineffective due to this issue.
> 
>  arch/mips/ath79/setup.c | 10 ----------
>  1 file changed, 10 deletions(-)

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2022-01-11 15:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 22:48 [PATCH] MIPS: ath79: drop _machine_restart again Lech Perczak
2022-01-11 15:18 ` Thomas Bogendoerfer [this message]

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=20220111151817.GA11006@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=f.fainelli@gmail.com \
    --cc=john@phrozen.org \
    --cc=lech.perczak@gmail.com \
    --cc=linux-mips@vger.kernel.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 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.