All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Mason <slash.tmp@free.fr>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linaro-kernel@lists.linaro.org, k.kozlowski@samsung.com,
	kgene.kim@samsung.com, heiko@sntech.de, linux-pm@vger.kernel.org,
	mmcclint@codeaurora.org, xf@rock-chips.com,
	Rafael Wysocki <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, rob.herring@linaro.org,
	Sebastian Frias <sebastian_frias@sigmadesigns.com>
Subject: Re: [PATCH V1 Resend 2/3] cpufreq: dt: Add generic platform-device creation support
Date: Fri, 1 Apr 2016 18:22:14 +0530	[thread overview]
Message-ID: <20160401125214.GE2987@vireshk-i7> (raw)
In-Reply-To: <56FE69E0.1080800@free.fr>

On 01-04-16, 14:30, Mason wrote:
> Hmmm... I'm using the older operating-points prop in my platform's DT.
> Why can't we define a new property (e.g. "enable-generic-cpufreq")
> which registers the "cpufreq-dt" pseudo-device?

DT is all about expressing hardware in a file. The same bindings
should be usable across any operating system, not just Linux. And so
we shouldn't have any OS or software-implementation specific
properties here.

> And platforms that manually register "cpufreq-dt" would be
> automatically white-listed, even if they don't have the new
> property, to maintain backward-compat?

Its not about just making it work, otherwise we would have done it
long time back by creating a DT node for cpufreq-dt driver.

> > @Rob: Will that be acceptable to you? We are discussing (again) about how to
> > probe cpufreq-dt driver automatically for platforms :)
> > 
> > The cpus node doesn't have any 'compatible' property today, and I will be
> > required to add that in this case.
> 
> Why does it need a compatible prop?

That compatible property will describe how to parse/describe
operating-points for a CPU. Any driver, which has the ability to parse
those bindings can do things base on such a compatibility string.

I hope you got the idea.

-- 
viresh

  reply	other threads:[~2016-04-01 12:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29  6:39 [PATCH V2 0/3] cpufreq: dt: Create platform device from generic code Viresh Kumar
2016-03-29  6:39 ` [PATCH V1 Resend 1/3] cpufreq: dt: Include types.h from cpufreq-dt.h Viresh Kumar
2016-03-29  6:39 ` [PATCH V1 Resend 2/3] cpufreq: dt: Add generic platform-device creation support Viresh Kumar
2016-03-29 15:14   ` Arnd Bergmann
2016-03-29 16:36     ` Viresh Kumar
2016-03-29 19:45       ` Arnd Bergmann
2016-03-30  3:22         ` Viresh Kumar
2016-03-30  7:53           ` Arnd Bergmann
2016-04-01 10:23             ` Viresh Kumar
2016-04-01 12:30               ` Mason
2016-04-01 12:52                 ` Viresh Kumar [this message]
2016-04-01 14:15               ` Rob Herring
2016-04-07  8:30                 ` Viresh Kumar
2016-04-18 21:00                   ` Arnd Bergmann
2016-03-29 16:42     ` Viresh Kumar
2016-03-29 19:46       ` Arnd Bergmann
2016-03-29  6:39 ` [PATCH V2 3/3] cpufreq: exynos: Use generic platdev driver Viresh Kumar
2016-03-29  6:39   ` Viresh Kumar
2016-03-29 15:04   ` Arnd Bergmann
2016-03-29 15:04     ` Arnd Bergmann
2016-03-29 15:22     ` Viresh Kumar
2016-03-29 15:22       ` Viresh Kumar
2016-03-29 23:46       ` Krzysztof Kozlowski
2016-03-29 23:46         ` Krzysztof Kozlowski

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=20160401125214.GE2987@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=arnd@arndb.de \
    --cc=heiko@sntech.de \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mmcclint@codeaurora.org \
    --cc=rjw@rjwysocki.net \
    --cc=rob.herring@linaro.org \
    --cc=sebastian_frias@sigmadesigns.com \
    --cc=slash.tmp@free.fr \
    --cc=xf@rock-chips.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.