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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR04MB401588B866A00A4507CC8C5795A30@VI1PR04MB4015.eurprd04.prod.outlook.com>
Date:   Wed, 28 Aug 2019 06:20:33 +0000
From:   Ashish Kumar <ashish.kumar@....com>
To:     Mark Brown <broonie@...nel.org>
CC:     "shawnguo@...nel.org" <shawnguo@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "mark.rutland@....com" <mark.rutland@....com>,
        "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
        Kuldeep Singh <kuldeep.singh@....com>
Subject: RE: [EXT] Re: [Patch v4 1/3] dt-bindings: spi: spi-fsl-qspi: Add
 ls2080a compatibility string to bindings



> -----Original Message-----
> From: Mark Brown <broonie@...nel.org>
> Sent: Tuesday, August 27, 2019 11:33 PM
> To: Ashish Kumar <ashish.kumar@....com>
> Cc: shawnguo@...nel.org; linux-kernel@...r.kernel.org; linux-
> spi@...r.kernel.org; devicetree@...r.kernel.org; robh+dt@...nel.org;
> mark.rutland@....com; linux-next@...r.kernel.org; Kuldeep Singh
> <kuldeep.singh@....com>
> Subject: Re: [EXT] Re: [Patch v4 1/3] dt-bindings: spi: spi-fsl-qspi: Add ls2080a
> compatibility string to bindings
> 
> On Mon, Aug 26, 2019 at 06:19:53AM +0000, Ashish Kumar wrote:
> 
> > For Patch-2, I intended to use this in arm64/boot/dts/freescale/fsl-
> ls1088a.dtsi (please see below), since both ls1088 and ls2080 has same QSPI
> controller.
> > So I had introduced new compatible
> > +                "fsl,ls1012a-qspi" followed by "fsl,ls1021a-qspi"
> > +                "fsl,ls1088a-qspi" followed by "fsl,ls2080a-qspi"
> 
> Even if the compatible is supposed to be used in conjunction with other
> fallbacks it should still explicitly be there in case someone forgets or decides
> not to do that for some reason.
Thanks Mark, I will update the spi-fsl-qspi.c to include ls1088, ls1012 in driver data.

Regards
Ashish 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ