public inbox for linux-watchdog@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linaro-acpi@lists.linaro.org
Cc: Timur Tabi <timur@codeaurora.org>,
	Guenter Roeck <linux@roeck-us.net>,
	linux-watchdog@vger.kernel.org, Wim Van Sebroeck <wim@iguana.be>,
	Vipul Gandhi <vgandhi@codeaurora.org>
Subject: Re: [Linaro-acpi] [PATCH] watchdog: introduce the ARM64 SBSA watchdog driver
Date: Fri, 01 May 2015 21:24:01 +0200	[thread overview]
Message-ID: <28676294.hhciQCjd9F@wuerfel> (raw)
In-Reply-To: <5543C921.9050800@codeaurora.org>

On Friday 01 May 2015 13:42:41 Timur Tabi wrote:
> 
> >> I think the GTDT is required.  Most likely, the kernel will fail to boot
> >> long before we get to this point if the GTDT is missing or corrupt.
> >
> > ACPI, the center of the universe ;-). Is ACPI support on arm64 now mandatory ?
> > I thought it also supports devicetree ?
> 
> Yes, ACPI for ARM64 *servers* is mandatory.  ARM64 servers are not 
> supposed to use device tree.
> 
> And since this is a driver for SBSA systems (SBSA = Server Base System 
> Architecture), this driver will only ever be used on an ARM64 server 
> system with ACPI and no device tree at all.

No, that is not a reasonable assumption to make. All the ARM64 server
systems we have today are using DT only and we will of course keep
supporting systems like that. 

Nothing prevents you from using the same register set on a platform
that is not SBSA compliant, or using DT on a machine that is SBSA
compliant, and we will definitely see that happen for chips that are
shared between products, e.g. a SBSA+SCPI system in a server targeted
market and the same hardware with devicetree for e.g. networking
equipment.

This means we need a DT binding for the driver, and the ACPI portion
that creates the platform device should be split out from the main
driver.

	Arnd

  reply	other threads:[~2015-05-01 19:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 19:33 [PATCH] watchdog: introduce the ARM64 SBSA watchdog driver Timur Tabi
2015-05-01  3:30 ` Guenter Roeck
2015-05-01 16:16   ` Timur Tabi
2015-05-01 17:28     ` Timur Tabi
2015-05-01 17:32       ` Guenter Roeck
2015-05-01 17:41         ` Timur Tabi
2015-05-01 17:59           ` Guenter Roeck
2015-05-01 18:46             ` Timur Tabi
2015-05-01 17:49     ` Guenter Roeck
2015-05-01 18:42       ` Timur Tabi
2015-05-01 19:24         ` Arnd Bergmann [this message]
2015-05-01 19:56           ` [Linaro-acpi] " Timur Tabi
2015-05-01 23:31             ` Guenter Roeck
2015-05-02 13:16               ` Timur Tabi
2015-05-01 19:26         ` Guenter Roeck
2015-05-01 19:49           ` Timur Tabi
2015-05-01 19:19     ` [Linaro-acpi] " Arnd Bergmann
2015-05-01 20:15       ` Timur Tabi
2015-05-01 23:16         ` Guenter Roeck
2015-05-01 23:22           ` Timur Tabi
2015-05-01 23:33             ` Guenter Roeck
2015-05-01 13:09 ` Ashwin Chaugule
2015-05-02 13:55 ` Hanjun Guo

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=28676294.hhciQCjd9F@wuerfel \
    --to=arnd@arndb.de \
    --cc=linaro-acpi@lists.linaro.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=timur@codeaurora.org \
    --cc=vgandhi@codeaurora.org \
    --cc=wim@iguana.be \
    /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