linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Andreas Schwab <schwab@suse.de>
Cc: Anup Patel <Anup.Patel@wdc.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Atish Patra <Atish.Patra@wdc.com>,
	Alistair Francis <Alistair.Francis@wdc.com>,
	Christoph Hellwig <hch@lst.de>, Anup Patel <anup@brainfault.org>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] RISC-V: Enable SYSCON reboot and poweroff drivers
Date: Mon, 11 Nov 2019 17:59:13 +0100	[thread overview]
Message-ID: <20191111165913.GA20290@lst.de> (raw)
In-Reply-To: <mvm1ruecpyv.fsf@suse.de>

On Mon, Nov 11, 2019 at 05:55:36PM +0100, Andreas Schwab wrote:
> > For QEMU virt machine, the DT is generated by QEMU at runtime
> > so we don't need an explicit DT file in Linux sources.
> 
> What about the HiFiveU?

According to Palmer the IP block exists there, but isn't actually
wired up to reset or reboot the board.  So adding the DT entries
is rather pointless.

  reply	other threads:[~2019-11-11 16:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11 13:34 [PATCH] RISC-V: Enable SYSCON reboot and poweroff drivers Anup Patel
2019-11-11 13:43 ` Anup Patel
2019-11-11 14:05   ` David Abdurachmanov
2019-11-11 14:08 ` Andreas Schwab
2019-11-11 14:21   ` Anup Patel
2019-11-11 14:32     ` Andreas Schwab
2019-11-11 16:51       ` Anup Patel
2019-11-11 16:55         ` Andreas Schwab
2019-11-11 16:59           ` Christoph Hellwig [this message]
2019-11-11 17:01           ` David Abdurachmanov
2019-11-11 17:05             ` Andreas Schwab
2019-11-11 17:06 ` Paul Walmsley
2019-11-12  4:19   ` Anup Patel
2019-11-23  3:03 ` Paul Walmsley

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=20191111165913.GA20290@lst.de \
    --to=hch@lst.de \
    --cc=Alistair.Francis@wdc.com \
    --cc=Anup.Patel@wdc.com \
    --cc=Atish.Patra@wdc.com \
    --cc=anup@brainfault.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=schwab@suse.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;
as well as URLs for NNTP newsgroup(s).