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] [day] [month] [year] [list]
Message-ID: <yw1x4me6onii.fsf@unicorn.mansr.com>
Date:	Thu, 21 Jan 2016 17:23:01 +0000
From:	Måns Rullgård <mans@...sr.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	linux-spi <linux-spi@...r.kernel.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [TROLL PATCH] spi: add option to create spidev nodes for unclaimed chip selects

Geert Uytterhoeven <geert@...ux-m68k.org> writes:

> On Thu, Jan 21, 2016 at 5:36 PM, Mans Rullgard <mans@...sr.com> wrote:
>> This adds an option to create spidev nodes for any chip selects not
>> bound to a driver via DT/ACPI.  It probably doesn't play nicely with
>> modules.
>
> And with pinmux, FWIW ;-)

In my particular case, I can put whatever pinmux I want in the DT and
bring out the SPI signals, but I simply don't know what device will be
connected.

-- 
Måns Rullgård

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ