[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <67bdb642-292c-598a-496f-9d186c8a6705@arm.com>
Date: Tue, 6 Mar 2018 16:43:55 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Jeremy Linton <jeremy.linton@....com>
Cc: linux-acpi@...r.kernel.org, Sudeep Holla <sudeep.holla@....com>,
linux-arm-kernel@...ts.infradead.org, lorenzo.pieralisi@....com,
hanjun.guo@...aro.org, rjw@...ysocki.net, will.deacon@....com,
catalin.marinas@....com, gregkh@...uxfoundation.org,
mark.rutland@....com, linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org, wangxiongfeng2@...wei.com,
vkilari@...eaurora.org, ahs3@...hat.com, dietmar.eggemann@....com,
morten.rasmussen@....com, palmer@...ive.com, lenb@...nel.org,
john.garry@...wei.com, austinwc@...eaurora.org,
tnowicki@...iumnetworks.com
Subject: Re: [PATCH v7 02/13] drivers: base: cacheinfo: setup DT cache
properties early
On 28/02/18 22:06, Jeremy Linton wrote:
> The original intent in cacheinfo was that an architecture
> specific populate_cache_leaves() would probe the hardware
> and then cache_shared_cpu_map_setup() and
> cache_override_properties() would provide firmware help to
> extend/expand upon what was probed. Arm64 was really
> the only architecture that was working this way, and
> with the removal of most of the hardware probing logic it
> became clear that it was possible to simplify the logic a bit.
>
> This patch combines the walk of the DT nodes with the
> code updating the cache size/line_size and nr_sets.
> cache_override_properties() (which was DT specific) is
> then removed. The result is that cacheinfo.of_node is
> no longer used as a temporary place to hold DT references
> for future calls that update cache properties. That change
> helps to clarify its one remaining use (matching
> cacheinfo nodes that represent shared caches) which
> will be used by the ACPI/PPTT code in the following patches.
>
Reviewed-by: Sudeep Holla <sudeep.holla@....com>
--
Regards,
Sudeep
Powered by blists - more mailing lists