From: Nishanth Menon <nm@ti.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Pandita, Vikram" <vikram.pandita@ti.com>,
"Premi, Sanjeev" <premi@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] Runtime detection of Si features
Date: Thu, 13 Aug 2009 12:58:34 -0500 [thread overview]
Message-ID: <4A84544A.7030808@ti.com> (raw)
In-Reply-To: <4A84429D.4050600@ti.com>
Nishanth Menon had written, on 08/13/2009 11:43 AM, the following:
> Kevin Hilman had written, on 08/13/2009 11:40 AM, the following:
>> "Pandita, Vikram" <vikram.pandita@ti.com> writes:
>>
>>>> -----Original Message-----
>>>> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of
>>>> Sent: Thursday, August 13, 2009 11:31 AM
>>>>>> Since most of the code seemed repetitive, macros
>>>>>> have been used for readability.
>>>>>>
>>>>>> Signed-off-by: Sanjeev Premi <premi@ti.com>
>>>>> I like the feature-based approach.
>>>>>
>>>>> A couple questions though. Is there a bit/register that reports the
>>>>> collapsed powerdomains of the devices with modified PRCM?
>>>>>
>>>>> Also, how will other code query the features? You're currently
>>>>> exporting the omap_has_*() functions, but there are no prototypes.
>>>>>
>>>>> I think I'd rather see a static inline functions in <mach/cpu.h>
>>>>> for checking features. Comments to that end inlined below...
>>>> Wonder if we can setup some sort of infrastructure for:
>>>> a) features
>>>> b) erratas
>>>> linked to OMAP revs + even better w.r.t silicon module(SGX,I2c)
>>>> revisions since at times they are used across multiple OMAPs?
>>> We are hitting exactly this issue with I2C errata 1.153
>>> Instead of basing the errata check on cpu_is...(),
>>> its more appropriate to base it on IP revision of I2C.
>> Shouldn't the IP revision of I2C be avaialble in an I2C revision
>> register an be used in the driver instead of cpu_is*?
> what I was proposing is a much more generic infrastructure which i2c
> among other modules can use. Getting IP revision is already available in
> the specific IP modules REVISION registers - we might want to
> standardize how drivers handle revision based feature/errata set to
> ensure that they would have an optimal way to handle the same.. just my
> 2 cents..
>
Thinking of this a little more:
driver's smart handling aside, having a sysfs entry to dump the features
and erratas for each of the modules used is so much nice to have..
sigh.. just wondering if anyone has ideas how feasible this might be..
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2009-08-13 17:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 15:18 [PATCH] Runtime detection of Si features Sanjeev Premi
2009-08-13 16:13 ` Kevin Hilman
2009-08-13 16:31 ` Nishanth Menon
2009-08-13 16:37 ` Pandita, Vikram
2009-08-13 16:40 ` Kevin Hilman
2009-08-13 16:43 ` Nishanth Menon
2009-08-13 17:58 ` Nishanth Menon [this message]
2009-08-13 18:01 ` Kevin Hilman
2009-08-17 11:21 ` Premi, Sanjeev
2009-08-17 8:14 ` Premi, Sanjeev
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=4A84544A.7030808@ti.com \
--to=nm@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@ti.com \
--cc=vikram.pandita@ti.com \
/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