From: Rob Herring <robh@kernel.org> To: Ray Jui <ray.jui@broadcom.com> Cc: Michael Turquette <mturquette@baylibre.com>, Stephen Boyd <sboyd@kernel.org>, Mark Rutland <mark.rutland@arm.com>, linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Pramod Kumar <pramod.kumar@broadcom.com> Subject: Re: [PATCH 2/3] clk: bcm: Update and add tingray clock entries Date: Thu, 31 May 2018 11:25:56 -0500 [thread overview] Message-ID: <20180531162556.GA955@rob-hp-laptop> (raw) In-Reply-To: <1527266717-8406-3-git-send-email-ray.jui@broadcom.com> On Fri, May 25, 2018 at 09:45:16AM -0700, Ray Jui wrote: > Update and add Stingray clock definitions and tables so they match the > binding document and the latest ASIC datasheet > > Signed-off-by: Pramod Kumar <pramod.kumar@broadcom.com> > Signed-off-by: Ray Jui <ray.jui@broadcom.com> > --- > drivers/clk/bcm/clk-sr.c | 135 ++++++++++++++++++++++++++++++++----- > include/dt-bindings/clock/bcm-sr.h | 24 +++++-- This goes in the 1st patch. > 2 files changed, 137 insertions(+), 22 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: robh@kernel.org (Rob Herring) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 2/3] clk: bcm: Update and add tingray clock entries Date: Thu, 31 May 2018 11:25:56 -0500 [thread overview] Message-ID: <20180531162556.GA955@rob-hp-laptop> (raw) In-Reply-To: <1527266717-8406-3-git-send-email-ray.jui@broadcom.com> On Fri, May 25, 2018 at 09:45:16AM -0700, Ray Jui wrote: > Update and add Stingray clock definitions and tables so they match the > binding document and the latest ASIC datasheet > > Signed-off-by: Pramod Kumar <pramod.kumar@broadcom.com> > Signed-off-by: Ray Jui <ray.jui@broadcom.com> > --- > drivers/clk/bcm/clk-sr.c | 135 ++++++++++++++++++++++++++++++++----- > include/dt-bindings/clock/bcm-sr.h | 24 +++++-- This goes in the 1st patch. > 2 files changed, 137 insertions(+), 22 deletions(-)
next prev parent reply other threads:[~2018-05-31 16:26 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-25 16:45 [PATCH 0/3] Update Broadcom Stingray clock entries Ray Jui 2018-05-25 16:45 ` Ray Jui 2018-05-25 16:45 ` [PATCH 1/3] dt-bindings: clk: Update Stingray binding doc Ray Jui 2018-05-25 16:45 ` Ray Jui 2018-05-25 16:45 ` [PATCH 2/3] clk: bcm: Update and add tingray clock entries Ray Jui 2018-05-25 16:45 ` Ray Jui 2018-05-30 23:41 ` Stephen Boyd 2018-05-30 23:41 ` Stephen Boyd 2018-05-30 23:41 ` Stephen Boyd 2018-05-30 23:41 ` Stephen Boyd 2018-05-31 0:23 ` Ray Jui 2018-05-31 0:23 ` Ray Jui 2018-05-31 16:25 ` Rob Herring [this message] 2018-05-31 16:25 ` Rob Herring 2018-06-01 17:56 ` Ray Jui 2018-06-01 17:56 ` Ray Jui 2018-06-01 19:02 ` Rob Herring 2018-06-01 19:02 ` Rob Herring 2018-06-02 0:47 ` Ray Jui 2018-06-02 0:47 ` Ray Jui 2018-05-25 16:45 ` [PATCH 3/3] arm64: dts: Update Stingray clock DT nodes Ray Jui 2018-05-25 16:45 ` Ray Jui
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=20180531162556.GA955@rob-hp-laptop \ --to=robh@kernel.org \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=devicetree@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-clk@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=mturquette@baylibre.com \ --cc=pramod.kumar@broadcom.com \ --cc=ray.jui@broadcom.com \ --cc=sboyd@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: 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.