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: <20200826142312.GH4965@sirena.org.uk>
Date:   Wed, 26 Aug 2020 15:23:12 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Vladimir Oltean <olteanv@...il.com>
Cc:     Qiang Zhao <qiang.zhao@....com>,
        kuldip dwivedi <kuldip.dwivedi@...esoftware.com>,
        "linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Pankaj Bansal <pankaj.bansal@....com>,
        Varun Sethi <V.Sethi@....com>,
        Tanveer Alam <tanveer.alam@...esoftware.com>
Subject: Re: [PATCH] spi: spi-fsl-dspi: Add ACPI support

On Wed, Aug 26, 2020 at 02:47:58PM +0300, Vladimir Oltean wrote:

> - The compatible string plays an integral part in the functionality of
>   the spi-fsl-dspi driver. I want to see a solution for ACPI where the
>   driver knows on which SoC it's running on. Otherwise it doesn't know
>   what are the silicon parameters of the DSPI module (XSPI present or
>   not, DMA present or not, FIFO depth). I don't see that now. I just see
>   something hardcoded for:
>   { "NXP0005", .driver_data = (kernel_ulong_t)&devtype_data[LS2085A], }

Based on some other stuff I've seen with ACPI on NXP stuff it looks like
they're following the same scheme but only caring about that one SoC for
the time being.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ