From: "H. Nikolaus Schaller" <hns@goldelico.com> To: "Benoît Cousson" <bcousson@baylibre.com>, "Tony Lindgren" <tony@atomide.com>, "Rob Herring" <robh+dt@kernel.org>, "Adam Ford" <aford173@gmail.com>, "André Roth" <neolynx@gmail.com>, "Mark Rutland" <mark.rutland@arm.com>, "Rafael J. Wysocki" <rjw@rjwysocki.net>, "Viresh Kumar" <viresh.kumar@linaro.org>, "Enric Balletbo i Serra" <eballetbo@gmail.com>, "Javier Martinez Canillas" <javier@dowhile0.org>, "Roger Quadros" <rogerq@ti.com>, "Teresa Remmet" <t.remmet@phytec.de>, "H. Nikolaus Schaller" <hns@goldelico.com> Cc: linux-omap@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, letux-kernel@openphoenux.org, kernel@pyra-handheld.com, linux-arm-kernel@lists.infradead.org Subject: [PATCH v3 7/8] cpufreq: ti-cpufreq: Add support for AM3517 Date: Wed, 11 Sep 2019 19:47:13 +0200 [thread overview] Message-ID: <beda9274922c0fdc293a974a707426fac7c77921.1568224033.git.hns@goldelico.com> (raw) In-Reply-To: <cover.1568224032.git.hns@goldelico.com> From: Adam Ford <aford173@gmail.com> The AM3517 only lists 600MHz @ 1.2V, but the register values for 0x4830A204 = 1b86 802f, it seems like am3517 might be a derivative of the omap36 which OPPs would be OPP50 (300 MHz) and OPP100 (600 MHz). This patch simply adds the am3517 to the compatible table similar to a mix of the omap3430 and omap3430 structure. Signed-off-by: Adam Ford <aford173@gmail.com> Tested-by: Adam Ford <aford173@gmail.com> Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com> --- drivers/cpufreq/ti-cpufreq.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/drivers/cpufreq/ti-cpufreq.c b/drivers/cpufreq/ti-cpufreq.c index f4704f9033e0..cd2f6b87ea3e 100644 --- a/drivers/cpufreq/ti-cpufreq.c +++ b/drivers/cpufreq/ti-cpufreq.c @@ -177,6 +177,21 @@ static struct ti_cpufreq_soc_data omap36xx_soc_data = { .multi_regulator = true, }; +/* + * AM3517 is quite similar to AM/DM37x except that it has no + * high speed grade eFuse and no abb ldo + */ + +static struct ti_cpufreq_soc_data am3517_soc_data = { + .efuse_xlate = omap3_efuse_xlate, + .efuse_offset = OMAP3_CONTROL_DEVICE_STATUS - OMAP3_SYSCON_BASE, + .efuse_shift = 0, + .efuse_mask = 0, + .rev_offset = OMAP3_CONTROL_IDCODE - OMAP3_SYSCON_BASE, + .multi_regulator = false, +}; + + /** * ti_cpufreq_get_efuse() - Parse and return efuse value present on SoC * @opp_data: pointer to ti_cpufreq_data context @@ -274,6 +289,7 @@ static int ti_cpufreq_setup_syscon_register(struct ti_cpufreq_data *opp_data) static const struct of_device_id ti_cpufreq_of_match[] = { { .compatible = "ti,am33xx", .data = &am3x_soc_data, }, + { .compatible = "ti,am3517", .data = &am3517_soc_data, }, { .compatible = "ti,am43", .data = &am4x_soc_data, }, { .compatible = "ti,dra7", .data = &dra7_soc_data }, { .compatible = "ti,omap34xx", .data = &omap34xx_soc_data, }, -- 2.19.1
WARNING: multiple messages have this Message-ID (diff)
From: "H. Nikolaus Schaller" <hns@goldelico.com> To: "Benoît Cousson" <bcousson@baylibre.com>, "Tony Lindgren" <tony@atomide.com>, "Rob Herring" <robh+dt@kernel.org>, "Adam Ford" <aford173@gmail.com>, "André Roth" <neolynx@gmail.com>, "Mark Rutland" <mark.rutland@arm.com>, "Rafael J. Wysocki" <rjw@rjwysocki.net>, "Viresh Kumar" <viresh.kumar@linaro.org>, "Enric Balletbo i Serra" <eballetbo@gmail.com>, "Javier Martinez Canillas" <javier@dowhile0.org>, "Roger Quadros" <rogerq@ti.com>, "Teresa Remmet" <t.remmet@phytec.de>, "H. Nikolaus Schaller" <hns@goldelico.com> Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@pyra-handheld.com, letux-kernel@openphoenux.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH v3 7/8] cpufreq: ti-cpufreq: Add support for AM3517 Date: Wed, 11 Sep 2019 19:47:13 +0200 [thread overview] Message-ID: <beda9274922c0fdc293a974a707426fac7c77921.1568224033.git.hns@goldelico.com> (raw) In-Reply-To: <cover.1568224032.git.hns@goldelico.com> From: Adam Ford <aford173@gmail.com> The AM3517 only lists 600MHz @ 1.2V, but the register values for 0x4830A204 = 1b86 802f, it seems like am3517 might be a derivative of the omap36 which OPPs would be OPP50 (300 MHz) and OPP100 (600 MHz). This patch simply adds the am3517 to the compatible table similar to a mix of the omap3430 and omap3430 structure. Signed-off-by: Adam Ford <aford173@gmail.com> Tested-by: Adam Ford <aford173@gmail.com> Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com> --- drivers/cpufreq/ti-cpufreq.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/drivers/cpufreq/ti-cpufreq.c b/drivers/cpufreq/ti-cpufreq.c index f4704f9033e0..cd2f6b87ea3e 100644 --- a/drivers/cpufreq/ti-cpufreq.c +++ b/drivers/cpufreq/ti-cpufreq.c @@ -177,6 +177,21 @@ static struct ti_cpufreq_soc_data omap36xx_soc_data = { .multi_regulator = true, }; +/* + * AM3517 is quite similar to AM/DM37x except that it has no + * high speed grade eFuse and no abb ldo + */ + +static struct ti_cpufreq_soc_data am3517_soc_data = { + .efuse_xlate = omap3_efuse_xlate, + .efuse_offset = OMAP3_CONTROL_DEVICE_STATUS - OMAP3_SYSCON_BASE, + .efuse_shift = 0, + .efuse_mask = 0, + .rev_offset = OMAP3_CONTROL_IDCODE - OMAP3_SYSCON_BASE, + .multi_regulator = false, +}; + + /** * ti_cpufreq_get_efuse() - Parse and return efuse value present on SoC * @opp_data: pointer to ti_cpufreq_data context @@ -274,6 +289,7 @@ static int ti_cpufreq_setup_syscon_register(struct ti_cpufreq_data *opp_data) static const struct of_device_id ti_cpufreq_of_match[] = { { .compatible = "ti,am33xx", .data = &am3x_soc_data, }, + { .compatible = "ti,am3517", .data = &am3517_soc_data, }, { .compatible = "ti,am43", .data = &am4x_soc_data, }, { .compatible = "ti,dra7", .data = &dra7_soc_data }, { .compatible = "ti,omap34xx", .data = &omap34xx_soc_data, }, -- 2.19.1 _______________________________________________ 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-09-11 17:47 UTC|newest] Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-09-11 17:47 [PATCH v3 0/8] OMAP3: convert opp-v1 to opp-v2 and read speed binned / 720MHz grade bits H. Nikolaus Schaller 2019-09-11 17:47 ` H. Nikolaus Schaller 2019-09-11 17:47 ` [PATCH v3 1/8] cpufreq: ti-cpufreq: add support for omap34xx and omap36xx H. Nikolaus Schaller 2019-09-11 17:47 ` H. Nikolaus Schaller 2019-09-11 17:47 ` H. Nikolaus Schaller 2019-09-11 19:05 ` Adam Ford 2019-09-11 19:05 ` Adam Ford 2019-09-11 19:05 ` Adam Ford 2019-09-11 17:47 ` [PATCH v3 2/8] ARM: dts: omap34xx & omap36xx: replace opp-v1 tables by opp-v2 for H. Nikolaus Schaller 2019-09-11 17:47 ` H. Nikolaus Schaller 2019-09-11 17:47 ` [PATCH v3 3/8] DTS: bindings: omap: update bindings documentation H. Nikolaus Schaller 2019-09-11 17:47 ` H. Nikolaus Schaller 2019-09-11 17:47 ` H. Nikolaus Schaller 2019-09-11 17:47 ` [PATCH v3 4/8] ARM: dts: omap3: bulk convert compatible to be explicitly ti,omap3430 or ti,omap3630 or ti,am3517 H. Nikolaus Schaller 2019-09-11 17:47 ` [PATCH v3 4/8] ARM: dts: omap3: bulk convert compatible to be explicitly ti, omap3430 or ti, omap3630 or ti, am3517 H. Nikolaus Schaller 2019-09-11 17:47 ` [PATCH v3 5/8] cpufreq: ti-cpufreq: omap36xx use "cpu0","vbb" if run in multi_regulator mode H. Nikolaus Schaller 2019-09-11 17:47 ` [PATCH v3 5/8] cpufreq: ti-cpufreq: omap36xx use "cpu0", "vbb" " H. Nikolaus Schaller 2019-09-16 16:24 ` [PATCH v3 5/8] cpufreq: ti-cpufreq: omap36xx use "cpu0","vbb" " Tony Lindgren 2019-09-16 16:24 ` [PATCH v3 5/8] cpufreq: ti-cpufreq: omap36xx use "cpu0", "vbb" " Tony Lindgren 2019-09-17 19:22 ` [PATCH v3 5/8] cpufreq: ti-cpufreq: omap36xx use "cpu0","vbb" " Rob Herring 2019-09-17 19:22 ` [PATCH v3 5/8] cpufreq: ti-cpufreq: omap36xx use "cpu0", "vbb" " Rob Herring 2019-09-17 19:22 ` [PATCH v3 5/8] cpufreq: ti-cpufreq: omap36xx use "cpu0","vbb" " Rob Herring 2019-09-11 17:47 ` [PATCH v3 6/8] ARM: dts: omap36xx: using OPP1G needs to control the abb_ldo H. Nikolaus Schaller 2019-09-11 17:47 ` H. Nikolaus Schaller 2019-09-13 21:13 ` Adam Ford 2019-09-13 21:13 ` Adam Ford 2019-09-14 9:30 ` H. Nikolaus Schaller 2019-09-14 9:30 ` H. Nikolaus Schaller 2019-09-16 16:25 ` Tony Lindgren 2019-09-16 16:25 ` Tony Lindgren 2019-09-11 17:47 ` H. Nikolaus Schaller [this message] 2019-09-11 17:47 ` [PATCH v3 7/8] cpufreq: ti-cpufreq: Add support for AM3517 H. Nikolaus Schaller 2019-09-16 16:26 ` Tony Lindgren 2019-09-16 16:26 ` Tony Lindgren 2019-09-11 17:47 ` [PATCH v3 8/8] ARM: dts: Add OPP-V2 table " H. Nikolaus Schaller 2019-09-11 17:47 ` H. Nikolaus Schaller 2019-09-16 16:26 ` Tony Lindgren 2019-09-16 16:26 ` Tony Lindgren 2019-09-16 16:28 ` [PATCH v3 0/8] OMAP3: convert opp-v1 to opp-v2 and read speed binned / 720MHz grade bits Tony Lindgren 2019-09-16 16:28 ` Tony Lindgren 2019-09-17 14:35 ` H. Nikolaus Schaller 2019-09-17 14:35 ` H. Nikolaus Schaller 2019-10-02 5:47 ` H. Nikolaus Schaller 2019-10-02 5:47 ` H. Nikolaus Schaller 2019-10-02 5:47 ` H. Nikolaus Schaller 2019-10-02 9:00 ` Viresh Kumar 2019-10-02 9:00 ` Viresh Kumar 2019-10-02 9:00 ` Viresh Kumar 2019-10-10 10:45 ` Viresh Kumar 2019-10-10 10:45 ` Viresh Kumar 2019-11-08 20:08 ` Adam Ford 2019-11-08 20:08 ` Adam Ford 2019-11-09 6:12 ` H. Nikolaus Schaller 2019-11-09 6:12 ` H. Nikolaus Schaller 2019-11-09 6:12 ` H. Nikolaus Schaller 2019-11-09 10:02 ` Adam Ford 2019-11-09 10:02 ` Adam Ford 2019-11-09 10:02 ` Adam Ford
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=beda9274922c0fdc293a974a707426fac7c77921.1568224033.git.hns@goldelico.com \ --to=hns@goldelico.com \ --cc=aford173@gmail.com \ --cc=bcousson@baylibre.com \ --cc=devicetree@vger.kernel.org \ --cc=eballetbo@gmail.com \ --cc=javier@dowhile0.org \ --cc=kernel@pyra-handheld.com \ --cc=letux-kernel@openphoenux.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=neolynx@gmail.com \ --cc=rjw@rjwysocki.net \ --cc=robh+dt@kernel.org \ --cc=rogerq@ti.com \ --cc=t.remmet@phytec.de \ --cc=tony@atomide.com \ --cc=viresh.kumar@linaro.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: linkBe 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.