From: Tony Lindgren <tony@atomide.com>
To: Frank Rowand <frowand.list@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
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>,
Nishanth Menon <nm@ti.com>, Tero Kristo <t-kristo@ti.com>,
Tom Rini <trini@konsulko.com>
Subject: Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states
Date: Thu, 8 Sep 2016 13:19:31 -0700 [thread overview]
Message-ID: <20160908201931.kvkqn5cuowovxph3@atomide.com> (raw)
In-Reply-To: <57D1B959.5090108@gmail.com>
* Frank Rowand <frowand.list@gmail.com> [160908 12:18]:
> > On 09/08/16 08:58, Tony Lindgren wrote:
> >> Just to consider other ways of doing it, we could use the compatible
> >> flag to tag devices that need to be just idled on probe, but that does
> >> not seem like generic solution to me.
> >
> > Yuck. Again overloading a property to convey multiple pieces of
> > information.
>
> I should have been more explicit in that statement.
>
> If the hardware device does not have "wires" routed to a connector or
> bus then it is still the same device. Thus the compatible should be
> the same.
>
> The difference is the way the device is used in the SOC or board.
That is correct. The device is exactly the same.
Regards,
Tony
next prev parent reply other threads:[~2016-09-08 20:19 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 [this message]
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
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=20160908201931.kvkqn5cuowovxph3@atomide.com \
--to=tony@atomide.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=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
--cc=trini@konsulko.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;
as well as URLs for NNTP newsgroup(s).