linux-kernel - Re: [PATCH v3 1/2] dt-bindings: Add bindings for nvidia,tegra186-ccplex-cluster

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 13 Jun 2017 15:47:39 +0300
From:   Mikko Perttunen <cyndis@...si.fi>
To:     Thierry Reding <thierry.reding@...il.com>,
        Mikko Perttunen <mperttunen@...dia.com>
Cc:     jonathanh@...dia.com, robh+dt@...nel.org, mark.rutland@....com,
        devicetree@...r.kernel.org, linux-tegra@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: Add bindings for
 nvidia,tegra186-ccplex-cluster



On 13.06.2017 15:46, Mikko Perttunen wrote:
> On 13.06.2017 15:42, Thierry Reding wrote:
>> On Mon, Jun 12, 2017 at 01:23:04PM +0300, Mikko Perttunen wrote:
>>> The Tegra186 CCPLEX_CLUSTER area contains memory-mapped
>>> registers that initiate CPU frequency/voltage transitions.
>>>
>>> Signed-off-by: Mikko Perttunen <mperttunen@...dia.com>
>>> Acked-by: Rob Herring <robh@...nel.org>
>>> ---
>>>  .../arm/tegra/nvidia,tegra186-ccplex-cluster.txt     | 20
>>> ++++++++++++++++++++
>>>  1 file changed, 20 insertions(+)
>>>  create mode 100644
>>> Documentation/devicetree/bindings/arm/tegra/nvidia,tegra186-ccplex-cluster.txt
>>>
>>
>> The ARM SoC maintainers don't like to pick up device tree bindings, so
>> I'd prefer this to go through the cpufreq tree that also contains the
>> driver patches. Presumably this wasn't merged through that tree because
>> of the missing Acked-by by a device tree maintainer? Given that Rob's
>> acked it now, maybe you can resend this to Viresh, who I think had
>> picked up the driver?
>
> Sure, I'll do that.

> I guess the .dts change should then also go in that
> way?

Or I guess not, since you applied it :)

Cheers,
Mikko

>
> Mikko
>
>>
>> Thanks,
>> Thierry
>>