From: <ilialin@codeaurora.org>
To: 'Sudeep Holla' <sudeep.holla@arm.com>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, vireshk@kernel.org, nm@ti.com,
sboyd@kernel.org, robh@kernel.org, mark.rutland@arm.com,
rjw@rjwysocki.net
Subject: RE: [PATCH v12 1/2] cpufreq: Add Kryo CPU scaling driver
Date: Thu, 24 May 2018 17:52:03 +0300 [thread overview]
Message-ID: <000901d3f36e$c9c995e0$5d5cc1a0$@codeaurora.org> (raw)
In-Reply-To: <15d6025c-1307-64e0-6715-34240fcaf8eb@arm.com>
OK, got you.
Is "operating-points-v2-kryo-cpu" good enough?
> -----Original Message-----
> From: Sudeep Holla <sudeep.holla@arm.com>
> Sent: Thursday, May 24, 2018 17:48
> To: ilialin@codeaurora.org
> Cc: Sudeep Holla <sudeep.holla@arm.com>; linux-pm@vger.kernel.org;
> devicetree@vger.kernel.org; linux-kernel@vger.kernel.org;
> vireshk@kernel.org; nm@ti.com; sboyd@kernel.org; robh@kernel.org;
> mark.rutland@arm.com; rjw@rjwysocki.net
> Subject: Re: [PATCH v12 1/2] cpufreq: Add Kryo CPU scaling driver
>
>
>
> On 24/05/18 15:10, ilialin@codeaurora.org wrote:
> > Thank you for the explanation. However, could you suggest, which
> > condition should I check then? Device tree?
> >
>
> Yes some compatible which is applicable for all the SoCs or platforms on
> which this driver can work ?
>
> --
> Regards,
> Sudeep
next prev parent reply other threads:[~2018-05-24 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 8:57 [PATCH v12 0/2] Kryo CPU scaling driver Ilia Lin
2018-05-24 8:57 ` [PATCH v12 1/2] cpufreq: Add " Ilia Lin
2018-05-24 12:51 ` Sudeep Holla
2018-05-24 13:03 ` ilialin
2018-05-24 14:01 ` Sudeep Holla
2018-05-24 14:10 ` ilialin
2018-05-24 14:47 ` Sudeep Holla
2018-05-24 14:52 ` ilialin [this message]
2018-05-24 15:02 ` Sudeep Holla
2018-05-24 8:57 ` [PATCH v12 2/2] dt-bindings: cpufreq: Document operating-points-v2-kryo-cpu Ilia Lin
2018-05-24 9:02 ` [PATCH v12 0/2] Kryo CPU scaling driver Viresh Kumar
2018-05-24 11:20 ` Amit Kucheria
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='000901d3f36e$c9c995e0$5d5cc1a0$@codeaurora.org' \
--to=ilialin@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=vireshk@kernel.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 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).