linux-kernel - Re: [PATCH V3 4/4] soc/tegra: pmc: Use the new reset APIs to manage reset controllers

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]

Message-ID: <e87a846b-4bbf-03cf-f3a6-99d5e468425c@nvidia.com>
Date:   Mon, 24 Apr 2017 13:45:20 +0100
From:   Jon Hunter <jonathanh@...dia.com>
To:     Vivek Gautam <vivek.gautam@...eaurora.org>,
        <p.zabel@...gutronix.de>, <swarren@...dotorg.org>,
        <balbi@...nel.org>
CC:     <linux-kernel@...r.kernel.org>, <linux-tegra@...r.kernel.org>,
        <linux-usb@...r.kernel.org>, <thierry.reding@...il.com>,
        <gregkh@...uxfoundation.org>, <linux-arm-msm@...r.kernel.org>,
        Thierry Reding <treding@...dia.com>
Subject: Re: [PATCH V3 4/4] soc/tegra: pmc: Use the new reset APIs to manage
 reset controllers

On 18/04/17 12:21, Vivek Gautam wrote:
> Make use of reset_control_array_*() set of APIs to manage
> an array of reset controllers available with the device.

Before we apply this patch, I need to check to see if the order of the
resets managed by the PMC driver matter. Today the order of the resets
is determined by the order they appear in the DT node and although the
new APIs work in the same way they do not guarantee this. So let me
check to see if we can any concerns about ordering here. Otherwise would
be nice to use these APIs.

Cheers
Jon

-- 
nvpublic