From: "Andreas Färber" <afaerber@suse.de>
To: linux-samsung-soc@vger.kernel.org, Kukjin Kim <kgene.kim@samsung.com>
Cc: Tarek Dakhran <t.dakhran@samsung.com>,
Kevin Hilman <khilman@linaro.org>,
Ben Dooks <ben-linux@fluff.org>, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
"ARM/SAMSUNG ARM A..." <linux-arm-kernel@lists.infradead.org>,
"OPEN FIRMWARE AND..." <devicetree@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: exynos5410: Fill in CPU clock-frequency
Date: Fri, 04 Jul 2014 13:32:09 +0200 [thread overview]
Message-ID: <53B690B9.2090906@suse.de> (raw)
In-Reply-To: <53A7DCF8.4090108@samsung.com>
Am 23.06.2014 09:53, schrieb Tarek Dakhran:
> On 06/22/2014 11:49 PM, Andreas Färber wrote:
>> It's 1.6 GHz for the Cortex-A15.
>>
>> Avoids warnings like "/cpus/cpu@0 missing clock-frequency property".
>>
>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>> ---
>> arch/arm/boot/dts/exynos5410.dtsi | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/exynos5410.dtsi
>> b/arch/arm/boot/dts/exynos5410.dtsi
>> index 3839c26..9d0b8cc 100644
>> --- a/arch/arm/boot/dts/exynos5410.dtsi
>> +++ b/arch/arm/boot/dts/exynos5410.dtsi
>> @@ -28,24 +28,28 @@
>> device_type = "cpu";
>> compatible = "arm,cortex-a15";
>> reg = <0x0>;
>> + clock-frequency = <1600000000>;
>>
>
> Reviewed-by: Tarek Dakhran<t.dakhran@samsung.com>
Ping? Seems really trivial...
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-07-04 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 19:49 [PATCH] ARM: dts: exynos5410: Fill in CPU clock-frequency Andreas Färber
2014-06-23 7:53 ` Tarek Dakhran
2014-07-04 11:32 ` Andreas Färber [this message]
2014-07-04 21:06 ` Kukjin Kim
2014-07-15 12:57 ` Andreas Färber
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=53B690B9.2090906@suse.de \
--to=afaerber@suse.de \
--cc=ben-linux@fluff.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kgene.kim@samsung.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=t.dakhran@samsung.com \
/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).