From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@ti.com>
Cc: Ilya Yanok <yanok@emcraft.com>,
linux-omap@vger.kernel.org, wd@denx.de, dzu@denx.de,
sasha_d@emcraft.com, hvaibhav@ti.com
Subject: Re: [PATCH] AM35xx: disable checking for reserved feature bits
Date: Wed, 7 Dec 2011 15:58:25 -0800 [thread overview]
Message-ID: <20111207235825.GS31337@atomide.com> (raw)
In-Reply-To: <87d3d2kt83.fsf@ti.com>
Hi,
* Kevin Hilman <khilman@ti.com> [111108 16:23]:
> Ilya Yanok <yanok@emcraft.com> writes:
>
> > Bits corresponding to the IVA and ISP features in OMAP_STATUS register
> > are reserved on AM35xx and checking for them results in wrong results.
>
> Ouch.
>
> > So we don't want to check for this features on AM35xx.
> >
> > Signed-off-by: Ilya Yanok <yanok@emcraft.com>
>
> This "feature" selection mechanism is clearly not scaling to newer SoCs.
> While this patch works around the problem, IMO, we need a more scalable
> solution.
Agreed.
> For features like IVA and ISP (and SGX) which are acutally IP blocks on
> the SoC, not "features" per-se, what we really need to be doing is
> checking for the presence of the IP block, not checking a bit in a
> register that's not consistent across various SoCs.
>
> We already have all the knowledge about whether the IP blocks are
> present in the SoC-specific hwmod data. So checking for the "feature"
> of a specific IP block should instead be done using an
> omap_hwmod_lookup().
>
> However, there's a bit of a snag because this "feature" detection is
> currently done before the hwmods are registered.
>
> As a quick-and-dirty proof of concept, the patch/hack below moves the
> feature checking after the hwmod init (omap3 only currently) and uses
> omap_hwmod_lookup() to check whether a given IP block exists.
>
> I only did a quick test on one OMAP3 platform (3430/n900) and it seems
> to work. The init order changes need some more thought, as I didn't
> fully validate whether the feature detection can be safely moved later
> for all platforms.
>
> This is just to show the direction we should be taking this SoC
> detection for newer SoCs.
This should be coordinated with the splitting of feature detection
as posted by Vaibhave in thread "[RFC PATCH] arm:omap: cleanup & split
omap2/3/4_check_revision function" thread.
We no longer need the SoC detection super early, so I suggest we make
the feature detection separate from SoC detection.
The SoC specific init can then call:
omap3_check_revision();
ti816x_check_features();
Regards,
Tony
next prev parent reply other threads:[~2011-12-07 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 23:51 [PATCH] AM35xx: disable checking for reserved feature bits Ilya Yanok
2011-11-09 0:57 ` Kevin Hilman
2011-12-07 23:58 ` Tony Lindgren [this message]
2011-12-10 1:21 ` Kevin Hilman
2011-12-16 11:31 ` Hiremath, Vaibhav
2011-12-20 10:55 ` Hiremath, Vaibhav
2012-01-05 1:18 ` Kevin Hilman
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=20111207235825.GS31337@atomide.com \
--to=tony@atomide.com \
--cc=dzu@denx.de \
--cc=hvaibhav@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=sasha_d@emcraft.com \
--cc=wd@denx.de \
--cc=yanok@emcraft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.