linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abhilash Kesavan <kesavan.abhilash@gmail.com>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Tomasz Figa <tomasz.figa@gmail.com>,
	Yadwinder Singh Brar <yadi.brar01@gmail.com>,
	"myungjoo.ham" <myungjoo.ham@samsung.com>,
	Yadwinder Singh Brar <yadi.brar@samsung.com>,
	Doug Anderson <dianders@google.com>,
	Andrew Bresticker <abrestic@google.com>
Subject: Re: [RFC v2 2/4] power: asv: Add a common ASV driver for Exynos SoCs.
Date: Tue, 3 Dec 2013 20:16:39 +0530	[thread overview]
Message-ID: <CAM4voakmcVGTHF6zHh=GrghJexPQOVGtmAFr-w7qqaeKVDEW7Q@mail.gmail.com> (raw)
In-Reply-To: <1384515691-26299-3-git-send-email-sachin.kamat@linaro.org>

Hi,

CC'ing Doug and Andrew who have also worked on ASV.

[...]

> +
> +       chip_id = of_find_compatible_node(NULL, NULL,
> +                                               "samsung,exynos4210-chipid");
> +       if (!chip_id) {
> +               pr_err("%s: unable to find chipid\n", __func__);
> +               return -ENODEV;
> +       }
> +
> +       base = of_iomap(chip_id, 0);
> +       if (!base) {
> +               dev_err(&pdev->dev, "unable to map chip_id register\n");
> +               ret = -ENOMEM;
> +               goto err_map;
> +       }
My u-boot had the chipid clock disabled and I was getting an invalid
value at 1000_0004 (0 on the SMDK5420 and 0x43520010 on the
chromebook). Maybe it would be better if we enable the chipid clock in
the driver as well.
> +
> +       exynos_asv_info->base = base;
> +
> +       /* call SoC specific intialisation routine */
> +
> +       register_asv_member(exynos_asv_info->asv_list, exynos_asv_info->nr_mem);
> +
> +       iounmap(base);
> +err_map:
> +       of_node_put(chip_id);
> +
> +       return ret;
> +}
[...]
> diff --git a/drivers/power/asv/exynos-asv.h b/drivers/power/asv/exynos-asv.h
> new file mode 100644
> index 000000000000..89a1ae8b5e19
> --- /dev/null
> +++ b/drivers/power/asv/exynos-asv.h
> @@ -0,0 +1,21 @@
> +/*
> + * Exynos - Adaptive Supply Voltage Driver Header File
> + *
> + * copyright (c) 2013 samsung electronics co., ltd.
> + *             http://www.samsung.com/
Please fix the copyright

Thanks,
Abhilash

  reply	other threads:[~2013-12-03 14:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15 11:41 [RFC v2 0/4] Add basic support for ASV Sachin Kamat
2013-11-15 11:41 ` [RFC v2 1/4] power: asv: Add common ASV support for Samsung SoCs Sachin Kamat
2013-12-03 14:46   ` Abhilash Kesavan
2013-12-15 13:38     ` Yadwinder Singh Brar
2013-12-09 18:45   ` Tomasz Figa
2013-12-15 13:30     ` Yadwinder Singh Brar
2013-12-15 13:51       ` Tomasz Figa
2013-12-26 16:28         ` Yadwinder Singh Brar
2013-11-15 11:41 ` [RFC v2 2/4] power: asv: Add a common ASV driver for Exynos SoCs Sachin Kamat
2013-12-03 14:46   ` Abhilash Kesavan [this message]
2013-11-15 11:41 ` [RFC v2 3/4] power: asv: Add support for Exynos5250 Sachin Kamat
2013-11-15 11:41 ` [RFC v2 4/4] ARM: SAMSUNG: Register static platform device for ASV for Exynos5 Sachin Kamat
     [not found] ` <CAJ0PZbS8FxRA_sPTOnWbZcNfUMp=k5Jf_tZHLg1fh6gsAGJ=Gw@mail.gmail.com>
2013-11-18  4:07   ` [RFC v2 0/4] Add basic support for ASV Sachin Kamat
2013-12-03 14:46     ` Abhilash Kesavan
2013-12-04  6:00       ` Sachin Kamat
2015-01-13 16:19         ` Kevin Hilman

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='CAM4voakmcVGTHF6zHh=GrghJexPQOVGtmAFr-w7qqaeKVDEW7Q@mail.gmail.com' \
    --to=kesavan.abhilash@gmail.com \
    --cc=abrestic@google.com \
    --cc=dianders@google.com \
    --cc=kgene.kim@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=myungjoo.ham@samsung.com \
    --cc=rjw@rjwysocki.net \
    --cc=sachin.kamat@linaro.org \
    --cc=tomasz.figa@gmail.com \
    --cc=yadi.brar01@gmail.com \
    --cc=yadi.brar@samsung.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).