From: Sven Van Asbroeck <thesven73@gmail.com>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Lee Jones" <lee.jones@linaro.org>,
mark.rutland@arm.com, "Andreas Färber" <afaerber@suse.de>,
treding@nvidia.com, "David Lechner" <david@lechnology.com>,
noralf@tronnes.org, johan@kernel.org,
"Michal Simek" <monstr@monstr.eu>,
michal.vokac@ysoft.com, "Arnd Bergmann" <arnd@arndb.de>,
"Greg KH" <gregkh@linuxfoundation.org>,
john.garry@huawei.com, geert+renesas@glider.be,
robin.murphy@arm.com,
"Paul Gortmaker" <paul.gortmaker@windriver.com>,
sebastien.bourdelin@savoirfairelinux.com, icenowy@aosc.io,
"Stuart Yoder" <stuyoder@gmail.com>,
"J. Kiszka" <jan.kiszka@siemens.com>,
maxime.ripard@bootlin.com,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH v11 2/7] anybus-s: support HMS Anybus-S bus
Date: Tue, 16 Apr 2019 14:43:49 -0400 [thread overview]
Message-ID: <CAGngYiX3QP25MLupsc-=gfb6CAh5wK49eGs2xqHh_5LxrKtaAA@mail.gmail.com> (raw)
In-Reply-To: <4aecef30-0d64-c5f7-c4de-43b0754e2fdd@metux.net>
On Tue, Apr 16, 2019 at 1:10 PM Enrico Weigelt, metux IT consult
<lkml@metux.net> wrote:
>
> Is it some proprietary backplane bus, where things like eg. fieldbus
> adapters are attached to ?
>
> I see some struct bus_type field declaration - is that going to be some
> subsystem, similar to those for other bus'es (eg. pci, usb, ...) ?
>
Correct on both points :)
The author of this proprietary standard (HMS) calls this a bus, but only
a single card can be connected to a slot. So it's not like pci or usb,
where you can connect multiple devices to a host.
> Maybe that deserves a bit more documentation :p
>
Sure, I can do that. What would be the best location for this?
The commit message? The Kconfig blurb? Comments in host.c?
Somewhere in Documentation/ ?
Sven
next prev parent reply other threads:[~2019-04-16 18:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 15:56 [PATCH v11 0/7] Add Fieldbus subsystem + support HMS Profinet card Sven Van Asbroeck
2019-04-16 15:56 ` [PATCH v11 1/7] fieldbus_dev: add Fieldbus Device subsystem Sven Van Asbroeck
2019-04-16 15:56 ` [PATCH v11 2/7] anybus-s: support HMS Anybus-S bus Sven Van Asbroeck
2019-04-16 17:06 ` Enrico Weigelt, metux IT consult
2019-04-16 18:43 ` Sven Van Asbroeck [this message]
2019-04-16 20:58 ` Enrico Weigelt, metux IT consult
2019-04-16 22:00 ` Sven Van Asbroeck
2019-04-17 15:25 ` Enrico Weigelt, metux IT consult
2019-04-18 17:44 ` Sven Van Asbroeck
2019-04-24 10:25 ` Enrico Weigelt, metux IT consult
2019-04-24 13:58 ` Sven Van Asbroeck
2019-04-16 15:56 ` [PATCH v11 3/7] anybus-s: support the Arcx anybus controller Sven Van Asbroeck
2019-04-16 17:27 ` Enrico Weigelt, metux IT consult
2019-04-16 18:35 ` Sven Van Asbroeck
2019-04-16 21:05 ` Enrico Weigelt, metux IT consult
2019-04-16 21:23 ` Sven Van Asbroeck
2019-04-17 8:39 ` Enrico Weigelt, metux IT consult
2019-04-17 14:17 ` Sven Van Asbroeck
2019-04-18 8:15 ` Enrico Weigelt, metux IT consult
2019-04-18 8:18 ` Enrico Weigelt, metux IT consult
2019-04-18 13:18 ` Sven Van Asbroeck
2019-04-16 15:56 ` [PATCH v11 4/7] dt-bindings: anybus-controller: document devicetree binding Sven Van Asbroeck
2019-04-16 15:56 ` [PATCH v11 5/7] dt-bindings: Add vendor prefix for arcx / Archronix Sven Van Asbroeck
2019-04-16 15:56 ` [PATCH v11 6/7] fieldbus_dev: support HMS Profinet IRT industrial controller Sven Van Asbroeck
2019-04-16 15:56 ` [PATCH v11 7/7] staging: fieldbus_dev: add TODO Sven Van Asbroeck
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='CAGngYiX3QP25MLupsc-=gfb6CAh5wK49eGs2xqHh_5LxrKtaAA@mail.gmail.com' \
--to=thesven73@gmail.com \
--cc=afaerber@suse.de \
--cc=arnd@arndb.de \
--cc=david@lechnology.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=icenowy@aosc.io \
--cc=jan.kiszka@siemens.com \
--cc=johan@kernel.org \
--cc=john.garry@huawei.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=michal.vokac@ysoft.com \
--cc=monstr@monstr.eu \
--cc=netdev@vger.kernel.org \
--cc=noralf@tronnes.org \
--cc=paul.gortmaker@windriver.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sebastien.bourdelin@savoirfairelinux.com \
--cc=stuyoder@gmail.com \
--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).