linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] soc: brcmstb: Add driver for DPFE
Date: Wed, 14 Jun 2017 14:32:54 -0700	[thread overview]
Message-ID: <79cb33fc-cc6a-e79c-5e5c-af632e20dc76@gmail.com> (raw)
In-Reply-To: <CANEuBv6N3TTNzSuDQXk-eiEV_fvGtVJZhdWUO_XdgPj6+j7q5A@mail.gmail.com>

On 06/14/2017 09:34 AM, Markus Mayer wrote:
> On 13 June 2017 at 17:03, Florian Fainelli <f.fainelli@gmail.com> wrote:
>> Hi Markus,
>>
>> On 06/13/2017 03:37 PM, Markus Mayer wrote:
>>> From: Markus Mayer <mmayer@broadcom.com>
>>>
>>> This driver allows access to DRAM properties, such as the refresh rate,
>>> via the Broadcom STB DDR PHY Front End (DPFE). The refresh rate can be
>>> used as indirect indicator of the DRAM temperature.
>>>
>>> The driver also allows setting of the sampling interval.
>>>
>>> Signed-off-by: Markus Mayer <mmayer@broadcom.com>
>>> ---
>>>  MAINTAINERS                      |   8 +
>>>  drivers/soc/bcm/brcmstb/Makefile |   2 +-
>>>  drivers/soc/bcm/brcmstb/dpfe.c   | 689 +++++++++++++++++++++++++++++++++++++++
>>>  3 files changed, 698 insertions(+), 1 deletion(-)
>>>  create mode 100644 drivers/soc/bcm/brcmstb/dpfe.c
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index f7d568b..04f0be6 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -2864,6 +2864,14 @@ S:     Maintained
>>>  F:   Documentation/devicetree/bindings/cpufreq/brcm,stb-avs-cpu-freq.txt
>>>  F:   drivers/cpufreq/brcmstb*
>>>
>>> +BROADCOM STB SOC DPFE DRIVER
>>> +M:   Markus Mayer <mmayer@broadcom.com>
>>> +M:   bcm-kernel-feedback-list at broadcom.com
>>> +L:   linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
>>> +S:   Maintained
>>> +F:   Documentation/devicetree/bindings/soc/bcm/brcm,dpfe-cpu.txt
>>> +F:   drivers/misc/brcmstb-dpfe.c
>>
>> Just one nit: this should be drivers/soc/bcm/brcmstb/dpfe.c, other than
>> that, I just need an Ack from Rob on the binding, and I will queue this
>> up, thanks!
> 
> Oops. Thanks for catching that. Would you like me to re-send or will
> you fix up that path on your end?

I can fix it up if Rob is happy with the current binding, if you need to
resubmit, please fix that as well. Thanks!
-- 
-- 
Florian

  reply	other threads:[~2017-06-14 21:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 22:37 [PATCH v2 0/2] SoC driver for Broadcom STB DPFE Markus Mayer
2017-06-13 22:37 ` [PATCH v2 1/2] dt/bindings: Add bindings for Broadcom STB DRAM Sensors Markus Mayer
2017-06-18 14:05   ` Rob Herring
2017-06-19 17:26     ` Markus Mayer
2017-06-21 20:44       ` Florian Fainelli
2017-06-21 21:02   ` Florian Fainelli
2017-06-13 22:37 ` [PATCH v2 2/2] soc: brcmstb: Add driver for DPFE Markus Mayer
2017-06-14  0:03   ` Florian Fainelli
2017-06-14 16:34     ` Markus Mayer
2017-06-14 21:32       ` Florian Fainelli [this message]
2017-06-21 21:00         ` Florian Fainelli
2017-06-21 21:01           ` 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=79cb33fc-cc6a-e79c-5e5c-af632e20dc76@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;
as well as URLs for NNTP newsgroup(s).