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: <01518a53-23d1-8c70-7327-69e8602bddb6@arm.com>
Date:   Thu, 28 Mar 2019 18:42:58 +0000
From:   Suzuki K Poulose <suzuki.poulose@....com>
To:     mathieu.poirier@...aro.org
Cc:     linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-acpi@...r.kernel.org, coresight@...ts.linaro.org,
        mike.leach@...aro.org, robert.walker@....com
Subject: Re: [PATCH 21/25] coresight: Use fwnode handle instead of device
 names

On 03/28/2019 05:42 PM, Mathieu Poirier wrote:
> On Wed, Mar 20, 2019 at 06:49:38PM +0000, Suzuki K Poulose wrote:
>> We rely on the device names to find a CoreSight device on the
>> coresight bus. The device name however is obtained from the platform,
>> which is bound to the real platform/amba device. As we are about
>> to use different naming scheme for the coresight devices, we can't
>> rely on the platform device name to find the corresponding
>> coresight device. Instead we use the platform agnostic
>> "fwnode handle" of the parent device to find the devices.
>> We also reuse the same fwnode as the parent for the Coresight
>> device we create.
>>
>> Cc: Mathieu Poirier <mathieu.poirier@...aro.org>
>> Signed-off-by: Suzuki K Poulose <suzuki.poulose@....com>

Agreed to all comments. Will address them in the next revision.

Cheers
Suzuki

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ