From: Fu Wei <fu.wei@linaro.org> To: Mark Rutland <mark.rutland@arm.com> Cc: Timur Tabi <timur@codeaurora.org>, 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: Mon, 2 Nov 2015 12:03:17 +0800 [thread overview] Message-ID: <CADyBb7sjZ-XcPkGqtD4Dq-V5CmXY1dSBf7RiC7VLunMBrdMvMw@mail.gmail.com> (raw) In-Reply-To: <20151030190514.GD30791@leverpostej> Hi Mark, Great thanks for your feedback. On 31 October 2015 at 03:05, Mark Rutland <mark.rutland@arm.com> wrote: > On Fri, Oct 30, 2015 at 01:53:24PM -0500, Timur Tabi wrote: >> 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. > > This is a moot point. The distintion between the signal and the > interrupt doens't matter here. > > I was only asking why the interrupt was optional, and it seems per the > spec it's expected to be handed to an agent at a higher exception level. yes, that is the good point. Thanks I have thought about it My thought is : In virtualization system, Linux kernel with KVM support as a Hypervisor, and guest are using a one of SBSA watchdog. WS0 is handled by guest OS, and WS1 will be handled by Hypervisor. And in datasheet of Foundation model, we can see: IRQ ID SPI offset Device 60 28 EL2 Generic Watchdog WS1 So maybe we need WS1 interrupt info, Maybe not. So I say : WS1 info in FDT binding info is optional. *BUT*, (1) I don't see any hardware need to handle WS1 for now, because AMD seattle is the only real hardware with SBSA watchdog I can test now. (2) In GTDT, there is not data about WS1 (3) I don't handle WS1 in this driver. > > That implies that the OS should only care about WS0, assuming that I've > understood correctly. yes, after getting your and Timur's email. I have thought about this in the weekend, Maybe we can forget about WS1 in the FDT binding info temporary until we need to handle WS1 in Linux on any hardware(or model). > > Thanks, > Mark. -- Best regards, Fu Wei Software Engineer Red Hat Software (Beijing) Co.,Ltd.Shanghai Branch Ph: +86 21 61221326(direct) Ph: +86 186 2020 4684 (mobile) Room 1512, Regus One Corporate Avenue,Level 15, One Corporate Avenue,222 Hubin Road,Huangpu District, Shanghai,China 200021
WARNING: multiple messages have this Message-ID (diff)
From: Fu Wei <fu.wei-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> To: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org> Cc: Timur Tabi <timur-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>, Linaro ACPI Mailman List <linaro-acpi-cunTk1MwBs8s++Sfvej+rw@public.gmane.org>, linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Wei Fu <tekkamanninja-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>, Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>, Vipul Gandhi <vgandhi-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>, Wim Van Sebroeck <wim-IQzOog9fTRqzQB+pC5nmwQ@public.gmane.org>, Jon Masters <jcm-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>, Leo Duran <leo.duran-5C7GfCeVMHo@public.gmane.org>, Jon Corbet <corbet-T1hC0tSOHrs@public.gmane.org>, Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>, Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>, Rafael Wysocki <rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org>, Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>, Pratyush Anand <panand-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>, Suravee Suthikulpanit <Suravee.Suthikulpanit-5C7GfCeVMHo@public.gmane.org>, Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Subject: Re: [PATCH v8 1/5] Documentation: add sbsa-gwdt driver documentation Date: Mon, 2 Nov 2015 12:03:17 +0800 [thread overview] Message-ID: <CADyBb7sjZ-XcPkGqtD4Dq-V5CmXY1dSBf7RiC7VLunMBrdMvMw@mail.gmail.com> (raw) In-Reply-To: <20151030190514.GD30791@leverpostej> Hi Mark, Great thanks for your feedback. On 31 October 2015 at 03:05, Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org> wrote: > On Fri, Oct 30, 2015 at 01:53:24PM -0500, Timur Tabi wrote: >> 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. > > This is a moot point. The distintion between the signal and the > interrupt doens't matter here. > > I was only asking why the interrupt was optional, and it seems per the > spec it's expected to be handed to an agent at a higher exception level. yes, that is the good point. Thanks I have thought about it My thought is : In virtualization system, Linux kernel with KVM support as a Hypervisor, and guest are using a one of SBSA watchdog. WS0 is handled by guest OS, and WS1 will be handled by Hypervisor. And in datasheet of Foundation model, we can see: IRQ ID SPI offset Device 60 28 EL2 Generic Watchdog WS1 So maybe we need WS1 interrupt info, Maybe not. So I say : WS1 info in FDT binding info is optional. *BUT*, (1) I don't see any hardware need to handle WS1 for now, because AMD seattle is the only real hardware with SBSA watchdog I can test now. (2) In GTDT, there is not data about WS1 (3) I don't handle WS1 in this driver. > > That implies that the OS should only care about WS0, assuming that I've > understood correctly. yes, after getting your and Timur's email. I have thought about this in the weekend, Maybe we can forget about WS1 in the FDT binding info temporary until we need to handle WS1 in Linux on any hardware(or model). > > Thanks, > Mark. -- Best regards, Fu Wei Software Engineer Red Hat Software (Beijing) Co.,Ltd.Shanghai Branch Ph: +86 21 61221326(direct) Ph: +86 186 2020 4684 (mobile) Room 1512, Regus One Corporate Avenue,Level 15, One Corporate Avenue,222 Hubin Road,Huangpu District, Shanghai,China 200021 -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-11-02 4:03 UTC|newest] Thread overview: 48+ 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-27 16:22 ` Mark Rutland 2015-10-28 4:10 ` Fu Wei 2015-10-28 4:10 ` Fu Wei 2015-10-30 17:46 ` Timur Tabi 2015-10-30 17:46 ` Timur Tabi 2015-10-30 18:35 ` Fu Wei 2015-10-30 18:53 ` Timur Tabi 2015-10-30 18:53 ` Timur Tabi 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:10 ` Fu Wei 2015-11-02 4:03 ` Fu Wei [this message] 2015-11-02 4:03 ` Fu Wei 2015-11-02 4:06 ` Timur Tabi 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 13:47 ` Timur Tabi 2015-11-05 14:03 ` Fu Wei 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-13 0:25 ` Guenter Roeck 2015-11-20 0:11 ` Al Stone 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=CADyBb7sjZ-XcPkGqtD4Dq-V5CmXY1dSBf7RiC7VLunMBrdMvMw@mail.gmail.com \ --to=fu.wei@linaro.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=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=timur@codeaurora.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.