| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20190103161538.20637-1-TheSven73@googlemail.com>
Date: Thu, 3 Jan 2019 11:15:32 -0500
From: Sven Van Asbroeck <thesven73@...il.com>
To: 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, david@...hnology.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
Subject: [PATCH fieldbus v6 0/6] Add Fieldbus subsystem + support HMS Profinet card
This patch:
1. adds a Fieldbus subsystem
2. adds support for the HMS Industrial Networks AB Profinet card.
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.
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.
v6:
Randy Dunlap:
correctly/consistently indent Kconfig
spelling/punctuation improvements
Greg KH:
suggestion: simplify /sys/class/fieldbus_dev/fieldbus_devX/ -> /sys/class/fieldbus_dev/X/
can't simplify: create_device() also determines the name of the
associated char device. simplification would result in a char device
named /dev/X ?
applied above suggestion to arcx-controller driver, this works ok as it does not
have associated char device
class name left as-is (fieldbus_dev) to differentiate between
"fieldbus controller" and "fieldbus device" in the future
makefile clean-up
sysfs attributes: snprintf -> sprintf
except card_name, as it's externally provided and could potentially
be > PAGE_SIZE
enabled/online sysfs attributes converted to "0/1" values
using kstrtobool()
v5:
Greg KH:
fix licence nit
consistent use of e-mail address
replaced raw sysfs attribute with kobject_uevent() call
keep __ATTRIBUTE_GROUPS because we need is_visible field
Rob Herring:
controller devicetree entry now requires multiple address
regions and interrupts
controller child node(s) now mapped to child devices by
slot/host position (using devicetree reg = <>)
architectural overhaul to align closely to existing pci arch:
pci anybus
--------------------------------------------------------------------------------
Common bus code (spec), pci/pci_driver.c anybus/dev_core.c
calls bus_register() no of compatible no of compatible
--------------------------------------------------------------------------------
Device on bus, calls
XXX_client_driver_register() hwmon/k8temp.c fieldbus/hms-profinet.c
--------------------------------------------------------------------------------
Controller, silicon driver pci/pcie-tango.c anybus/arcx-anybus.c
platform_driver calls platform_driver calls
pci_host_probe() anybus_host_common_probe()
v4:
general
create fieldbus_dev subsystem, with standardized 'simple'
userspace interface (sysfs + cdev)
remove redundant __packed keywords
use __be16/32 types wherever values are explicitly big-endian
hms-profinet:
remove configuration code, and uapi headers: not supported (yet)
when registering as a fieldbus_dev.
anybuss-host:
use struct kref to reference-count tasks
replace busy loops with usleep_range() loop after 10 tries
use threaded irq so time_before_eq(jiffies, timeout) will
continue to work
allow client devices to be assigned a devicetree node,
in the same way as pci/mmc/...
v3:
devicetree-bindings
adding the vendor prefix is now a separate commit
anybus-bridge:
moved misc driver to drivers/bus/
converted of_gpio_* to gpiod_* abstractions
can power readout is now a fixed-voltage regulator
anybuss-host:
converted refcounts from atomic_t to refcount_t
fixed potential use-after-free
hms-profinet:
applied minor kernel build robot suggestion
v2:
added architecture overview comments to host driver
completely reworked anybus-bridge driver, it becomes a reset controller
anybuss-host driver now needs devicetree entry, link to reset controller
I will hold off on kernel-doc until the overall architecture gets
more validation / approval
fixed Kconfig, comment-style, document ioctl magic numbers
removed redundant pwm dependency
renamed enable-gpios to reset-gpios
stop driving reset-gpio after unloading driver
use interrupt-parent / interrupts method to describe interrupts
in the devicetree
convert references 'i.MX WEIM parallel bus' to 'parallel bus'
replace devicetree functions with more generic platform_get_resource()
platform_get_irq()
added device unique data to add_device_randomness()
v1:
first shot
Sven Van Asbroeck (6):
fieldbus_dev: add Fieldbus Device subsystem.
anybus-s: support HMS Anybus-S bus
anybus-s: support the Arcx anybus controller
dt-bindings: anybus-controller: document devicetree binding
dt-bindings: Add vendor prefix for arcx / Archronix
fieldbus_dev: support HMS Profinet IRT industrial controller
Documentation/ABI/testing/fieldbus-dev-cdev | 31 +
.../ABI/testing/sysfs-class-fieldbus-dev | 62 +
.../fieldbus/arcx,anybus-controller.txt | 71 +
.../devicetree/bindings/vendor-prefixes.txt | 1 +
Documentation/fieldbus_dev/fieldbus_dev.txt | 66 +
drivers/Kconfig | 2 +
drivers/Makefile | 1 +
drivers/fieldbus/Kconfig | 18 +
drivers/fieldbus/Makefile | 10 +
drivers/fieldbus/anybuss/Kconfig | 39 +
drivers/fieldbus/anybuss/Makefile | 10 +
drivers/fieldbus/anybuss/arcx-anybus.c | 399 +++++
drivers/fieldbus/anybuss/hms-profinet.c | 223 +++
drivers/fieldbus/anybuss/host.c | 1459 +++++++++++++++++
drivers/fieldbus/dev_core.c | 348 ++++
include/linux/anybuss-client.h | 104 ++
include/linux/anybuss-controller.h | 47 +
include/linux/fieldbus_dev.h | 105 ++
18 files changed, 2996 insertions(+)
create mode 100644 Documentation/ABI/testing/fieldbus-dev-cdev
create mode 100644 Documentation/ABI/testing/sysfs-class-fieldbus-dev
create mode 100644 Documentation/devicetree/bindings/fieldbus/arcx,anybus-controller.txt
create mode 100644 Documentation/fieldbus_dev/fieldbus_dev.txt
create mode 100644 drivers/fieldbus/Kconfig
create mode 100644 drivers/fieldbus/Makefile
create mode 100644 drivers/fieldbus/anybuss/Kconfig
create mode 100644 drivers/fieldbus/anybuss/Makefile
create mode 100644 drivers/fieldbus/anybuss/arcx-anybus.c
create mode 100644 drivers/fieldbus/anybuss/hms-profinet.c
create mode 100644 drivers/fieldbus/anybuss/host.c
create mode 100644 drivers/fieldbus/dev_core.c
create mode 100644 include/linux/anybuss-client.h
create mode 100644 include/linux/anybuss-controller.h
create mode 100644 include/linux/fieldbus_dev.h
--
2.17.1
Powered by blists - more mailing lists