linux-kernel - Re: [RFC] spi: add spi multiplexing functions for dt

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: <20180124145430.GD9366@sirena.org.uk>
Date:   Wed, 24 Jan 2018 14:54:30 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Ben Whitten <ben.whitten@...il.com>
Cc:     linux-spi@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] spi: add spi multiplexing functions for dt

On Wed, Jan 24, 2018 at 02:01:55PM +0000, Ben Whitten wrote:
> On 23 January 2018 at 11:11, Mark Brown <broonie@...nel.org> wrote:

> > level.  Things that have their own transfer function would be better off
> > just being first order SPI controllers I think so that they get access
> > to everything the framework offers and can correctly advertise
> > capabilities and so on.

> This runs as a very simple fake SPI controller per bus that the mux is
> controlling. Having this custom transfer message allowed me to pop
> in the way my device exposes the downstream devices, through its
> regmap.

Which like I say is a problem - if your device (which just sounds like a
SPI controller) has different capabilities and constraints to the parent
then client drivers won't see that.

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