From: Johannes Thumshirn <jthumshirn@suse.de>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Andreas Werner <andreas.werner@men.de>, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] mcb: export FPGA information via sysfs
Date: Fri, 18 Mar 2016 15:26:35 +0100 [thread overview]
Message-ID: <cover.1458311073.git.jthumshirn@suse.de> (raw)
The following series adds a way to obtain information about a MCB FPGA via
sysfs. This is viable i.e. for a field technician to check if the latest FPGA
bitstream version is applied to the hardware.
The first patch layes the foundation in order to get sysfs correctly working
with MCB and the second patch exports the bus information into sysfs.
Changes from v1:
* Address kbuild robots warning about broken bisectability
Johannes Thumshirn (2):
mcb: Correctly initialize the bus's device
mcb: export bus information via sysfs
Documentation/ABI/testing/sysfs-bus-mcb | 29 ++++++++++++
drivers/mcb/mcb-core.c | 79 +++++++++++++++++++++++++++++++--
drivers/mcb/mcb-internal.h | 1 -
drivers/mcb/mcb-parse.c | 15 +++----
include/linux/mcb.h | 14 ++++--
5 files changed, 121 insertions(+), 17 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-bus-mcb
--
2.7.2
next reply other threads:[~2016-03-18 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 14:26 Johannes Thumshirn [this message]
2016-03-18 14:26 ` [PATCH v2 1/2] mcb: Correctly initialize the bus's device Johannes Thumshirn
2016-04-08 7:06 ` Andreas Werner
2016-04-08 7:28 ` Johannes Thumshirn
2016-03-18 14:26 ` [PATCH v2 2/2] mcb: export bus information via sysfs Johannes Thumshirn
2016-04-08 7:07 ` Andreas Werner
2016-04-08 7:28 ` Johannes Thumshirn
-- strict thread matches above, loose matches on Subject: below --
2016-03-18 13:49 [PATCH 0/2] mcb: export FPGA " Johannes Thumshirn
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=cover.1458311073.git.jthumshirn@suse.de \
--to=jthumshirn@suse.de \
--cc=andreas.werner@men.de \
--cc=linux-kernel@vger.kernel.org \
/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