From: David Lechner <david@lechnology.com>
To: Sven Van Asbroeck <thesven73@gmail.com>,
svendev@arcx.com, robh+dt@kernel.org, linus.walleij@linaro.org
Cc: lee.jones@linaro.org, mark.rutland@arm.com, afaerber@suse.de,
treding@nvidia.com, noralf@tronnes.org, johan@kernel.org,
monstr@monstr.eu, michal.vokac@ysoft.com, arnd@arndb.de,
gregkh@linuxfoundation.org, john.garry@huawei.com,
geert+renesas@glider.be, robin.murphy@arm.com,
paul.gortmaker@windriver.com,
sebastien.bourdelin@savoirfairelinux.com, icenowy@aosc.io,
stuyoder@gmail.com, maxime.ripard@bootlin.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 0/6] Add Fieldbus subsystem + support HMS Profinet card
Date: Wed, 5 Dec 2018 20:05:33 -0600 [thread overview]
Message-ID: <3b0b4c5c-23a6-428c-6060-3e5c314bd9e7@lechnology.com> (raw)
In-Reply-To: <20181204220224.27324-1-TheSven73@googlemail.com>
On 12/4/18 4:02 PM, Sven Van Asbroeck wrote:
> This patch:
> 1. adds a Fieldbus subsystem
> 2. adds support for the HMS Industrial Networks AB Profinet card.
Does this actually need a new fieldbus subsystem or could it just be
implemented as a new network protocol?
>
> 1. Fieldbus subsystem
> ---------------------
>
> Fieldbus device (client) adapters allow data exchange with a PLC aka.
> "Fieldbus Controller" over a fieldbus (Profinet, FLNet, etc.)
> They are typically used when a Linux device wants to expose itself
> as an actuator, motor, console light, switch, etc. over the fieldbus.
> The framework is designed to provide a generic interface to Fieldbus
> Devices from both the Linux Kernel and the userspace.
Then this generic interface to a fieldbus device could just be a socket.
>
> 2. Add support for HMS Profinet Card
> ------------------------------------
>
> Profinet is an industry technical standard for data communication over
> Industrial Ethernet, designed for collecting data from, and controlling,
> equipment in industrial systems, with a particular strength in delivering data
> under tight time constraints (on the order of 1ms or less).
>
> The profinet card itself is connected to the system via an industrial bus
> called 'anybus'.
>
> I have followed the bus driver/client driver pattern, and created an anybus
> bus driver, plus a client driver for the profinet card.
>
> In case this patch set gets (eventually) accepted, drivers for other anybus
> client cards may follow: flnet, cc-link, ...
>
> The anybus slot on the host is located on an 'anybus controller', which is
> custom h/w designed by arcx. It exposes a dual anybus host implementation,
> plus a power readout unrelated to the anybus.
>
next prev parent reply other threads:[~2018-12-06 2:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 22:02 [PATCH v5 0/6] Add Fieldbus subsystem + support HMS Profinet card Sven Van Asbroeck
2018-12-04 22:02 ` [PATCH v5 1/6] fieldbus_dev: add Fieldbus Device subsystem Sven Van Asbroeck
2018-12-05 1:01 ` Randy Dunlap
2018-12-05 1:12 ` Randy Dunlap
2018-12-05 10:16 ` Greg KH
2018-12-05 15:39 ` Sven Van Asbroeck
2018-12-05 19:17 ` Greg KH
2018-12-05 22:32 ` Sven Van Asbroeck
2018-12-05 22:50 ` Arnd Bergmann
2018-12-06 14:07 ` Greg KH
2018-12-06 18:32 ` Sven Van Asbroeck
2018-12-04 22:02 ` [PATCH v5 2/6] anybus-s: support HMS Anybus-S bus Sven Van Asbroeck
2018-12-04 22:02 ` [PATCH v5 3/6] anybus-s: support the Arcx anybus controller Sven Van Asbroeck
2018-12-04 22:02 ` [PATCH v5 4/6] dt-bindings: anybus-controller: document devicetree binding Sven Van Asbroeck
2018-12-07 17:44 ` Rob Herring
2018-12-04 22:02 ` [PATCH v5 5/6] dt-bindings: Add vendor prefix for arcx / Archronix Sven Van Asbroeck
2018-12-04 22:02 ` [PATCH v5 6/6] fieldbus_dev: support HMS Profinet IRT industrial controller Sven Van Asbroeck
2018-12-05 1:03 ` Randy Dunlap
2018-12-06 2:05 ` David Lechner [this message]
2018-12-06 18:32 ` [PATCH v5 0/6] Add Fieldbus subsystem + support HMS Profinet card 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=3b0b4c5c-23a6-428c-6060-3e5c314bd9e7@lechnology.com \
--to=david@lechnology.com \
--cc=afaerber@suse.de \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=icenowy@aosc.io \
--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=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=michal.vokac@ysoft.com \
--cc=monstr@monstr.eu \
--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=svendev@arcx.com \
--cc=thesven73@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).