From: Tom Rini <trini@konsulko.com>
To: Matthijs van Duin <matthijsvanduin@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>, Nishanth Menon <nm@ti.com>,
Frank Rowand <frowand.list@gmail.com>,
Tony Lindgren <tony@atomide.com>,
Grant Likely <grant.likely@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-omap <linux-omap@vger.kernel.org>,
Tero Kristo <t-kristo@ti.com>
Subject: Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states
Date: Mon, 12 Sep 2016 09:49:55 -0400 [thread overview]
Message-ID: <20160912134955.GE13192@bill-the-cat> (raw)
In-Reply-To: <CAALWOA98nPB9MRTmOnxWM3cePuAcxeMmyDRJ8hwo+zQh6HX+ug@mail.gmail.com>
On Mon, Sep 12, 2016 at 03:46:23PM +0200, Matthijs van Duin wrote:
> On 12 September 2016 at 15:35, Tom Rini <trini@konsulko.com> wrote:
> > What do you mean by "you can't put it to good use" ? Is that the case
> > of stuff that's say exposed via a header and could be used but isn't (ie
> > the cape/hat/chip/etc case) or the IP block is still OK but just not
> > exposed at all?
> >
> > What we're trying to address here is the case of "don't even try to
> > use the peripheral, bad things will happen. But please properly idle
> > the IP block!".
>
> I'm pretty sure IP blocks in the "don't even try" category are
> necessarily idled. There's no reason they wouldn't be.
OK. But this is specifically about the blocks that we are being told by
the vendor are _not_ idled and need to be.
--
Tom
next prev parent reply other threads:[~2016-09-12 13:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 22:35 [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states Tony Lindgren
2016-08-30 0:23 ` Rob Herring
2016-08-30 0:39 ` Tony Lindgren
2016-08-31 17:47 ` Tony Lindgren
2016-08-31 20:50 ` Frank Rowand
2016-08-31 21:41 ` Tony Lindgren
2016-09-08 13:38 ` Rob Herring
2016-09-08 14:20 ` Nishanth Menon
2016-09-08 15:58 ` Tony Lindgren
2016-09-08 19:09 ` Frank Rowand
2016-09-08 19:17 ` Frank Rowand
2016-09-08 20:19 ` Tony Lindgren
2016-09-08 19:05 ` Frank Rowand
2016-09-09 2:43 ` Rob Herring
2016-09-09 14:10 ` Tom Rini
2016-09-10 1:11 ` Matthijs van Duin
2016-09-12 13:35 ` Tom Rini
2016-09-12 13:46 ` Matthijs van Duin
2016-09-12 13:49 ` Tom Rini [this message]
2016-09-12 13:38 ` Tom Rini
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=20160912134955.GE13192@bill-the-cat \
--to=trini@konsulko.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=matthijsvanduin@gmail.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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