From: Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Florian Fainelli
<f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Markus Mayer <code-7CzEARzsJhSsTnJN9+BGXg@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Gregory Fong
<gregory.0xf0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Markus Mayer <mmayer-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
Broadcom Kernel List
<bcm-kernel-feedback-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
Device Tree List
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
ARM Kernel List
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2 2/2] soc: brcmstb: Add driver for DPFE
Date: Wed, 21 Jun 2017 14:01:32 -0700 [thread overview]
Message-ID: <ff00e06e-d4b4-a42c-6f6a-5f2f2b5df1b8@gmail.com> (raw)
In-Reply-To: <a59aab64-b351-2e16-a5ab-b2ac41ffbf5e-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 06/21/2017 02:00 PM, Florian Fainelli wrote:
> On 06/14/2017 02:32 PM, Florian Fainelli wrote:
>> On 06/14/2017 09:34 AM, Markus Mayer wrote:
>>> On 13 June 2017 at 17:03, Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>>> Hi Markus,
>>>>
>>>> On 06/13/2017 03:37 PM, Markus Mayer wrote:
>>>>> From: Markus Mayer <mmayer-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
>>>>>
>>>>> 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-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
>>>>> ---
>>>>> 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-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
>>>>> +M: bcm-kernel-feedback-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org
>>>>> +L: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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!
>
> Can you respin a v2 with the MAINTAINERS file as well as the downstream
> kernel fixes that implement suspend/resume support?
Never mind, I grepped for the wrong thing, applied
--
Florian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-06-21 21:01 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
[not found] ` <CANEuBv6YEoTBBzPA5fkrveD05RZNtTBTak-qmxz7BvnrED5pbg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-21 20:44 ` Florian Fainelli
[not found] ` <20170613223710.31719-2-code-7CzEARzsJhSsTnJN9+BGXg@public.gmane.org>
2017-06-21 21:02 ` Florian Fainelli
2017-06-13 22:37 ` [PATCH v2 2/2] soc: brcmstb: Add driver for DPFE Markus Mayer
[not found] ` <20170613223710.31719-3-code-7CzEARzsJhSsTnJN9+BGXg@public.gmane.org>
2017-06-14 0:03 ` Florian Fainelli
[not found] ` <5b79dee6-bb84-30b3-1bb2-287b24d42534-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-06-14 16:34 ` Markus Mayer
[not found] ` <CANEuBv6N3TTNzSuDQXk-eiEV_fvGtVJZhdWUO_XdgPj6+j7q5A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-14 21:32 ` Florian Fainelli
2017-06-21 21:00 ` Florian Fainelli
[not found] ` <a59aab64-b351-2e16-a5ab-b2ac41ffbf5e-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-06-21 21:01 ` Florian Fainelli [this message]
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=ff00e06e-d4b4-a42c-6f6a-5f2f2b5df1b8@gmail.com \
--to=f.fainelli-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=bcm-kernel-feedback-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=code-7CzEARzsJhSsTnJN9+BGXg@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=gregory.0xf0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=mmayer-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).