[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3b0b4c5c-23a6-428c-6060-3e5c314bd9e7@lechnology.com>
Date: Wed, 5 Dec 2018 20:05:33 -0600
From: David Lechner <david@...hnology.com>
To: Sven Van Asbroeck <thesven73@...il.com>, svendev@...x.com,
robh+dt@...nel.org, linus.walleij@...aro.org
Cc: lee.jones@...aro.org, mark.rutland@....com, afaerber@...e.de,
treding@...dia.com, noralf@...nnes.org, johan@...nel.org,
monstr@...str.eu, michal.vokac@...ft.com, arnd@...db.de,
gregkh@...uxfoundation.org, john.garry@...wei.com,
geert+renesas@...der.be, robin.murphy@....com,
paul.gortmaker@...driver.com,
sebastien.bourdelin@...oirfairelinux.com, icenowy@...c.io,
stuyoder@...il.com, maxime.ripard@...tlin.com,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v5 0/6] Add Fieldbus subsystem + support HMS Profinet card
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.
>
Powered by blists - more mailing lists