[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20150129121320.GI21293@sirena.org.uk>
Date: Thu, 29 Jan 2015 12:13:20 +0000
From: Mark Brown <broonie@...nel.org>
To: "BhuvanChandra.DV" <bhuvanchandra.dv@...adex.com>
Cc: "mark.rutland@....com" <mark.rutland@....com>,
"stefan@...er.ch" <stefan@...er.ch>,
"shawn.guo@...aro.org" <shawn.guo@...aro.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"pawel.moll@....com" <pawel.moll@....com>,
"ijc+devicetree@...lion.org.uk" <ijc+devicetree@...lion.org.uk>,
"galak@...eaurora.org" <galak@...eaurora.org>,
"linux@....linux.org.uk" <linux@....linux.org.uk>,
"B44548@...escale.com" <B44548@...escale.com>,
"Li.Xiubo@...escale.com" <Li.Xiubo@...escale.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>
Subject: Re: [PATCH 7/7] spi: spi-fsl-dspi: Add support for TCFQ transfer mode
On Thu, Jan 29, 2015 at 11:58:25AM +0000, BhuvanChandra.DV wrote:
> As far as i understood the major difference between the two modes are when
> the interrupt to trigger, as EOQ mode will trigger the interrupt at end of
> queue and TCF will trigger the interrupt at every frame transfer. Probably
> mode selection shouldn't be a device tree property, but i don't see any
> automatic way to choose between the modes.
> Maybe a config would be more appropriate?
Or if there's either no particular reason to choose one over the other
or one is always better then just pick one in the driver and don't worry
about implementing both.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists