devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Kevin Hilman <khilman@baylibre.com>,
	Carlo Caione <carlo@caione.org>,
	devicetree@vger.kernel.org, linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	Neil Armstrong <narmstrong@baylibre.com>,
	linux-clk@vger.kernel.org
Subject: Re: [PATCH 1/4] clk: gxbb: expose i2c clocks
Date: Wed, 14 Sep 2016 11:25:06 -0700	[thread overview]
Message-ID: <20160914182506.GS7243@codeaurora.org> (raw)
In-Reply-To: <1473847568-20163-2-git-send-email-jbrunet@baylibre.com>

On 09/14, Jerome Brunet wrote:
> I2C and AO_I2C clocks are needed for the i2c driver, expose to DT
> (and comment out in clk driver)
> 
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
> ---

Acked-by: Stephen Boyd <sboyd@codeaurora.org>

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2016-09-14 18:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 10:06 [PATCH 0/4] ARM: amlogic: add i2c support to Amlogic's gxbb family Jerome Brunet
2016-09-14 10:06 ` [PATCH 1/4] clk: gxbb: expose i2c clocks Jerome Brunet
2016-09-14 18:25   ` Stephen Boyd [this message]
     [not found] ` <1473847568-20163-1-git-send-email-jbrunet-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2016-09-14 10:06   ` [PATCH 2/4] ARM64: dts: meson-gxbb: add pins for I2C Jerome Brunet
2016-09-14 10:06   ` [PATCH 3/4] ARM64: dts: meson-gxbb: add I2C nodes Jerome Brunet
2016-09-14 10:06   ` [PATCH 4/4] ARM64: dts: gxbb: add i2c bus Jerome Brunet

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=20160914182506.GS7243@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=carlo@caione.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=narmstrong@baylibre.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).