From: Viresh Kumar <viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-F5mvAk5X5gdBDgjK7y7TUQ@public.gmane.org,
rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org,
linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ajitpal.singh-qxv4g6HH51o@public.gmane.org
Subject: Re: [PATCH 7/8] cpufreq: st: Provide runtime initialised driver for ST's platforms
Date: Tue, 23 Jun 2015 13:33:09 +0530 [thread overview]
Message-ID: <20150623080309.GI16776@linux> (raw)
In-Reply-To: <20150623071647.GD3245@x1>
On 23-06-15, 08:16, Lee Jones wrote:
> Thanks for your timely review Viresh.
Your welcome Lee :)
> On Tue, 23 Jun 2015, Viresh Kumar wrote:
> > On 22-06-15, 16:43, Lee Jones wrote:
> > > +config ARM_ST_CPUFREQ
> > > + bool "ST CPUFreq support"
> >
> > Isn't using ST just too generic? There are multiple SoCs ST has been
> > involved with, I have worked on a completely different series.
> > Probably a more relative string is required here, like stih407 ?
>
> This is ST's only CPUFreq implementation and is pretty board
> agnostic. This particular driver only currently supports the STiH407
> family, but internally it supports some others too. I'll have a chat
> and see if we can make it more specific somehow.
So, SPEAr is also from ST. And it already have a driver for itself.
> > > + if (!ddata->dvfs_tab_count) {
> > > + dev_err(&pdev->dev, "No suitable AVS table found\n");
> >
> > Why is this an error? I thought in this case you will go ahead with
> > the normal OPP-table.
>
> I've written it so it's an error within this function, as it makes the
> function fail, but is downgraded by the caller to a warning and
> gracefully bypassed to still allow frequency scaling.
Not that, I was asking about the print. I thought we will still try to
find OPP from the CPU node and a warning or a error might not be the
right choice. You can surely add a debug print. Currently you are
doing a dev_err() here, followed by a dev_warn() I think..
> > So you have added new OPPs here, but cpufreq-dt will try to add old
> > OPPs. You must be getting lots of warnings ?
>
> Yes, we recieve the 'duplicate OPPs detected' warning, but there is
> nothing we can do about that.
:)
OPP-v2 will get that solved too..
> > > + if (ddata->substrate < 0)
> > > + goto set_default;
> >
> > Maybe:
> >
> > if (ddata->substrate >= 0)
> > return;
>
> 0 is a valid substrate value.
I had >= in the comparison. Wasn't that right?
And I was just suggesting that a single return can be used instead of
if (xyz)
goto set_default;
return;
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/8] cpufreq: st: Provide runtime initialised driver for ST's platforms
Date: Tue, 23 Jun 2015 13:33:09 +0530 [thread overview]
Message-ID: <20150623080309.GI16776@linux> (raw)
In-Reply-To: <20150623071647.GD3245@x1>
On 23-06-15, 08:16, Lee Jones wrote:
> Thanks for your timely review Viresh.
Your welcome Lee :)
> On Tue, 23 Jun 2015, Viresh Kumar wrote:
> > On 22-06-15, 16:43, Lee Jones wrote:
> > > +config ARM_ST_CPUFREQ
> > > + bool "ST CPUFreq support"
> >
> > Isn't using ST just too generic? There are multiple SoCs ST has been
> > involved with, I have worked on a completely different series.
> > Probably a more relative string is required here, like stih407 ?
>
> This is ST's only CPUFreq implementation and is pretty board
> agnostic. This particular driver only currently supports the STiH407
> family, but internally it supports some others too. I'll have a chat
> and see if we can make it more specific somehow.
So, SPEAr is also from ST. And it already have a driver for itself.
> > > + if (!ddata->dvfs_tab_count) {
> > > + dev_err(&pdev->dev, "No suitable AVS table found\n");
> >
> > Why is this an error? I thought in this case you will go ahead with
> > the normal OPP-table.
>
> I've written it so it's an error within this function, as it makes the
> function fail, but is downgraded by the caller to a warning and
> gracefully bypassed to still allow frequency scaling.
Not that, I was asking about the print. I thought we will still try to
find OPP from the CPU node and a warning or a error might not be the
right choice. You can surely add a debug print. Currently you are
doing a dev_err() here, followed by a dev_warn() I think..
> > So you have added new OPPs here, but cpufreq-dt will try to add old
> > OPPs. You must be getting lots of warnings ?
>
> Yes, we recieve the 'duplicate OPPs detected' warning, but there is
> nothing we can do about that.
:)
OPP-v2 will get that solved too..
> > > + if (ddata->substrate < 0)
> > > + goto set_default;
> >
> > Maybe:
> >
> > if (ddata->substrate >= 0)
> > return;
>
> 0 is a valid substrate value.
I had >= in the comparison. Wasn't that right?
And I was just suggesting that a single return can be used instead of
if (xyz)
goto set_default;
return;
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@stlinux.com,
rjw@rjwysocki.net, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, ajitpal.singh@st.com
Subject: Re: [PATCH 7/8] cpufreq: st: Provide runtime initialised driver for ST's platforms
Date: Tue, 23 Jun 2015 13:33:09 +0530 [thread overview]
Message-ID: <20150623080309.GI16776@linux> (raw)
In-Reply-To: <20150623071647.GD3245@x1>
On 23-06-15, 08:16, Lee Jones wrote:
> Thanks for your timely review Viresh.
Your welcome Lee :)
> On Tue, 23 Jun 2015, Viresh Kumar wrote:
> > On 22-06-15, 16:43, Lee Jones wrote:
> > > +config ARM_ST_CPUFREQ
> > > + bool "ST CPUFreq support"
> >
> > Isn't using ST just too generic? There are multiple SoCs ST has been
> > involved with, I have worked on a completely different series.
> > Probably a more relative string is required here, like stih407 ?
>
> This is ST's only CPUFreq implementation and is pretty board
> agnostic. This particular driver only currently supports the STiH407
> family, but internally it supports some others too. I'll have a chat
> and see if we can make it more specific somehow.
So, SPEAr is also from ST. And it already have a driver for itself.
> > > + if (!ddata->dvfs_tab_count) {
> > > + dev_err(&pdev->dev, "No suitable AVS table found\n");
> >
> > Why is this an error? I thought in this case you will go ahead with
> > the normal OPP-table.
>
> I've written it so it's an error within this function, as it makes the
> function fail, but is downgraded by the caller to a warning and
> gracefully bypassed to still allow frequency scaling.
Not that, I was asking about the print. I thought we will still try to
find OPP from the CPU node and a warning or a error might not be the
right choice. You can surely add a debug print. Currently you are
doing a dev_err() here, followed by a dev_warn() I think..
> > So you have added new OPPs here, but cpufreq-dt will try to add old
> > OPPs. You must be getting lots of warnings ?
>
> Yes, we recieve the 'duplicate OPPs detected' warning, but there is
> nothing we can do about that.
:)
OPP-v2 will get that solved too..
> > > + if (ddata->substrate < 0)
> > > + goto set_default;
> >
> > Maybe:
> >
> > if (ddata->substrate >= 0)
> > return;
>
> 0 is a valid substrate value.
I had >= in the comparison. Wasn't that right?
And I was just suggesting that a single return can be used instead of
if (xyz)
goto set_default;
return;
--
viresh
next prev parent reply other threads:[~2015-06-23 8:03 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 15:43 [PATCH 0/8] cpufreq: Introduce support for ST's cpufreq functionality Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-22 15:43 ` [PATCH 1/8] ARM: STi: STiH407: Provide generic (safe) DVFS configuration Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-22 15:43 ` [PATCH 2/8] ARM: STi: STiH407: Provide CPU with clocking information Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-22 15:43 ` [PATCH 4/8] ARM: STi: STiH407: Provide a node for CPUFreq Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-22 15:43 ` Lee Jones
[not found] ` <1434987837-24212-5-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-06-23 2:16 ` Viresh Kumar
2015-06-23 2:16 ` Viresh Kumar
2015-06-23 2:16 ` Viresh Kumar
2015-06-23 7:10 ` Lee Jones
2015-06-23 7:10 ` Lee Jones
2015-06-23 7:10 ` Lee Jones
2015-06-23 7:57 ` Viresh Kumar
2015-06-23 7:57 ` Viresh Kumar
[not found] ` <1434987837-24212-1-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-06-22 15:43 ` [PATCH 3/8] ARM: STi: STiH407: Link CPU with its voltage supply Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-22 15:43 ` [PATCH 5/8] ARM: STi: STiH407: Move PWM nodes STiH407 => STiH407-family Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-23 2:17 ` Viresh Kumar
2015-06-23 2:17 ` Viresh Kumar
2015-06-23 2:17 ` Viresh Kumar
2015-06-23 7:08 ` Lee Jones
2015-06-23 7:08 ` Lee Jones
2015-06-23 7:08 ` Lee Jones
2015-06-23 7:55 ` Viresh Kumar
2015-06-23 7:55 ` Viresh Kumar
2015-06-22 15:43 ` [PATCH 6/8] ARM: multi_v7_defconfig: Enable support for PWM Regulators Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-22 15:43 ` [PATCH 7/8] cpufreq: st: Provide runtime initialised driver for ST's platforms Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-23 2:50 ` Viresh Kumar
2015-06-23 2:50 ` Viresh Kumar
2015-06-23 2:50 ` Viresh Kumar
2015-06-23 7:16 ` Lee Jones
2015-06-23 7:16 ` Lee Jones
2015-06-23 7:16 ` Lee Jones
2015-06-23 7:31 ` [STLinux Kernel] " Maxime Coquelin
2015-06-23 7:31 ` Maxime Coquelin
2015-06-23 7:31 ` Maxime Coquelin
2015-06-23 8:03 ` Viresh Kumar [this message]
2015-06-23 8:03 ` Viresh Kumar
2015-06-23 8:03 ` Viresh Kumar
2015-06-23 8:27 ` Lee Jones
2015-06-23 8:27 ` Lee Jones
2015-06-23 8:30 ` Viresh Kumar
2015-06-23 8:30 ` Viresh Kumar
2015-06-23 9:00 ` Lee Jones
2015-06-23 9:00 ` Lee Jones
2015-06-23 8:00 ` Paul Bolle
2015-06-23 8:00 ` Paul Bolle
[not found] ` <1435046411.4528.6.camel-IWqWACnzNjzz+pZb47iToQ@public.gmane.org>
2015-06-23 8:28 ` Lee Jones
2015-06-23 8:28 ` Lee Jones
2015-06-23 8:28 ` Lee Jones
2015-06-23 20:03 ` Paul Bolle
2015-06-23 20:03 ` Paul Bolle
2015-06-24 7:33 ` Lee Jones
2015-06-24 7:33 ` Lee Jones
2015-06-22 15:43 ` [PATCH 8/8] dt: cpufreq: st: Provide bindings for ST's CPUFreq implementation Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-22 15:43 ` Lee Jones
2015-06-23 2:34 ` Viresh Kumar
2015-06-23 2:34 ` Viresh Kumar
2015-06-23 2:34 ` Viresh Kumar
2015-06-23 7:06 ` Lee Jones
2015-06-23 7:06 ` Lee Jones
2015-06-23 7:06 ` Lee Jones
2015-06-23 7:55 ` Viresh Kumar
2015-06-23 7:55 ` Viresh Kumar
2015-06-23 8:38 ` Lee Jones
2015-06-23 8:38 ` Lee Jones
2015-06-23 8:52 ` Javier Martinez Canillas
2015-06-23 8:52 ` Javier Martinez Canillas
2015-06-23 8:59 ` Lee Jones
2015-06-23 8:59 ` Lee Jones
2015-06-23 9:00 ` Viresh Kumar
2015-06-23 9:00 ` Viresh Kumar
2015-06-23 9:00 ` Viresh Kumar
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=20150623080309.GI16776@linux \
--to=viresh.kumar-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=ajitpal.singh-qxv4g6HH51o@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-F5mvAk5X5gdBDgjK7y7TUQ@public.gmane.org \
--cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.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: 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.