linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/1] ARM: imx: add gpu device
Date: Wed, 30 Mar 2011 11:12:10 +0200	[thread overview]
Message-ID: <20110330091210.GA19394@pengutronix.de> (raw)
In-Reply-To: <AANLkTimGUvNra0igyUGRJrzj5y3SwYFt4WEGKrLxd88-@mail.gmail.com>

Hello,

On Wed, Mar 30, 2011 at 05:03:45PM +0800, Eric Miao wrote:
> >> > @@ -203,6 +205,7 @@ static void __init mx35_3ds_init(void)
> >> > ? ? ? ? ? ? pr_warn("Init of the debugboard failed, all "
> >> > ? ? ? ? ? ? ? ? ? ? ? ? ? ? "devices on the debugboard are unusable.\n");
> >> > ? ? imx35_add_imx_i2c0(&mx35_3ds_i2c0_data);
> >> > + ? imx35_add_mxc_gpu(&z160_revision);
> >> Do you really need to pass this by pointer? Wouldn't
> >> imx35_add_mxc_gpu(0) be good enough?
> > It's because sometimes z160_revision has different values with different
> > TO versions and z160_revision will be dup as plat data.
Yeah, I got that. I just meant how imx_add_mxc_gpu works. Just let it
take a int (instead of an int *) and pass the address of the local
parameter to imx_add_platform_device_dmamask.
 
> This is where platform_device_id comes into play, at least by registering
> device with different names, e.g. 'imx35-gpu' or 'imx51-gpu', and the
> driver can handle.
> 
> Difference between steppings is a bit tricky though, I think a QUIRK_
> way, and pass combined QUIRK_* flags will be better in imx35_add_mxc_gpu()
> function itself.
... or that

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2011-03-30  9:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30  6:05 [PATCH v2 1/1] ARM: imx: add gpu device Richard Zhao
2011-03-30  7:16 ` Uwe Kleine-König
2011-03-30  8:16   ` Richard Zhao
2011-03-30  9:03     ` Eric Miao
2011-03-30  9:12       ` Uwe Kleine-König [this message]
2011-03-30  9:16         ` Wolfram Sang
2011-03-30  7:36 ` Sascha Hauer
2011-03-30  7:52   ` Arnaud Patard (Rtp)
2011-03-30  8:00     ` Richard Zhao
2011-03-30  8:05     ` Sascha Hauer
2011-03-30 22:23   ` Matt Sealey
2011-03-31  5:38     ` Richard Zhao
2011-04-01  0:29       ` Matt Sealey
2011-03-31  8:26     ` Sascha Hauer
2011-04-01  0:36       ` Matt Sealey
2011-04-01 13:30         ` Sascha Hauer
2011-03-31 10:00     ` Uwe Kleine-König

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=20110330091210.GA19394@pengutronix.de \
    --to=u.kleine-koenig@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).