mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vineet Gupta <vgupta@synopsys.com>
To: Vlad Zakharov <Vladislav.Zakharov@synopsys.com>,
	linux-snps-arc@lists.infradead.org
Cc: devicetree@vger.kernel.org, Vineet Gupta <vgupta@synopys.com>,
	linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 0/3] ARC: get frequency via clock driver instead of reading device tree
Date: Sat, 4 Mar 2017 16:07:24 -0800	[thread overview]
Message-ID: <2e9840bb-fdf4-84c3-0520-695977a46c53@synopsys.com> (raw)
In-Reply-To: <1488540602-11438-1-git-send-email-vzakhar@synopsys.com>

On 03/03/2017 03:29 AM, Vlad Zakharov wrote:
> This patch series replaces reading device tree with getting CPU
> clock frequency via clock driver in show_cpuinfo function.
> 
> In order to achieve this we also add cpu nodes to device tree which
> describes SMP system and add "clocks" properties to all ARC cpu nodes. 

Series seems sane to me - will give it a spin next week before adding for 4.11

Thx,
-Vieet


> Vlad Zakharov (3):
>   ARC: [dts] add input clocks for cpu nodes
>   ARC: [dts] add cpu nodes to ARCHS SMP device tree
>   arc: get rate from clk driver instead of reading device tree
> 
>  arch/arc/boot/dts/skeleton.dtsi        |  1 +
>  arch/arc/boot/dts/skeleton_hs.dtsi     |  1 +
>  arch/arc/boot/dts/skeleton_hs_idu.dtsi | 21 ++++++++++++++++++++-
>  arch/arc/kernel/setup.c                | 17 +++++++++++++----
>  4 files changed, 35 insertions(+), 5 deletions(-)
> 

      parent reply	other threads:[~2017-03-05  0:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 11:29 Vlad Zakharov
2017-03-03 11:30 ` [PATCH 1/3] ARC: [dts] add input clocks for cpu nodes Vlad Zakharov
2017-03-03 11:30 ` [PATCH 2/3] ARC: [dts] add cpu nodes to ARCHS SMP device tree Vlad Zakharov
2017-03-03 11:30 ` [PATCH 3/3] arc: get rate from clk driver instead of reading " Vlad Zakharov
2017-03-05  0:07 ` Vineet Gupta [this message]

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=2e9840bb-fdf4-84c3-0520-695977a46c53@synopsys.com \
    --to=vgupta@synopsys.com \
    --cc=Vladislav.Zakharov@synopsys.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=vgupta@synopys.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

all inboxes | Powered by JetHome®