[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <508E3857.6080109@ti.com>
Date: Mon, 29 Oct 2012 13:33:35 +0530
From: Afzal Mohammed <x0148406@...com>
To: Daniel Mack <zonque@...il.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Grant Likely <grant.likely@...retlab.ca>,
Rob Herring <rob.herring@...xeda.com>,
Rob Landley <rob@...dley.net>, Sekhar Nori <nsekhar@...com>,
Kevin Hilman <khilman@...com>,
Russell King <linux@....linux.org.uk>,
Alessandro Zummo <a.zummo@...ertech.it>,
<devicetree-discuss@...ts.ozlabs.org>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
<davinci-linux-open-source@...ux.davincidsp.com>,
<linux-arm-kernel@...ts.infradead.org>,
<rtc-linux@...glegroups.com>
Subject: Re: [PATCH v4 3/5] rtc: omap: dt support
Hi Daniel,
On Monday 22 October 2012 01:21 AM, Daniel Mack wrote:
> On 19.10.2012 11:59, Afzal Mohammed wrote:
>> +static const struct of_device_id omap_rtc_of_match[] = {
>> + { .compatible = "ti,da830-rtc",
>> + .data =&omap_rtc_devtype[OMAP_RTC_DATA_DA830_IDX],
> Wouldn't it make sense to list all the compatible models here? The
> advantage of a compatible list is that we can name the models
> explicitly, or maybe at least "davinci-rtc". Is there any reason for
> this particular name?
Exact name followed by compatible models needs to be
specified in DT node only, right ? (when driver for the
first variant can handle it)
And when additional features of newer IP's has to be
leveraged, new entries can be added in the driver
match table.
First known variant of SoC for DT is da830 (exact name),
hence it was used.
Regards
Afzal
--
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