From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] dma: imx-sdma: Add ROM script addresses to driver
Date: Mon, 19 Aug 2013 19:39:12 +0200 [thread overview]
Message-ID: <20130819173912.GF31036@pengutronix.de> (raw)
In-Reply-To: <20130819144136.GC28297@S2101-09.ap.freescale.net>
On Mon, Aug 19, 2013 at 10:41:38PM +0800, Shawn Guo wrote:
> Copy devicetree mailing list.
>
> > @@ -352,8 +521,15 @@ static struct platform_device_id sdma_devtypes[] = {
> > MODULE_DEVICE_TABLE(platform, sdma_devtypes);
> >
> > static const struct of_device_id sdma_dt_ids[] = {
> > - { .compatible = "fsl,imx31-sdma", .data = &sdma_imx31, },
> > + { .compatible = "fsl,imx6q-sdma", .data = &sdma_imx6q, },
> > + { .compatible = "fsl,imx53-sdma", .data = &sdma_imx53, },
> > + { .compatible = "fsl,imx51-sdma", .data = &sdma_imx51, },
> > + { .compatible = "fsl,imx35-to2-sdma", .data = &sdma_imx35_to2, },
> > + { .compatible = "fsl,imx35-to1-sdma", .data = &sdma_imx35_to1, },
> > { .compatible = "fsl,imx35-sdma", .data = &sdma_imx35, },
>
> Do we need to bind the compatible with sdma_imx35_to2 like below?
>
> { .compatible = "fsl,imx35-sdma", .data = &sdma_imx35_to2, },
If we do this we assume that every i.MX35 is TO2. TO1 revisions will
misbehave then. I intentionally didn't do this so that the current
binding continues to work as before without script addresses.
>
> Otherwise, we will need to patch sdma_imx35 with proper .script_addrs
> assignment?
>
> Also, I do not know how we will play these tapeout specific compatible
> in device tree. As you know, we currently do not have tapeout but only
> chip specific DTS, since we expect kernel will figure out the
> tapeout/revision and handle the differences accordingly.
In fact the kernel does figure out the tapeout version, but I don't have
access to it in the driver.
Currently we have a problem anyway. We have the firmware names in the
dts, but the firmware is tapeout specific for i.MX31/35.
So I think our options are:
- remove the tapeout specifics from the devicetrees, this would mean to
also remove the firmware names.
- keep the tapeout specifics in the devicetree, then we could even add
some more like I did ;)
I don't know what's the best way to proceed. For now I could remove the
tapeout specific bindings, this way we would get the ROM script
addresses at least for i.MX25/5/6.
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-08-19 17:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 12:16 [PATCH] dma: imx-sdma: Add ROM script addresses to driver Sascha Hauer
2013-08-19 12:16 ` [PATCH 1/3] dma: imx-sdma: Use struct for driver data Sascha Hauer
2013-08-19 12:16 ` [PATCH 2/3] dma: imx-sdma: Add ROM script addresses to driver Sascha Hauer
2013-08-19 14:41 ` Shawn Guo
2013-08-19 17:39 ` Sascha Hauer [this message]
2013-08-20 2:35 ` Shawn Guo
2013-08-20 6:42 ` Sascha Hauer
2013-08-19 12:16 ` [PATCH 3/3] ARM: i.MX: remove sdma script address arrays from platform data Sascha Hauer
2013-08-19 22:23 ` [PATCH] dma: imx-sdma: Add ROM script addresses to driver Matt Sealey
2013-08-20 7:00 ` Sascha Hauer
2013-08-20 13:53 ` Matt Sealey
2013-08-20 15:02 ` Sascha Hauer
2013-08-29 17:23 ` Matt Sealey
2013-08-31 8:56 ` Sascha Hauer
-- strict thread matches above, loose matches on Subject: below --
2013-08-20 8:04 [PATCH v2] " Sascha Hauer
2013-08-20 8:04 ` [PATCH 2/3] " Sascha Hauer
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=20130819173912.GF31036@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).