From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Kevin Hilman <khilman@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Stefan Kristiansson <stefank@nvidia.com>,
Mikko Perttunen <mperttunen@nvidia.com>,
linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/3] PM / Domains: Allow overriding the ->xlate() callback
Date: Wed, 15 Mar 2017 13:43:57 +0000 [thread overview]
Message-ID: <8e4623c4-fd51-eadc-661b-5d2a88f3a8ef@nvidia.com> (raw)
In-Reply-To: <20170315133652.GA29259@ulmo.ba.sec>
On 15/03/17 13:36, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Tue, Mar 14, 2017 at 08:34:01PM +0000, Jon Hunter wrote:
>>
>> On 14/03/17 19:15, Thierry Reding wrote:
>>> From: Thierry Reding <treding@nvidia.com>
>>>
>>> Allow generic power domain providers to override the ->xlate() callback
>>> in case the default genpd_xlate_onecell() translation callback is not
>>> good enough.
>>>
>>> One potential use-case for this is to allow generic power domains to be
>>> specified by an ID rather than an index.
>>
>> Are you sure this is necessary, because I recall that the genpd core
>> does allow for holes in the domain array (which is what we have). See
>> commit 609bed67bd8f ('PM / Domains: Allow holes in genpd_data.domains
>> array').
>
> I suppose we could use that, but it feels like the wrong solution to me.
> Why would we want to deal with holes in the array when we can simply do
> all the required work at probe time and add only the existing domains in
> any particular SoC.
>
> For example on Tegra186 we've got a maximum ID of 43, so we'd need to
> allocate 44 pointers, but we only use 17 of those IDs. People usually
> reply to that that newer SoCs come with enough memory to make this
> waste irrelevant. I don't buy that. Why should we waste memory if it
> can be easily avoided?
I was wondering how many holes we have. That seems a bit excessive and
so I would agree it is a waste.
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2017-03-15 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 19:15 [PATCH 0/3] soc/tegra: bpmp: Generic PM domains for Tegra186 Thierry Reding
[not found] ` <20170314191516.13083-1-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-14 19:15 ` [PATCH 1/3] PM / Domains: Allow overriding the ->xlate() callback Thierry Reding
2017-03-14 20:34 ` Jon Hunter
[not found] ` <20d4efbc-b3f1-4d64-0aae-ac51e171a09a-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-03-15 13:36 ` Thierry Reding
2017-03-15 13:43 ` Jon Hunter [this message]
2017-03-14 19:15 ` [PATCH 2/3] soc/tegra: bpmp: Update ABI header Thierry Reding
2017-03-14 19:15 ` [PATCH 3/3] soc/tegra: bpmp: Implement generic PM domains Thierry Reding
2017-03-14 20:46 ` Jon Hunter
[not found] ` <709fd66d-b8ca-5cb7-ba58-a64ee3363c96-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-03-15 13:45 ` Thierry Reding
[not found] ` <20170314191516.13083-4-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-15 10:49 ` Mikko Perttunen
2017-03-15 15:00 ` Thierry Reding
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=8e4623c4-fd51-eadc-661b-5d2a88f3a8ef@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=khilman@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=rjw@rjwysocki.net \
--cc=stefank@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=ulf.hansson@linaro.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).