From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Timur Tabi <timur@codeaurora.org>
Cc: fu.wei@linaro.org, lenb@kernel.org, daniel.lezcano@linaro.org,
tglx@linutronix.de, marc.zyngier@arm.com, hanjun.guo@linaro.org,
linux-arm-kernel@lists.infradead.org,
linaro-acpi@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, rruigrok@codeaurora.org,
harba@codeaurora.org, cov@codeaurora.org,
graeme.gregory@linaro.org, al.stone@linaro.org, jcm@redhat.com,
"wei@redhat.com--cc=arnd"@arndb.de, wim@iguana.be,
catalin.marinas@arm.com, will.deacon@arm.com,
Suravee.Suthikulpanit@amd.com, leo.duran@amd.com
Subject: Re: [PATCH v4 0/5] acpi, clocksource, kvm: add GTDT and ARM memory-mapped timer support
Date: Fri, 18 Mar 2016 01:41:06 +0100 [thread overview]
Message-ID: <2196518.cd4jtVChuo@vostro.rjw.lan> (raw)
In-Reply-To: <56EAC832.6070203@codeaurora.org>
On Thursday, March 17, 2016 10:07:30 AM Timur Tabi wrote:
> fu.wei@linaro.org wrote:
> > From: Fu Wei <fu.wei@linaro.org>
> >
> > This patchset:
> > (1)Move some enums and marcos to header file for arm_arch_timer,
> > improve the pr_* code by defining "pr_fmt(fmt)" in arm_arch_timer.c
> >
> > (2)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c
> > Parse all kinds of timer in GTDT table of ACPI:arch timer,
> > memory-mapped timer and SBSA Generic Watchdog timer.
> > This driver can help to simplify all the relevant timer drivers,
> > and separate all the ACPI GTDT knowledge from them.
> >
> > (3)Simplify ACPI code for arch timer in arm_arch_timer.c
> >
> > (4)Add memory-mapped timer support in arm_arch_timer.c
>
> The SBSA watchdog driver is already in watchdog-next and will be merged
> into 4.6. These five patches are necessary for the watchdog driver to
> probe on an ACPI system.
>
> I'm guessing since that v4 was posted in the middle of the 4.6 merge
> window, that these patches won't make it and we'll have to wait until
> 4.7 (at the earliest)?
First off, the last version I've seen is the v3. I must have overlooked
the v4 then, but I don't think it was CCed to linux-acpi (which should
have happened).
Second, these patches require review from multiple maintainers and (or including)
people who actually know how the GTDT is supposed to be used. I haven't
seen any responses from any of them yet, so the answer to your question is
"yes".
I will have a couple of comments for patch [1/6] (in the v3), but it's
not been a priority due to the apparent overall lack of interest in this
series.
Thanks,
Rafael
next prev parent reply other threads:[~2016-03-18 0:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1458199917-30699-1-git-send-email-fu.wei@linaro.org>
2016-03-17 15:07 ` Timur Tabi
2016-03-18 0:41 ` Rafael J. Wysocki [this message]
2016-03-18 0:55 ` Timur Tabi
2016-03-18 4:24 ` Fu Wei
2016-03-18 4:22 ` Fu Wei
2016-03-18 9:28 ` Fu Wei
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=2196518.cd4jtVChuo@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc="wei@redhat.com--cc=arnd"@arndb.de \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=al.stone@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=cov@codeaurora.org \
--cc=daniel.lezcano@linaro.org \
--cc=fu.wei@linaro.org \
--cc=graeme.gregory@linaro.org \
--cc=hanjun.guo@linaro.org \
--cc=harba@codeaurora.org \
--cc=jcm@redhat.com \
--cc=lenb@kernel.org \
--cc=leo.duran@amd.com \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=rruigrok@codeaurora.org \
--cc=tglx@linutronix.de \
--cc=timur@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
Powered by JetHome