From: Rob Herring <robh@kernel•org>
To: Leonard Crestez <leonard.crestez@nxp•com>
Cc: "Mark Rutland" <mark.rutland@arm•com>,
"Artur Świgoń" <a.swigon@partner•samsung.com>,
"Jacky Bai" <ping.bai@nxp•com>,
"Viresh Kumar" <viresh.kumar@linaro•org>,
"Michael Turquette" <mturquette@baylibre•com>,
"Angus Ainslie" <angus@akkea•ca>,
"Alexandre Bailon" <abailon@baylibre•com>,
"Matthias Kaehlcke" <mka@chromium•org>,
"Abel Vesa" <abel.vesa@nxp•com>,
"Saravana Kannan" <saravanak@google•com>,
"Krzysztof Kozlowski" <krzk@kernel•org>,
"linux-clk@vger•kernel.org" <linux-clk@vger•kernel.org>,
"Chanwoo Choi" <cw00.choi@samsung•com>,
"MyungJoo Ham" <myungjoo.ham@samsung•com>,
dl-linux-imx <linux-imx@nxp•com>,
"devicetree@vger•kernel.org" <devicetree@vger•kernel.org>,
"linux-pm@vger•kernel.org" <linux-pm@vger•kernel.org>,
"Martin Kepplinger" <martink@posteo•de>,
"linux-arm-kernel@lists•infradead.org"
<linux-arm-kernel@lists•infradead.org>,
"Aisheng Dong" <aisheng.dong@nxp•com>,
"Anson Huang" <anson.huang@nxp•com>,
"Stephen Boyd" <sboyd@kernel•org>,
"Rafael J. Wysocki" <rjw@rjwysocki•net>,
"Kyungmin Park" <kyungmin.park@samsung•com>,
"kernel@pengutronix•de" <kernel@pengutronix•de>,
"Fabio Estevam" <fabio.estevam@nxp•com>,
"Shawn Guo" <shawnguo@kernel•org>,
"Georgi Djakov" <georgi.djakov@linaro•org>
Subject: Re: [PATCH v3 3/6] dt-bindings: devfreq: Add bindings for imx ddr controller
Date: Tue, 5 Nov 2019 14:13:02 -0600 [thread overview]
Message-ID: <20191105201302.GA4772@bogus> (raw)
In-Reply-To: <VI1PR04MB7023F375AEDC4549FA12247FEE7E0@VI1PR04MB7023.eurprd04.prod.outlook.com>
On Tue, Nov 05, 2019 at 07:25:57PM +0000, Leonard Crestez wrote:
> On 05.11.2019 00:21, Rob Herring wrote:
> > On Thu, Oct 31, 2019 at 11:50:24PM +0200, Leonard Crestez wrote:
> >> Add devicetree bindings for the i.MX DDR Controller on imx8m series
> >> chips. It supports dynamic frequency switching between multiple data
> >> rates and this is exposed to Linux via the devfreq subsystem.
> >>
> >> Signed-off-by: Leonard Crestez <leonard.crestez@nxp•com>
> >> ---
> >> .../devicetree/bindings/devfreq/imx-ddrc.yaml | 60 +++++++++++++++++++
> >
> > .../bindings/memory-controllers/
>
> Okay, but I'm not sure about the rules here. Usually there is a 1:1
> mapping between subsystems and bindings directory but I guess devfreq is
> odd since it's not really a physical class of device.
Mostly true, but it's not completely 1:1.
> I saw there is also a drivers/memory and there is already a
> devfreq-using driver in there (EXYNOS5422_DMC).
Yeah, well it's been a while since I last tried to clean up locations of
things. DDR controller bindings are not in the best shape.
> It's not clear if my driver fits in there; as far as I can see the only
> "core" functionality in drivers/memory is parsing DDR timings from DTS
> but for imx8m this is all controlled in firmware.
You shouldn't have to think about that. Bindings should be for DDR
controllers regardless of whether there's a driver for devfreq, EDAC,
perf, or ??? or all of those.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-05 20:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 21:50 [PATCH v3 0/6] PM / devfreq: Add dynamic scaling for imx ddr controller Leonard Crestez
2019-10-31 21:50 ` [PATCH v3 1/6] clk: imx8m: Set CLK_GET_RATE_NOCACHE on dram clocks Leonard Crestez
2019-12-02 3:12 ` Shawn Guo
2019-12-02 4:19 ` Leonard Crestez
2019-10-31 21:50 ` [PATCH v3 2/6] clk: imx: Mark dram pll on 8mm and 8mn with CLK_GET_RATE_NOCACHE Leonard Crestez
2019-10-31 21:50 ` [PATCH v3 3/6] dt-bindings: devfreq: Add bindings for imx ddr controller Leonard Crestez
2019-11-04 22:21 ` Rob Herring
2019-11-05 19:25 ` Leonard Crestez
2019-11-05 20:13 ` Rob Herring [this message]
2019-10-31 21:50 ` [PATCH v3 4/6] PM / devfreq: Add dynamic scaling " Leonard Crestez
2019-12-02 5:38 ` Shawn Guo
2019-12-02 9:12 ` Leonard Crestez
2019-12-02 13:34 ` Shawn Guo
2019-10-31 21:50 ` [PATCH v3 5/6] PM / devfreq: imx-ddrc: Measure bandwidth with perf Leonard Crestez
2019-10-31 21:50 ` [PATCH v3 6/6] arm64: dts: imx8m: Add ddr controller nodes Leonard Crestez
2019-11-04 22:01 ` Rob Herring
2019-11-11 14:29 ` Leonard Crestez
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=20191105201302.GA4772@bogus \
--to=robh@kernel$(echo .)org \
--cc=a.swigon@partner$(echo .)samsung.com \
--cc=abailon@baylibre$(echo .)com \
--cc=abel.vesa@nxp$(echo .)com \
--cc=aisheng.dong@nxp$(echo .)com \
--cc=angus@akkea$(echo .)ca \
--cc=anson.huang@nxp$(echo .)com \
--cc=cw00.choi@samsung$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=fabio.estevam@nxp$(echo .)com \
--cc=georgi.djakov@linaro$(echo .)org \
--cc=kernel@pengutronix$(echo .)de \
--cc=krzk@kernel$(echo .)org \
--cc=kyungmin.park@samsung$(echo .)com \
--cc=leonard.crestez@nxp$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-clk@vger$(echo .)kernel.org \
--cc=linux-imx@nxp$(echo .)com \
--cc=linux-pm@vger$(echo .)kernel.org \
--cc=mark.rutland@arm$(echo .)com \
--cc=martink@posteo$(echo .)de \
--cc=mka@chromium$(echo .)org \
--cc=mturquette@baylibre$(echo .)com \
--cc=myungjoo.ham@samsung$(echo .)com \
--cc=ping.bai@nxp$(echo .)com \
--cc=rjw@rjwysocki$(echo .)net \
--cc=saravanak@google$(echo .)com \
--cc=sboyd@kernel$(echo .)org \
--cc=shawnguo@kernel$(echo .)org \
--cc=viresh.kumar@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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