From: Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>
To: Abhishek <huntbag@linux.vnet.ibm.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
stewart@linux.vnet.ibm.com, linux-pm@vger.kernel.org,
daniel.lezcano@linaro.org, rjw@rjwysocki.net,
linux-kernel@vger.kernel.org, paulus@samba.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] cpuidle/powernv : Add Description for cpuidle state
Date: Tue, 5 Jun 2018 14:38:27 +0530 [thread overview]
Message-ID: <20180605090827.u535p5du5em3kgil@aksadiga.ibm> (raw)
In-Reply-To: <17cd53ec-6bc1-5814-8824-3c6a4f0b90cd@linux.vnet.ibm.com>
On Tue, Jun 05, 2018 at 02:24:39PM +0530, Abhishek wrote:
>
>
> On 06/04/2018 05:15 PM, Akshay Adiga wrote:
> > On Mon, Jun 04, 2018 at 07:04:14PM +1000, Benjamin Herrenschmidt wrote:
> > > Is this a new property ? I'm not fan of adding yet another of those
> > > silly arrays.
> > >
> > > I would say this is the right time now to switch over to a node per
> > > state instead, as we discussed with Vaidy.
>
> It is not a new property. Name was being used for description as description
> was not present in device tree. A skiboot patch adding description to device
> tree have been posted. This patch reads those description instead of copying
> name itself into description. And we fall back to reading name into
> description to not break the comaptibility with older firmware.
>From a cpuidle point of view this is a exisiting property, but for
powernv there was no device-tree property describing this.
Abhishek has added the following skiboot patch for adding description
for each idle state in device-tree .
https://patchwork.ozlabs.org/patch/924879/
I agree this can go into new device tree format which each idle state
as a node. Probably i will roll this patch into mine in the next
version.
>
> Thanks
> Abhishek
>
> > I posted the node based device tree here :
> > skiboot patch : https://patchwork.ozlabs.org/patch/923120/
> > kernel patch : https://lkml.org/lkml/2018/5/30/1146
> >
> > Do you have any inputs for this design ?
> >
> > > Additionally, while doing that, we can provide the versioning mechanism
> > > I proposed so we can deal with state specific issues and erratas.
> > >
> > > Cheers,
> > > Ben.
> > >
>
prev parent reply other threads:[~2018-06-05 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 8:17 [PATCH v2] cpuidle/powernv : Add Description for cpuidle state Abhishek Goel
2018-06-04 9:04 ` Benjamin Herrenschmidt
2018-06-04 11:45 ` Akshay Adiga
2018-06-05 8:54 ` Abhishek
2018-06-05 9:08 ` Akshay Adiga [this message]
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=20180605090827.u535p5du5em3kgil@aksadiga.ibm \
--to=akshay.adiga@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=daniel.lezcano@linaro.org \
--cc=huntbag@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=rjw@rjwysocki.net \
--cc=stewart@linux.vnet.ibm.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).