From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] soc: bcm: brcmstb: pm: Add support for newer rev B3.0 controllers
Date: Mon, 4 Jun 2018 14:16:22 -0700 [thread overview]
Message-ID: <23b65eba-89ee-75e6-589a-deb2cd2ff2d2@gmail.com> (raw)
In-Reply-To: <20180522223024.GA7817@rob-hp-laptop>
On 05/22/2018 03:30 PM, Rob Herring wrote:
> On Fri, May 11, 2018 at 03:02:41PM -0700, Florian Fainelli wrote:
>> From: Doug Berger <opendmb@gmail.com>
>>
>> Update the Device Tree binding document and add a matching entry for the
>> MEMC DDR controller revision B3.0 which is found on chips like 7278A0
>> and newer.
>>
>> Signed-off-by: Doug Berger <opendmb@gmail.com>
>> [florian: tweak commit message, make it apply to upstream kernel]
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>> ---
>> Documentation/devicetree/bindings/arm/bcm/brcm,brcmstb.txt | 1 +
>> drivers/soc/bcm/brcmstb/pm/pm-arm.c | 4 ++++
>> 2 files changed, 5 insertions(+)
>
> Reviewed-by: Rob Herring <robh@kernel.org>
>
> Side note: this should really move out of bindings/arm/ to
> bindings/memory-controllers/ or at least to its own file.
Good idea, thanks, will do that.
--
--
Florian
next prev parent reply other threads:[~2018-06-04 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 22:02 [PATCH 0/2] soc: bcm: brcmstb: Updates to support newer controllers Florian Fainelli
2018-05-11 22:02 ` [PATCH 1/2] soc: bcm: brcmstb: pm: Add support for newer rev B3.0 controllers Florian Fainelli
2018-05-22 22:30 ` Rob Herring
2018-06-04 21:16 ` Florian Fainelli [this message]
2018-06-04 21:15 ` Florian Fainelli
2018-05-11 22:02 ` [PATCH 2/2] soc: bcm: brcmstb: Add missing DDR MEMC compatible strings Florian Fainelli
2018-05-22 22:31 ` Rob Herring
2018-06-04 21:15 ` Florian Fainelli
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=23b65eba-89ee-75e6-589a-deb2cd2ff2d2@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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: 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