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  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 13 Feb 2019 12:16:35 +0000
From:   Mark Brown <broonie@...nel.org>
To:     masonccyang@...c.com.tw
Cc:     bbrezillon@...nel.org,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Simon Horman <horms@...ge.net.au>, juliensu@...c.com.tw,
        linux-kernel@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
        linux-spi@...r.kernel.org, Marek Vasut <marek.vasut@...il.com>,
        Sergei Shtylyov <sergei.shtylyov@...entembedded.com>,
        zhengxunli@...c.com.tw
Subject: Re: Applied "spi: Add Renesas R-Car Gen3 RPC-IF SPI controller
 driver" to the spi tree

On Wed, Feb 13, 2019 at 04:25:32PM +0800, masonccyang@...c.com.tw wrote:

> From current mainline branch, MFD seems support the device which is on 
> the same hardware bus(i.e, I2C, SPI, MMIO and SPMI)for multi-function 
> by Read/Write the common same registers.

That's most MFDs but there are some that do some level of enumeration
(even if it's just looking at the device ID that got registered) to
decide what subdevices get registered, that's what people are suggesting
here I think.

> I am checking and not sure if MMIO of MFD could support RPC-IF for 
> different hardware bus on SPI and CFI.
> I also doubt if this method is a correct solution for RPC-IF works
> either in SPI mode or CFI mode.

For MMIO devices MFD just passes through the parent resources.

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

Powered by blists - more mailing lists