From: Tomasz Figa <tomasz.figa@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Yadwinder Singh Brar <yadi.brar01@gmail.com>,
Yadwinder Singh Brar <yadi.brar@samsung.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Tomasz Figa <t.figa@samsung.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Thomas Abraham <thomas.abraham@linaro.org>,
Kukjin Kim <kgene.kim@samsung.com>
Subject: Re: [RFC 0/4] Add basic support for ASV
Date: Thu, 14 Nov 2013 16:06:33 +0100 [thread overview]
Message-ID: <1906951.EFsdgbeaob@flatron> (raw)
In-Reply-To: <CAKew6eUK9ZtoVgVu_b13Bn20iMNWzHnWjSHMjxD1Y+zDtvoCWw@mail.gmail.com>
Hi Yadwinder,
On Monday 11 of November 2013 23:27:08 Yadwinder Singh Brar wrote:
> gentle ping for suggestions/reviews ..
Hmm, I must have somehow missed this series when you orignally sent it.
Can I ask you to resend it, as I don't have it in my e-mail client archive
any longer?
While at it, I would also ask you to add my private e-mail address
(this one) and linux-pm mailing list to Cc list.
Thanks in advance.
Best regards,
Tomasz
>
>
> On Wed, Sep 11, 2013 at 8:14 PM, Yadwinder Singh Brar
> <yadi.brar@samsung.com> wrote:
> > This series is to add basic common infrastructure for ASV.
> > Basically ASV is a technique used on samsung SoCs, which provides the
> > recommended supply voltage for dvfs of arm, mif etc. For a given operating
> > frequency, the voltage is recommended based on SoC's ASV group.
> > ASV group gets fussed on SoCs during process of mass production.
> >
> > This series includes:
> > - basic common infrastructue for ASV. It provides common APIs for user drivers
> > like cpufreq & devfreq and and an interface for SoC specific drivers to
> > register ASV members(instances)
> > - a common platform driver to register ASV members for exynos SoCs
> > - an example providing minimal support (only for ARM ASV) for exynos5250 chips
> >
> > Its just basic skelton which I wanted to get it reviewed or discussed in
> > early stage, before going ahead on further development based on it.
> > Presently example is based on static ASV table provided in SoC specific file,
> > which I expects to go into DT. But exactly how and where needs to be discussed,
> > may be in next revisions once we get through the basic skelton.
> > Also the location of driver in kernel may also seem odd to someone and
> > many more things :).
> >
> > Looking for your valuable reviews and suggestions.
> >
> > Thanks
> >
> > Yadwinder Singh Brar (4):
> > power: asv: Add common ASV support for samsung SoCs
> > power: asv: Add a common asv driver for exynos SoCs.
> > power: asv: Add support for exynos5250
> > arm: exynos5: Register static platform device for ASV.
> >
> > arch/arm/mach-exynos/mach-exynos5-dt.c | 3 +
> > drivers/power/Kconfig | 1 +
> > drivers/power/Makefile | 1 +
> > drivers/power/asv/Kconfig | 24 ++++
> > drivers/power/asv/Makefile | 2 +
> > drivers/power/asv/exynos-asv.c | 81 ++++++++++++++
> > drivers/power/asv/exynos-asv.h | 22 ++++
> > drivers/power/asv/exynos5250-asv.c | 141 ++++++++++++++++++++++++
> > drivers/power/asv/samsung-asv.c | 175 ++++++++++++++++++++++++++++++
> > include/linux/power/samsung-asv-driver.h | 61 +++++++++++
> > include/linux/power/samsung-asv.h | 37 +++++++
> > 11 files changed, 548 insertions(+), 0 deletions(-)
> > create mode 100644 drivers/power/asv/Kconfig
> > create mode 100644 drivers/power/asv/Makefile
> > create mode 100644 drivers/power/asv/exynos-asv.c
> > create mode 100644 drivers/power/asv/exynos-asv.h
> > create mode 100644 drivers/power/asv/exynos5250-asv.c
> > create mode 100644 drivers/power/asv/samsung-asv.c
> > create mode 100644 include/linux/power/samsung-asv-driver.h
> > create mode 100644 include/linux/power/samsung-asv.h
> >
> >
> > _______________________________________________
> > linux-arm-kernel mailing list
> > linux-arm-kernel@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 0/4] Add basic support for ASV
Date: Thu, 14 Nov 2013 16:06:33 +0100 [thread overview]
Message-ID: <1906951.EFsdgbeaob@flatron> (raw)
In-Reply-To: <CAKew6eUK9ZtoVgVu_b13Bn20iMNWzHnWjSHMjxD1Y+zDtvoCWw@mail.gmail.com>
Hi Yadwinder,
On Monday 11 of November 2013 23:27:08 Yadwinder Singh Brar wrote:
> gentle ping for suggestions/reviews ..
Hmm, I must have somehow missed this series when you orignally sent it.
Can I ask you to resend it, as I don't have it in my e-mail client archive
any longer?
While at it, I would also ask you to add my private e-mail address
(this one) and linux-pm mailing list to Cc list.
Thanks in advance.
Best regards,
Tomasz
>
>
> On Wed, Sep 11, 2013 at 8:14 PM, Yadwinder Singh Brar
> <yadi.brar@samsung.com> wrote:
> > This series is to add basic common infrastructure for ASV.
> > Basically ASV is a technique used on samsung SoCs, which provides the
> > recommended supply voltage for dvfs of arm, mif etc. For a given operating
> > frequency, the voltage is recommended based on SoC's ASV group.
> > ASV group gets fussed on SoCs during process of mass production.
> >
> > This series includes:
> > - basic common infrastructue for ASV. It provides common APIs for user drivers
> > like cpufreq & devfreq and and an interface for SoC specific drivers to
> > register ASV members(instances)
> > - a common platform driver to register ASV members for exynos SoCs
> > - an example providing minimal support (only for ARM ASV) for exynos5250 chips
> >
> > Its just basic skelton which I wanted to get it reviewed or discussed in
> > early stage, before going ahead on further development based on it.
> > Presently example is based on static ASV table provided in SoC specific file,
> > which I expects to go into DT. But exactly how and where needs to be discussed,
> > may be in next revisions once we get through the basic skelton.
> > Also the location of driver in kernel may also seem odd to someone and
> > many more things :).
> >
> > Looking for your valuable reviews and suggestions.
> >
> > Thanks
> >
> > Yadwinder Singh Brar (4):
> > power: asv: Add common ASV support for samsung SoCs
> > power: asv: Add a common asv driver for exynos SoCs.
> > power: asv: Add support for exynos5250
> > arm: exynos5: Register static platform device for ASV.
> >
> > arch/arm/mach-exynos/mach-exynos5-dt.c | 3 +
> > drivers/power/Kconfig | 1 +
> > drivers/power/Makefile | 1 +
> > drivers/power/asv/Kconfig | 24 ++++
> > drivers/power/asv/Makefile | 2 +
> > drivers/power/asv/exynos-asv.c | 81 ++++++++++++++
> > drivers/power/asv/exynos-asv.h | 22 ++++
> > drivers/power/asv/exynos5250-asv.c | 141 ++++++++++++++++++++++++
> > drivers/power/asv/samsung-asv.c | 175 ++++++++++++++++++++++++++++++
> > include/linux/power/samsung-asv-driver.h | 61 +++++++++++
> > include/linux/power/samsung-asv.h | 37 +++++++
> > 11 files changed, 548 insertions(+), 0 deletions(-)
> > create mode 100644 drivers/power/asv/Kconfig
> > create mode 100644 drivers/power/asv/Makefile
> > create mode 100644 drivers/power/asv/exynos-asv.c
> > create mode 100644 drivers/power/asv/exynos-asv.h
> > create mode 100644 drivers/power/asv/exynos5250-asv.c
> > create mode 100644 drivers/power/asv/samsung-asv.c
> > create mode 100644 include/linux/power/samsung-asv-driver.h
> > create mode 100644 include/linux/power/samsung-asv.h
> >
> >
> > _______________________________________________
> > linux-arm-kernel mailing list
> > linux-arm-kernel at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2013-11-14 15:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 11:14 [RFC 0/4] Add basic support for ASV Yadwinder Singh Brar
2013-09-11 11:14 ` Yadwinder Singh Brar
2013-09-11 11:14 ` [RFC 1/4] power: asv: Add common ASV support for samsung SoCs Yadwinder Singh Brar
2013-09-11 11:14 ` [RFC 2/4] power: asv: Add a common asv driver for exynos SoCs Yadwinder Singh Brar
2013-09-11 11:14 ` [RFC 3/4] power: asv: Add support for exynos5250 Yadwinder Singh Brar
2013-09-11 11:14 ` [RFC 4/4] arm: exynos5: Register static platform device for ASV Yadwinder Singh Brar
2013-11-11 14:27 ` [RFC 0/4] Add basic support " Yadwinder Singh Brar
2013-11-11 14:27 ` Yadwinder Singh Brar
2013-11-13 2:33 ` MyungJoo Ham
2013-11-13 2:33 ` MyungJoo Ham
2013-11-14 14:06 ` Yadwinder Singh Brar
2013-11-14 14:06 ` Yadwinder Singh Brar
2013-11-14 15:06 ` Tomasz Figa [this message]
2013-11-14 15:06 ` Tomasz Figa
2013-11-14 23:15 ` Yadwinder Singh Brar
2013-11-14 23:15 ` Yadwinder Singh Brar
2013-11-15 0:03 ` Tomasz Figa
2013-11-15 0:03 ` Tomasz Figa
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=1906951.EFsdgbeaob@flatron \
--to=tomasz.figa@gmail.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rjw@sisk.pl \
--cc=t.figa@samsung.com \
--cc=thomas.abraham@linaro.org \
--cc=viresh.kumar@linaro.org \
--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 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.