From: Timur Tabi <timur@codeaurora.org>
To: Fu Wei <fu.wei@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Linaro ACPI Mailman List <linaro-acpi@lists.linaro.org>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org, Wei Fu <tekkamanninja@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, Guenter Roeck <linux@roeck-us.net>,
Vipul Gandhi <vgandhi@codeaurora.org>,
Wim Van Sebroeck <wim@iguana.be>, Jon Masters <jcm@redhat.com>,
Leo Duran <leo.duran@amd.com>, Jon Corbet <corbet@lwn.net>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Rafael Wysocki <rjw@rjwysocki.net>,
Dave Young <dyoung@redhat.com>,
Pratyush Anand <panand@redhat.com>,
Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>,
Rob Herring <robherring2@gmail.com>
Subject: Re: [PATCH v8 1/5] Documentation: add sbsa-gwdt driver documentation
Date: Fri, 30 Oct 2015 13:53:24 -0500 [thread overview]
Message-ID: <5633BCA4.1050400@codeaurora.org> (raw)
In-Reply-To: <CADyBb7sPqsoQdYBUpHY2HvZ+iT7ABa9NoCX7Jax1NKugYOy1zQ@mail.gmail.com>
On 10/30/2015 01:35 PM, Fu Wei wrote:
>> I think maybe Mark was asking why WS1 is optional, not the WS1
> My answer is for "why WS1 is optional"!
>
>> >interrupt. Maybe you can reword the documentation to make is clear
>> >that
> I didn't say : "only the*interrupt* for WS1 is optional."
WS1 itself is not optional. The spec says that WS0 and WS1 are separate
events, and doesn't saying anything about either being optional. The
*interrupt* for WS1, however, is optional.
Besides, what does the driver do with the WS1 interrupt? If it's
specified in the device tree, it appears to be ignored by the driver.
And the ACPI table only allows for specifying ONE interrupt. So how
would the driver register a handler for WS1 on an ACPI system?
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2015-10-30 18:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 16:06 [PATCH v8 0/5] Watchdog: introduce ARM SBSA watchdog driver fu.wei
2015-10-27 16:06 ` [PATCH v8 1/5] Documentation: add sbsa-gwdt driver documentation fu.wei
2015-10-27 16:22 ` Mark Rutland
2015-10-28 4:10 ` Fu Wei
2015-10-30 17:46 ` Timur Tabi
2015-10-30 18:35 ` Fu Wei
2015-10-30 18:53 ` Timur Tabi [this message]
2015-10-30 19:05 ` Mark Rutland
2015-10-30 20:37 ` Timur Tabi
2015-11-02 4:10 ` Fu Wei
2015-11-02 4:03 ` Fu Wei
2015-11-02 4:06 ` Timur Tabi
2015-11-02 4:23 ` Jon Masters
2015-10-27 16:06 ` [PATCH v8 2/5] ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts fu.wei
2015-10-27 16:06 ` [PATCH v8 3/5] ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi fu.wei
2015-10-27 16:06 ` [PATCH v8 4/5] Watchdog: introdouce "pretimeout" into framework fu.wei
2015-10-27 16:06 ` [PATCH v8 5/5] Watchdog: introduce ARM SBSA watchdog driver fu.wei
2015-11-05 1:59 ` [Linaro-acpi] " Timur Tabi
2015-11-05 5:13 ` Guenter Roeck
2015-11-05 11:58 ` Fu Wei
2015-11-05 13:47 ` Timur Tabi
2015-11-05 13:47 ` Timur Tabi
2015-11-05 14:03 ` Fu Wei
2015-11-05 14:08 ` Timur Tabi
2015-11-05 14:35 ` Fu Wei
2015-11-05 14:40 ` Timur Tabi
2015-11-05 15:00 ` Fu Wei
2015-11-05 16:41 ` Guenter Roeck
2015-11-05 17:58 ` Fu Wei
2015-11-05 17:59 ` Timur Tabi
2015-11-05 18:04 ` Fu Wei
2015-11-13 0:06 ` Al Stone
2015-11-13 0:23 ` Timur Tabi
2015-11-19 23:50 ` Al Stone
2015-11-13 0:25 ` Guenter Roeck
2015-11-20 0:11 ` Al Stone
2015-11-20 0:26 ` Timur Tabi
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=5633BCA4.1050400@codeaurora.org \
--to=timur@codeaurora.org \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dyoung@redhat.com \
--cc=fu.wei@linaro.org \
--cc=jcm@redhat.com \
--cc=leo.duran@amd.com \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=panand@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=robherring2@gmail.com \
--cc=tekkamanninja@gmail.com \
--cc=vgandhi@codeaurora.org \
--cc=will.deacon@arm.com \
--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