From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux MMC List <linux-mmc@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Subject: Re: [PATCH v2 3/3] mmc: renesas_sdhi: do hard reset if possible
Date: Tue, 16 Mar 2021 13:57:09 +0100 [thread overview]
Message-ID: <20210316125709.GE1031@ninjato> (raw)
In-Reply-To: <CAMuHMdUw8wWh3ybsFUopKGMw-Zbcqr9bJBEGHAerL-Y226A0=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
> > + select RESET_CONTROLLER
>
> ... if ARCH_RENESAS?
>
> While RESET_CONTROLLER can be enabled on SuperH (and compiles),
> there are no reset drivers for SuperH, so it won't be used anyway.
Yeah, I also thought about it and decided against it. Because a new arch
will then support resets out of the box while the overhead for old archs
is negligible, I'd think.
But no strong opinion here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-16 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 14:59 [PATCH v2 0/3] mmc: renesas_sdhi: reset via reset controller Wolfram Sang
2021-03-15 14:59 ` [PATCH v2 1/3] mmc: tmio: abort DMA before reset Wolfram Sang
2021-03-15 14:59 ` [PATCH v2 2/3] mmc: renesas_sdhi: break SCC reset into own function Wolfram Sang
2021-03-15 14:59 ` [PATCH v2 3/3] mmc: renesas_sdhi: do hard reset if possible Wolfram Sang
2021-03-16 12:53 ` Geert Uytterhoeven
2021-03-16 12:57 ` Wolfram Sang [this message]
2021-03-16 13:14 ` Geert Uytterhoeven
2021-03-16 16:59 ` Wolfram Sang
2021-03-16 6:38 ` [PATCH v2 0/3] mmc: renesas_sdhi: reset via reset controller Yoshihiro Shimoda
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=20210316125709.GE1031@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=geert@linux-m68k.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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