[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140628170709.GB23634@xo-6d-61-c0.localdomain>
Date: Sat, 28 Jun 2014 19:07:09 +0200
From: Pavel Machek <pavel@....cz>
To: Suman Anna <s-anna@...com>
Cc: Tony Lindgren <tony@...mide.com>,
Jassi Brar <jaswinder.singh@...aro.org>,
Dave Gerlach <d-gerlach@...com>, linux-kernel@...r.kernel.org,
linux-omap@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Jassi Brar <jassisinghbrar@...il.com>,
Rob Herring <robh+dt@...nel.org>
Subject: Re: [PATCH 2/6] mailbox/omap: add support for parsing dt devices
Hi!
> The non-DT support has to be maintained for now to not break
> OMAP3 legacy boot, and the legacy-style code will be cleaned
> up once OMAP3 is also converted to DT-boot only.
> @@ -587,24 +606,157 @@ static int omap_mbox_unregister(struct omap_mbox_device *mdev)
> return 0;
> }
>
> +static const struct omap_mbox_device_data omap2_data = {
> + .num_users = 4,
> + .num_fifos = 6,
> + .intr_type = MBOX_INTR_CFG_TYPE1,
> +};
> +
> +static const struct omap_mbox_device_data omap3_data = {
> + .num_users = 2,
> + .num_fifos = 2,
> + .intr_type = MBOX_INTR_CFG_TYPE1,
> +};
> +
> +static const struct omap_mbox_device_data am335x_data = {
> + .num_users = 4,
> + .num_fifos = 8,
> + .intr_type = MBOX_INTR_CFG_TYPE2,
> +};
So you use compatible strings to look up 3 integers. Would it be better to have
num_users/num_fifos/intr_type directly in the device tree? That should be cleaner
and more flexible...
If you do that, would it be possible to have share compatible string?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists