From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: myungjoo.ham@samsung.com, kyungmin.park@samsung.com,
rafael.j.wysocki@intel.com, nm@ti.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] devfreq: exynos4: Support devicetree to get device id of Exynos4 SoC
Date: Wed, 12 Mar 2014 15:37:24 +0100 [thread overview]
Message-ID: <1794344.yC40yetU2h@amdc1032> (raw)
In-Reply-To: <1394624882-2989-2-git-send-email-cw00.choi@samsung.com>
Hi Chanwoo,
On Wednesday, March 12, 2014 08:47:59 PM Chanwoo Choi wrote:
> This patch support DT(DeviceTree) method to probe exynos4_bus and get device
> id of each Exynos4 SoC by using dt helper function.
>
> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
> ---
> drivers/devfreq/exynos/exynos4_bus.c | 26 +++++++++++++++++++++++++-
> 1 file changed, 25 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/devfreq/exynos/exynos4_bus.c b/drivers/devfreq/exynos/exynos4_bus.c
> index e07b0c6..168a7c6 100644
> --- a/drivers/devfreq/exynos/exynos4_bus.c
> +++ b/drivers/devfreq/exynos/exynos4_bus.c
> @@ -23,6 +23,7 @@
> #include <linux/devfreq.h>
> #include <linux/platform_device.h>
> #include <linux/regulator/consumer.h>
> +#include <linux/of.h>
> #include <linux/module.h>
>
> /* Exynos4 ASV has been in the mailing list, but not upstreamed, yet. */
> @@ -1017,6 +1018,28 @@ unlock:
> return NOTIFY_DONE;
> }
>
> +static struct of_device_id exynos4_busfreq_id_match[] = {
> + {
> + .compatible = "samsung,exynos4210-busfreq",
> + .data = (void *)TYPE_BUSF_EXYNOS4210,
> + }, {
> + .compatible = "samsung,exynos4x12-busfreq",
> + .data = (void *)TYPE_BUSF_EXYNOS4x12,
> + },
> +};
> +
> +static int exynos4_busfreq_get_driver_data(struct platform_device *pdev)
> +{
> + struct device *dev = &pdev->dev;
> + const struct of_device_id *match;
> +
> + match = of_match_node(exynos4_busfreq_id_match, dev->of_node);
> + if (!match)
> + return -ENODEV;
> +
> + return (int) match->data;
> +}
> +
> static int exynos4_busfreq_probe(struct platform_device *pdev)
> {
> struct busfreq_data *data;
> @@ -1030,7 +1053,7 @@ static int exynos4_busfreq_probe(struct platform_device *pdev)
> return -ENOMEM;
> }
>
> - data->type = pdev->id_entry->driver_data;
> + data->type = exynos4_busfreq_get_driver_data(pdev);
> data->dmc[0].hw_base = S5P_VA_DMC0;
> data->dmc[1].hw_base = S5P_VA_DMC1;
> data->pm_notifier.notifier_call = exynos4_busfreq_pm_notifier_event;
> @@ -1135,6 +1158,7 @@ static struct platform_driver exynos4_busfreq_driver = {
> .name = "exynos4-busfreq",
> .owner = THIS_MODULE,
> .pm = &exynos4_busfreq_pm,
> + .of_match_table = exynos4_busfreq_id_match,
> },
> };
It looks OK but it would be good to also add bindings documentation file,
i.e. Documentation/devicetree/bindings/devfreq/exynos4_bus.txt.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2014-03-12 14:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 11:47 [PATCH 0/4] devfreq: exynos4: Support dt and use common ppmu driver Chanwoo Choi
2014-03-12 11:47 ` [PATCH 1/4] devfreq: exynos4: Support devicetree to get device id of Exynos4 SoC Chanwoo Choi
2014-03-12 14:37 ` Bartlomiej Zolnierkiewicz [this message]
2014-03-13 2:16 ` Chanwoo Choi
2014-03-12 11:48 ` [PATCH 2/4] devfreq: exynos4: Use common ppmu driver and get ppmu address from dt data Chanwoo Choi
2014-03-12 14:57 ` Bartlomiej Zolnierkiewicz
2014-03-12 11:48 ` [PATCH 3/4] devfreq: exynos4: Add ppmu's clock control and code clean about regulator control Chanwoo Choi
2014-03-12 15:17 ` Bartlomiej Zolnierkiewicz
2014-03-13 2:15 ` Chanwoo Choi
2014-03-13 4:20 ` Chanwoo Choi
2014-03-12 11:48 ` [PATCH 4/4] devfreq: exynos4: Use SET_SYSTEM_SLEEP_PM_OPS macro instead of legacy method Chanwoo Choi
2014-03-12 15:22 ` Bartlomiej Zolnierkiewicz
2014-03-12 15:35 ` [PATCH 0/4] devfreq: exynos4: Support dt and use common ppmu driver Bartlomiej Zolnierkiewicz
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=1794344.yC40yetU2h@amdc1032 \
--to=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=nm@ti.com \
--cc=rafael.j.wysocki@intel.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