All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Eric Anholt <eric@anholt.net>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Ray Jui <rjui@broadcom.com>, Rob Herring <robh+dt@kernel.org>,
	Scott Branden <sbranden@broadcom.com>,
	Stefan Wahren <wahrenst@gmx.net>
Cc: linux-clk@vger.kernel.org, Stefan Wahren <wahrenst@gmx.net>
Subject: Re: [PATCH 3/4] clk: bcm2835: Add BCM2711_CLOCK_EMMC2 support
Date: Tue, 17 Sep 2019 10:16:13 -0700	[thread overview]
Message-ID: <20190917171614.A9C592053B@mail.kernel.org> (raw)
In-Reply-To: <1566145424-3186-4-git-send-email-wahrenst@gmx.net>

Quoting Stefan Wahren (2019-08-18 09:23:43)
> The new BCM2711 supports an additional clock for the emmc2 block.
> So add a new compatible and register this clock only for BCM2711.
> 
> Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
> Reviewed-by: Matthias Brugger <mbrugger@suse.com>
> Acked-by: Eric Anholt <eric@anholt.net>
> Reviewed-by: Eric Anholt <eric@anholt.net>
> ---

Applied to clk-next


  reply	other threads:[~2019-09-17 17:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-18 16:23 [PATCH 0/4] clk: bcm2835: Add bcm2711 support Stefan Wahren
2019-08-18 16:23 ` [PATCH 1/4] dt-bindings: bcm2835-cprman: " Stefan Wahren
2019-09-17 17:16   ` Stephen Boyd
2019-08-18 16:23 ` [PATCH 2/4] clk: bcm2835: Introduce SoC specific clock registration Stefan Wahren
2019-09-17 17:16   ` Stephen Boyd
2019-08-18 16:23 ` [PATCH 3/4] clk: bcm2835: Add BCM2711_CLOCK_EMMC2 support Stefan Wahren
2019-09-17 17:16   ` Stephen Boyd [this message]
2019-08-18 16:23 ` [PATCH 4/4] clk: bcm2835: Mark PLLD_PER as CRITICAL Stefan Wahren
2019-09-17 17:16   ` Stephen Boyd
2019-08-26 18:16 ` [PATCH 0/4] clk: bcm2835: Add bcm2711 support Stefan Wahren
2019-09-04 18:17   ` Stefan Wahren

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=20190917171614.A9C592053B@mail.kernel.org \
    --to=sboyd@kernel.org \
    --cc=eric@anholt.net \
    --cc=f.fainelli@gmail.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=wahrenst@gmx.net \
    /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 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.