linux-kernel - Re: [spi-devel-general] [Patch] Add spi full duplex mode transfer support

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>] [day] [month] [year] [list]

Message-Id: <200608300835.32535.david-b@pacbell.net>
Date:	Wed, 30 Aug 2006 08:35:31 -0700
From:	David Brownell <david-b@...bell.net>
To:	spi-devel-general@...ts.sourceforge.net
Cc:	"Manish Jaggi" <manish.jaggi@...il.com>,
	Luke Yang <luke.adi@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [spi-devel-general] [Patch] Add spi full duplex mode transfer support

On Wednesday 30 August 2006 3:37 am, Manish Jaggi wrote:
> 
> On the same lines can we have a member in spi_transfer structure
> like bUseDMA.

LinuxStronglyAvoidsMixedCaseSymbols, see Documentation/CodingStyle.


> In spi PIO mode for short writes of 2 to 8 words is better.
> And we use DMA for larger writes/reads
> 
> What do u think?

I think that such tradeoffs are best hidden from the upper layer
(protocol) drivers, since they're specific to the hardware and
to how the driver is implemented.  So the lower level (controller)
driver should make such tradeoffs.

It's also a change of $SUBJECT but that's a different issue.  :)

- Dave


-
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/