From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robherring2@gmail.com>
Cc: Sagar Dharia <sdharia@codeaurora.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
bp@suse.de, poeschel@lemonage.de,
Thierry Reding <treding@nvidia.com>,
gong.chen@linux.intel.com, andreas.noever@gmail.com,
Alan Cox <alan@linux.intel.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
daniel@ffwll.ch, oded.gabbay@amd.com, jkosina@suse.cz,
sharon.dvir1@mail.huji.ac.il, Joe Perches <joe@perches.com>,
David Miller <davem@davemloft.net>,
James Hogan <james.hogan@imgtec.com>,
michael.opdenacker@free-electrons.com,
Daniel Thompson <daniel.thompson@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
khei
Subject: Re: [PATCH V3 2/6] of/slimbus: OF helper for SLIMbus
Date: Tue, 4 Aug 2015 18:27:36 +0100 [thread overview]
Message-ID: <20150804172736.GA20873@sirena.org.uk> (raw)
In-Reply-To: <CAL_JsqLDzLXR5aC__YhCUzGzVcVYcv_H7QS6zG0vezQPST_Y2Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
On Mon, Aug 03, 2015 at 11:13:55AM -0500, Rob Herring wrote:
> On Mon, Aug 3, 2015 at 1:59 AM, Sagar Dharia <sdharia@codeaurora.org> wrote:
> > +Optional:
> > +- compatible - Slave devices can use compatible field to have a name.
> > + If this field is missing, name of the device will be
> > + determined using slave's enumeration address.
> > + (e.g. in the example below, slave's name will be:
> > + 0x217:0x60:0x1:0x0)
> Are devices discoverable and uniquely identifiable? This would be
> something like a VID/PID which can be read in a generic way. It looks
> like the address contains this info, but can you discover the
> addresses of devices on the bus? If not compatible should not be
> optional.
Yes, the bus is enumerable. However in essentially all implementations
devices won't enumerate without some additional non-standard work being
done to power them on since applications tend to be extremely power
sensitive relative to the basic operating cost of the bus. Which is
entertaining.
This probably means that the binding needs to say that the compatible is
optional but that for all practical purposes Linux requires it until
such time as someone decides it's worth supporting systems that can
usefully enumerate.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-08-04 17:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 6:59 [PATCH V3 0/6] Introduce framework for SLIMbus device drivers Sagar Dharia
2015-08-03 6:59 ` [PATCH V3 1/6] SLIMbus: Device management on SLIMbus Sagar Dharia
2015-08-14 18:17 ` Mark Brown
2015-08-03 6:59 ` [PATCH V3 2/6] of/slimbus: OF helper for SLIMbus Sagar Dharia
2015-08-03 16:13 ` Rob Herring
2015-08-04 17:27 ` Mark Brown [this message]
2015-08-06 19:10 ` Sagar Dharia
2015-08-03 6:59 ` [PATCH V3 3/6] slimbus: Add messaging APIs to slimbus framework Sagar Dharia
2015-08-14 18:25 ` Mark Brown
2015-08-14 18:33 ` Mark Brown
2015-08-03 6:59 ` [PATCH V3 4/6] slim: qcom: Add Qualcomm Slimbus controller driver Sagar Dharia
2015-08-14 18:31 ` Mark Brown
[not found] ` <20150814183106.GE10748-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-08-17 23:44 ` Sagar Dharia
2015-08-03 6:59 ` [PATCH V3 5/6] slimbus: Add support for 'clock-pause' feature Sagar Dharia
2015-08-14 18:39 ` Mark Brown
2015-08-17 23:43 ` Sagar Dharia
2015-08-03 6:59 ` [PATCH V3 6/6] slim: qcom: Add runtime-pm support using clock-pause feature Sagar Dharia
2015-08-14 18:43 ` Mark Brown
2015-08-14 18:46 ` [PATCH V3 0/6] Introduce framework for SLIMbus device drivers Mark Brown
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=20150804172736.GA20873@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alan@linux.intel.com \
--cc=andreas.noever@gmail.com \
--cc=bp@suse.de \
--cc=daniel.thompson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gong.chen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=james.hogan@imgtec.com \
--cc=jkosina@suse.cz \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=michael.opdenacker@free-electrons.com \
--cc=oded.gabbay@amd.com \
--cc=pawel.moll@arm.com \
--cc=poeschel@lemonage.de \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.com \
--cc=sdharia@codeaurora.org \
--cc=sharon.dvir1@mail.huji.ac.il \
--cc=treding@nvidia.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).