From: Sascha Hauer <s.hauer@pengutronix.de>
To: Nicolin Chen <b42378@freescale.com>
Cc: timur@tabi.org, shawn.guo@linaro.org, broonie@kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
alsa-devel@alsa-project.org, rob.herring@calxeda.com,
mark.rutland@arm.com, swarren@wwwdotorg.org, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, b32955@freescale.com
Subject: Re: [PATCH 1/3] dma: imx-sdma: Add ssi dual fifo script support
Date: Tue, 29 Oct 2013 14:51:43 +0100 [thread overview]
Message-ID: <20131029135142.GT30088@pengutronix.de> (raw)
In-Reply-To: <9ed025d4e98f716ba80b27acaaa98f43ad3bd75a.1383047327.git.b42378@freescale.com>
On Tue, Oct 29, 2013 at 08:33:15PM +0800, Nicolin Chen wrote:
> There's a script for SSI missing in current sdma script list. Thus add it.
> This script would allow SSI use its dual fifo mode to transimit/receive
> data without occasional hardware underrun/overrun.
>
> This patch also fixed a counting error for total number of scripts.
Look at drivers/dma/imx-sdma.c:
> /**
> * struct sdma_firmware_header - Layout of the firmware image
> *
> * @magic "SDMA"
> * @version_major increased whenever layout of struct
> * sdma_script_start_addrs
> * changes.
Can you image why this firmware has a version field? Right, it's because
it encodes the layout of struct sdma_script_start_addrs.
As the comment clearly states you have to *increase this field* when you
add scripts.
Obviously you missed that, as the firmware on lkml posted recently
shows:
> 00000000: 414d4453 00000001 00000001 0000001c SDMA............
^^^^^^^^
Still '1'
> 00000010: 00000026 000000b4 0000067a 00000282 &.......z.......
> 00000020: ffffffff 00000000 ffffffff ffffffff ................
> 00000030: ffffffff ffffffff ffffffff ffffffff ................
> 00000040: ffffffff ffffffff 00001a6a ffffffff ........j.......
> 00000050: 000002eb 000018bb ffffffff 00000408 ................
> 00000060: ffffffff 000003c0 ffffffff ffffffff ................
> 00000070: ffffffff 000002ab ffffffff 0000037b ............{...
> 00000080: ffffffff ffffffff 0000044c 0000046e ........L...n...
> 00000090: ffffffff 00001800 ffffffff ffffffff ................
> 000000a0: 00000000 00001800 00001862 00001a16 ........b.......
^^^^^^^^^^^^^^^^^
new script addresses introduced
> -#define SDMA_SCRIPT_ADDRS_ARRAY_SIZE_V1 34
> +#define SDMA_SCRIPT_ADDRS_ARRAY_SIZE_V1 37
And no, this is not a bug. It's your firmware header that is buggy.
What you need is:
#define SDMA_SCRIPT_ADDRS_ARRAY_SIZE_V2 37
You (you as a company, not you as a person) knew that it was me who
created this firmware format. So it was absolutely unnecessary to create
an incompatible firmware instead of dropping me a short note.
Please add a version check to the driver as necessary and provide a proper
firmware.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2013-10-29 13:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 12:33 [PATCH 0/3] Add dual-fifo mode support of i.MX ssi Nicolin Chen
2013-10-29 12:33 ` [PATCH 1/3] dma: imx-sdma: Add ssi dual fifo script support Nicolin Chen
2013-10-29 13:51 ` Sascha Hauer [this message]
2013-10-30 4:48 ` Nicolin Chen
2013-10-29 17:21 ` Kumar Gala
2013-10-29 12:33 ` [PATCH 2/3] ASoC: fsl_ssi: Add dual fifo mode support Nicolin Chen
2013-10-29 12:42 ` Timur Tabi
2013-10-29 12:53 ` Chen Guangyu-B42378
2013-10-29 13:00 ` Timur Tabi
2013-10-29 13:03 ` Chen Guangyu-B42378
[not found] ` <cover.1383047327.git.b42378-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2013-10-29 12:33 ` [PATCH 3/3] ARM: dts: imx: use dual-fifo sdma script for ssi Nicolin Chen
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=20131029135142.GT30088@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=alsa-devel@alsa-project.org \
--cc=b32955@freescale.com \
--cc=b42378@freescale.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=shawn.guo@linaro.org \
--cc=swarren@wwwdotorg.org \
--cc=timur@tabi.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).