From: Guenter Roeck <linux@roeck-us.net>
To: Timur Tabi <timur@codeaurora.org>, Arnd Bergmann <arnd@arndb.de>,
linaro-acpi@lists.linaro.org
Cc: 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 16:31:09 -0700 [thread overview]
Message-ID: <55440CBD.6000504@roeck-us.net> (raw)
In-Reply-To: <5543DA53.8070702@codeaurora.org>
On 05/01/2015 12:56 PM, Timur Tabi wrote:
> On 05/01/2015 02:24 PM, Arnd Bergmann wrote:
>> 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.
>
> This is what drives me crazy about Linux kernel development. I've been doing this for 15 years, and I still get random emails that contradict everything I've been told to date.
>
> I was repeatedly told over the past year by multiple people that ARM64 server == ACPI, no ifs, ands, or buts.
>
I don't think anyone ever claimed that Linux development is free
of politics. Except for master politicians, of course.
>> 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.
>
> Well, someone who actually has a DT-based ARM64 server system (which is not me) should come up with such a definition.
>
> I'm hoping that my driver can be accepted without DT support, and that someone else who is interested in running my driver on an SBSA device tree platform can add what's missing.
>
I am perfectly fine with that. All I am asking for is flexibility on your part.
Even if you (and/or others) may personally believe that ACPI _is_ the
center of the universe, please be open to the possibility that others
may have a different opinion and/or different requirements. We should not
have to completely rewrite the driver to add devicetree support later on.
Note we still have to figure out how to instantiate the device based on
the acpi data. I have no idea how that should be done, but it seems
odd if it is really supposed to be done as you have implemented it.
Maybe that is the case, but if so I would like to get a confirmation
from an acpi maintainer.
Thanks,
Guenter
next prev parent reply other threads:[~2015-05-01 23:31 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 ` [Linaro-acpi] " Arnd Bergmann
2015-05-01 19:56 ` Timur Tabi
2015-05-01 23:31 ` Guenter Roeck [this message]
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=55440CBD.6000504@roeck-us.net \
--to=linux@roeck-us.net \
--cc=arnd@arndb.de \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-watchdog@vger.kernel.org \
--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