From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Ayyathurai, Vijayakannan" <vijayakannan.ayyathurai@intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"mgross@linux.intel.com" <mgross@linux.intel.com>,
"Wan Mohamad,
Wan Ahmad Zainie" <wan.ahmad.zainie.wan.mohamad@intel.com>,
"Raja Subramanian,
Lakshmi Bai" <lakshmi.bai.raja.subramanian@intel.com>,
"Seow, Chen Yong" <chen.yong.seow@intel.com>
Subject: Re: [PATCH v2 0/2] Add drivers for Intel Keem Bay SoC timer block
Date: Mon, 18 Jan 2021 16:34:58 +0100 [thread overview]
Message-ID: <98fd451c-828e-e2e4-8462-51f9c88b6f1e@linaro.org> (raw)
In-Reply-To: <DM6PR11MB4250A1E8C1F2CA97516A2E59FBA90@DM6PR11MB4250.namprd11.prod.outlook.com>
On 13/01/2021 11:54, Ayyathurai, Vijayakannan wrote:
> Hi,
>
>> From: Vijayakannan Ayyathurai <vijayakannan.ayyathurai@intel.com>
>>
>> Changes since v1:
>> - Add support for KEEMBAY_TIMER to get selected through Kconfig.platforms.
>> - Add CLOCK_EVT_FEAT_DYNIRQ as part of clockevent feature.
>> - Avoid overlapping reg regions across 2 device nodes.
>> - Simplify 2 device nodes as 1 because both are from same IP block.
>> - Adapt the driver code according to the new simplified devicetree.
>>
>> Vijayakannan Ayyathurai (2):
>> dt-bindings: timer: Add bindings for Intel Keem Bay SoC timer
>> clocksource: Add Intel Keem Bay Timer Support
>
> Kindly help us to review this updated patch(v2) set.
Review in progress ... :)
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2021-01-18 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 6:25 [PATCH v2 0/2] Add drivers for Intel Keem Bay SoC timer block vijayakannan.ayyathurai
2020-12-30 6:25 ` [PATCH v2 1/2] dt-bindings: timer: Add bindings for Intel Keem Bay SoC timer vijayakannan.ayyathurai
2020-12-31 15:34 ` Rob Herring
2021-01-01 16:12 ` Ayyathurai, Vijayakannan
2020-12-30 6:25 ` [PATCH v2 2/2] clocksource: Add Intel Keem Bay Timer Support vijayakannan.ayyathurai
2021-01-18 15:56 ` Daniel Lezcano
2021-01-19 2:56 ` Ayyathurai, Vijayakannan
2021-01-19 8:50 ` andriy.shevchenko
2021-01-20 19:18 ` Ayyathurai, Vijayakannan
2021-01-13 10:54 ` [PATCH v2 0/2] Add drivers for Intel Keem Bay SoC timer block Ayyathurai, Vijayakannan
2021-01-18 15:34 ` Daniel Lezcano [this message]
2021-01-19 1:55 ` Ayyathurai, Vijayakannan
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=98fd451c-828e-e2e4-8462-51f9c88b6f1e@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=chen.yong.seow@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=lakshmi.bai.raja.subramanian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=vijayakannan.ayyathurai@intel.com \
--cc=wan.ahmad.zainie.wan.mohamad@intel.com \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).