From: BhuvanChandra.DV <bhuvanchandra.dv@toradex.com>
To: Mark Brown <broonie@kernel.org>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"B44548@freescale.com" <B44548@freescale.com>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"Li.Xiubo@freescale.com" <Li.Xiubo@freescale.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stefan@agner.ch" <stefan@agner.ch>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"galak@codeaurora.org" <galak@codeaurora.org>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 7/7] spi: spi-fsl-dspi: Add support for TCFQ transfer mode
Date: Thu, 29 Jan 2015 11:58:25 +0000 [thread overview]
Message-ID: <1422533049999.91114@toradex.com> (raw)
In-Reply-To: <20150128190342.GE21293@sirena.org.uk>
On 01/29/2015 12:33 AM, Mark Brown wrote:
> On Tue, Jan 27, 2015 at 04:33:28PM +0530, Bhuvanchandra DV wrote:
>
>> TCFQ is interrupt of Transfer Complete Flag in DSPI module.
>> EOQ is interrupt of End of Queue Flag in DSPI module.
>> For adopting of different platform, either of them is a way of DSPI
>> transfer data. This patch add TCF support for DSPI module in other platform.
> I can't really understand what the purpose of this is, sorry. What are
> these modes and why would one choose one over the other? Your changelog
> suggests this is being done per board which implies that it's tuning for
> performance but that's usually something that should be done in device
> drivers, not the device tree - perhaps the tuning will change over time
> as the driver is optimized or perhaps it varies depending on the
> transfer.
>
> The code mentions a DMA option as well, generally where it's available
> DMA is something that's chosen at runtime based on the length of the
> transfer.
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?
@Chao, is there any specific reason to implement this mode?
WARNING: multiple messages have this Message-ID (diff)
From: bhuvanchandra.dv@toradex.com (BhuvanChandra.DV)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/7] spi: spi-fsl-dspi: Add support for TCFQ transfer mode
Date: Thu, 29 Jan 2015 11:58:25 +0000 [thread overview]
Message-ID: <1422533049999.91114@toradex.com> (raw)
In-Reply-To: <20150128190342.GE21293@sirena.org.uk>
On 01/29/2015 12:33 AM, Mark Brown wrote:
> On Tue, Jan 27, 2015 at 04:33:28PM +0530, Bhuvanchandra DV wrote:
>
>> TCFQ is interrupt of Transfer Complete Flag in DSPI module.
>> EOQ is interrupt of End of Queue Flag in DSPI module.
>> For adopting of different platform, either of them is a way of DSPI
>> transfer data. This patch add TCF support for DSPI module in other platform.
> I can't really understand what the purpose of this is, sorry. What are
> these modes and why would one choose one over the other? Your changelog
> suggests this is being done per board which implies that it's tuning for
> performance but that's usually something that should be done in device
> drivers, not the device tree - perhaps the tuning will change over time
> as the driver is optimized or perhaps it varies depending on the
> transfer.
>
> The code mentions a DMA option as well, generally where it's available
> DMA is something that's chosen at runtime based on the length of the
> transfer.
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?
@Chao, is there any specific reason to implement this mode?
next prev parent reply other threads:[~2015-01-29 11:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 11:03 [PATCH 6/7] spi: spi-fsl-dspi: split the resuable code Bhuvanchandra DV
2015-01-27 11:03 ` Bhuvanchandra DV
2015-01-27 11:03 ` Bhuvanchandra DV
2015-01-27 11:03 ` Bhuvanchandra DV
[not found] ` <1422356608-15961-1-git-send-email-bhuvanchandra.dv-2KBjVHiyJgBBDgjK7y7TUQ@public.gmane.org>
2015-01-27 11:03 ` [PATCH 7/7] spi: spi-fsl-dspi: Add support for TCFQ transfer mode Bhuvanchandra DV
2015-01-27 11:03 ` Bhuvanchandra DV
2015-01-27 11:03 ` Bhuvanchandra DV
2015-01-27 11:03 ` Bhuvanchandra DV
2015-01-28 19:03 ` Mark Brown
2015-01-28 19:03 ` Mark Brown
2015-01-28 19:03 ` Mark Brown
2015-01-29 11:58 ` BhuvanChandra.DV [this message]
2015-01-29 11:58 ` BhuvanChandra.DV
2015-01-29 12:13 ` Mark Brown
2015-01-29 12:13 ` Mark Brown
2015-01-29 12:53 ` BhuvanChandra.DV
2015-01-29 12:53 ` BhuvanChandra.DV
[not found] ` <1422536382672.21760-2KBjVHiyJgBBDgjK7y7TUQ@public.gmane.org>
2015-01-29 18:10 ` Stefan Agner
2015-01-29 18:10 ` Stefan Agner
2015-01-29 18:10 ` Stefan Agner
2015-01-29 18:10 ` Stefan Agner
2015-01-30 12:30 ` Mark Brown
2015-01-30 12:30 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1422533049999.91114@toradex.com \
--to=bhuvanchandra.dv@toradex.com \
--cc=B44548@freescale.com \
--cc=Li.Xiubo@freescale.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=stefan@agner.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.