From: Chanwoo Choi <cwchoi00@gmail.com>
To: Lukasz Luba <l.luba@partner.samsung.com>
Cc: devicetree <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-pm@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, b.zolnierkie@samsung.com,
krzk@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
cw00.choi@samsung.com, kyungmin.park@samsung.com,
m.szyprowski@samsung.com, s.nawrocki@samsung.com,
myungjoo.ham@samsung.com, kgene@kernel.org,
willy.mh.wolff.ml@gmail.com
Subject: Re: [PATCH v4 2/5] drivers: devfreq: events: change matching code during probe
Date: Wed, 26 Jun 2019 17:22:23 +0900 [thread overview]
Message-ID: <CAGTfZH0X7GmGWTyDZdJV_o98oCgrGR+syRD_pcby-DbOeZ3Emg@mail.gmail.com> (raw)
In-Reply-To: <20190605091236.24263-3-l.luba@partner.samsung.com>
[-- Attachment #1: Type: text/plain, Size: 4474 bytes --]
Hi Lukasz,
2019년 6월 5일 (수) 18:13, Lukasz Luba <l.luba@partner.samsung.com>님이 작성:
> The patch changes the way how the 'ops' gets populated for different
> device versions. The matching function now uses 'of_device_id' in order
> to identify the device type.
>
> Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
> ---
> drivers/devfreq/event/exynos-ppmu.c | 38 +++++++++++++++++++----------
> 1 file changed, 25 insertions(+), 13 deletions(-)
>
Acked-by: Chanwoo Choi <cw00.choi@samsung.com>
> diff --git a/drivers/devfreq/event/exynos-ppmu.c
> b/drivers/devfreq/event/exynos-ppmu.c
> index c2ea94957501..17f3c86a6f00 100644
> --- a/drivers/devfreq/event/exynos-ppmu.c
> +++ b/drivers/devfreq/event/exynos-ppmu.c
> @@ -16,6 +16,7 @@
> #include <linux/kernel.h>
> #include <linux/module.h>
> #include <linux/of_address.h>
> +#include <linux/of_device.h>
> #include <linux/platform_device.h>
> #include <linux/regmap.h>
> #include <linux/suspend.h>
> @@ -23,6 +24,11 @@
>
> #include "exynos-ppmu.h"
>
> +enum exynos_ppmu_type {
> + EXYNOS_TYPE_PPMU,
> + EXYNOS_TYPE_PPMU_V2,
> +};
> +
> struct exynos_ppmu_data {
> struct clk *clk;
> };
> @@ -36,6 +42,7 @@ struct exynos_ppmu {
> struct regmap *regmap;
>
> struct exynos_ppmu_data ppmu;
> + enum exynos_ppmu_type ppmu_type;
> };
>
> #define PPMU_EVENT(name) \
> @@ -483,31 +490,23 @@ static const struct devfreq_event_ops
> exynos_ppmu_v2_ops = {
> static const struct of_device_id exynos_ppmu_id_match[] = {
> {
> .compatible = "samsung,exynos-ppmu",
> - .data = (void *)&exynos_ppmu_ops,
> + .data = (void *)EXYNOS_TYPE_PPMU,
> }, {
> .compatible = "samsung,exynos-ppmu-v2",
> - .data = (void *)&exynos_ppmu_v2_ops,
> + .data = (void *)EXYNOS_TYPE_PPMU_V2,
> },
> { /* sentinel */ },
> };
> MODULE_DEVICE_TABLE(of, exynos_ppmu_id_match);
>
> -static struct devfreq_event_ops *exynos_bus_get_ops(struct device_node
> *np)
> -{
> - const struct of_device_id *match;
> -
> - match = of_match_node(exynos_ppmu_id_match, np);
> - return (struct devfreq_event_ops *)match->data;
> -}
> -
> static int of_get_devfreq_events(struct device_node *np,
> struct exynos_ppmu *info)
> {
> struct devfreq_event_desc *desc;
> - struct devfreq_event_ops *event_ops;
> struct device *dev = info->dev;
> struct device_node *events_np, *node;
> int i, j, count;
> + const struct of_device_id *of_id;
>
> events_np = of_get_child_by_name(np, "events");
> if (!events_np) {
> @@ -515,7 +514,6 @@ static int of_get_devfreq_events(struct device_node
> *np,
> "failed to get child node of devfreq-event
> devices\n");
> return -EINVAL;
> }
> - event_ops = exynos_bus_get_ops(np);
>
> count = of_get_child_count(events_np);
> desc = devm_kcalloc(dev, count, sizeof(*desc), GFP_KERNEL);
> @@ -523,6 +521,12 @@ static int of_get_devfreq_events(struct device_node
> *np,
> return -ENOMEM;
> info->num_events = count;
>
> + of_id = of_match_device(exynos_ppmu_id_match, dev);
> + if (of_id)
> + info->ppmu_type = (enum exynos_ppmu_type)of_id->data;
> + else
> + return -EINVAL;
> +
> j = 0;
> for_each_child_of_node(events_np, node) {
> for (i = 0; i < ARRAY_SIZE(ppmu_events); i++) {
> @@ -540,7 +544,15 @@ static int of_get_devfreq_events(struct device_node
> *np,
> continue;
> }
>
> - desc[j].ops = event_ops;
> + switch (info->ppmu_type) {
> + case EXYNOS_TYPE_PPMU:
> + desc[j].ops = &exynos_ppmu_ops;
> + break;
> + case EXYNOS_TYPE_PPMU_V2:
> + desc[j].ops = &exynos_ppmu_v2_ops;
> + break;
> + }
> +
> desc[j].driver_data = info;
>
> of_property_read_string(node, "event-name", &desc[j].name);
> --
> 2.17.1
>
>
[-- Attachment #2: Type: text/html, Size: 6084 bytes --]
next prev parent reply other threads:[~2019-06-26 8:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190605091301eucas1p278a554a15879a1b6fbc3d2bb5168f8cb@eucas1p2.samsung.com>
2019-06-05 9:12 ` [PATCH v4 0/5] Exynos Performance Monitoring Counters enhancements Lukasz Luba
[not found] ` <CGME20190605091301eucas1p2f360a867c8df8ba542942d425289f355@eucas1p2.samsung.com>
2019-06-05 9:12 ` [PATCH v4 1/5] include: dt-bindings: add Performance Monitoring Unit for Exynos Lukasz Luba
[not found] ` <CGME20190605091302eucas1p2b2a959c0889666e95bd727381bceab24@eucas1p2.samsung.com>
2019-06-05 9:12 ` [PATCH v4 2/5] drivers: devfreq: events: change matching code during probe Lukasz Luba
2019-06-26 8:22 ` Chanwoo Choi [this message]
[not found] ` <CGME20190605091303eucas1p27177d349e0f2bd37bf582dbd7266321a@eucas1p2.samsung.com>
2019-06-05 9:12 ` [PATCH v4 3/5] drivers: devfreq: events: extend events by type of counted data Lukasz Luba
2019-07-24 10:15 ` Lukasz Luba
2019-07-24 10:24 ` Chanwoo Choi
2019-07-25 16:23 ` Lukasz Luba
[not found] ` <CGME20190605091304eucas1p21e0717cafa17a14de569f1773cc7abe5@eucas1p2.samsung.com>
2019-06-05 9:12 ` [PATCH v4 4/5] Documentation: devicetree: add PPMU events description Lukasz Luba
2019-06-26 8:23 ` Chanwoo Choi
2019-06-26 13:58 ` Lukasz Luba
2019-06-26 14:03 ` Krzysztof Kozlowski
2019-06-26 14:17 ` Lukasz Luba
2019-06-27 1:11 ` Chanwoo Choi
2019-06-27 10:31 ` Lukasz Luba
[not found] ` <CGME20190605091305eucas1p136332cc3d1a299d90617bddcb365bee0@eucas1p1.samsung.com>
2019-06-05 9:12 ` [PATCH v4 5/5] DT: arm: exynos4412: add event data type which is monitored Lukasz Luba
2019-07-23 17:58 ` Krzysztof Kozlowski
2019-07-24 10:09 ` Lukasz Luba
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=CAGTfZH0X7GmGWTyDZdJV_o98oCgrGR+syRD_pcby-DbOeZ3Emg@mail.gmail.com \
--to=cwchoi00@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=l.luba@partner.samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mark.rutland@arm.com \
--cc=myungjoo.ham@samsung.com \
--cc=robh+dt@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=willy.mh.wolff.ml@gmail.com \
/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).