linux-kernel - Re: [RFC][PATCH v2 2/3] spi_bitbang : get nsecs delay from cs during transfer

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: <AANLkTi=Fi+TaV=FJfz07kGBLnKMDoh5ph2vnLA9xLNVK@mail.gmail.com>
Date:	Tue, 14 Dec 2010 13:17:22 -0500
From:	Ben Gardiner <bengardiner@...ometrics.ca>
To:	Wolfram Sang <w.sang@...gutronix.de>
Cc:	spi-devel-general@...ts.sourceforge.net,
	Grant Likely <grant.likely@...retlab.ca>,
	David Brownell <dbrownell@...rs.sourceforge.net>,
	linux-kernel@...r.kernel.org, Michael Buesch <mb@...sch.de>
Subject: Re: [RFC][PATCH v2 2/3] spi_bitbang : get nsecs delay from cs during transfer

On Tue, Dec 14, 2010 at 1:08 PM, Wolfram Sang <w.sang@...gutronix.de> wrote:
> Hi Ben,
>
>> I think it is starting to sink-in that a 'slower' spi gpio _driver_ is
>> needed. I can think of a couple different ways to make the CS-to-data
>> delay assigned to 'nsecs' a per-device feature:
>> 1) a flag or 2) a function pointer in struct spi_bitbang. Were you
>> thinking of something else entirely?
>
> Nope, just saw (very high-level) that it should be per-device as it
> might be feasible to have a fast and a slow bus at the same time. My
> advice would be to start coding your favourite solution and check if it
> feels right :)

:) Sounds like good advice.

Thanks again, Wolfram.

Best Regards,
Ben Gardiner

---
Nanometrics Inc.
http://www.nanometrics.ca
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/