From: Linus Walleij <linus.walleij@linaro.org>
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
svendev@arcx.com, "Lee Jones" <lee.jones@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Andreas Färber" <afaerber@suse.de>,
"Thierry Reding" <treding@nvidia.com>,
"David Lechner" <david@lechnology.com>,
"Noralf Trønnes" <noralf@tronnes.org>,
"Johan Hovold" <johan@kernel.org>,
"Michal Simek" <monstr@monstr.eu>,
michal.vokac@ysoft.com, "Greg KH" <gregkh@linuxfoundation.org>,
john.garry@huawei.com,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Robin Murphy" <robin.murphy@arm.com>,
"Paul Gortmaker" <paul.gortmaker@windriver.com>,
"Sebastien Bourdelin" <sebastien.bourdelin@savoirfairelinux.com>,
"Icenowy Zheng" <icenowy@aosc.io>,
"Stuart Yoder" <stuyoder@gmail.com>
Subject: Re: [PATCH anybus v2 1/5] misc: support the Arcx anybus bridge.
Date: Thu, 1 Nov 2018 22:53:46 +0100 [thread overview]
Message-ID: <CACRpkdZkv6ikrFmJptBTwftj7TkR5Bce9e2R1ceTw_pLqH1LcA@mail.gmail.com> (raw)
In-Reply-To: <CAGngYiVorxYY+8e75068i4=PJi1gEvnGkgvBfi0+9H+c1qD-oQ@mail.gmail.com>
On Thu, Nov 1, 2018 at 6:17 PM Sven Van Asbroeck <thesven73@gmail.com> wrote:
> >> +static DEVICE_ATTR_RO(version);
> >
> > Do you need this in userspace really?
> >
> >> +static DEVICE_ATTR_RO(design_number);
> >
> > And this?
>
> Unfortunately, I do :(
> The application software reads these out and displays them in an UI. It's
> important to be able to see these on a running device.
OK...
> Perhaps there is another kernel abstraction I could use?
I don't think so. If you want to be pedantic, document the sysfs
files in Documentation/ABI/testing/sysfs-*
Maybe the properties should be on the bus though? I don't know :/
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-11-01 21:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 19:44 [PATCH anybus v2 0/5] Support HMS Profinet Card over Anybus thesven73
2018-10-31 19:44 ` [PATCH anybus v2 1/5] misc: support the Arcx anybus bridge thesven73
2018-10-31 23:15 ` Linus Walleij
2018-11-01 17:17 ` Sven Van Asbroeck
2018-11-01 21:53 ` Linus Walleij [this message]
2018-11-02 14:16 ` Sven Van Asbroeck
2018-10-31 19:44 ` [PATCH anybus v2 2/5] dt-bindings: anybus-bridge: document devicetree binding thesven73
2018-10-31 23:29 ` Andreas Färber
2018-10-31 19:44 ` [PATCH anybus v2 3/5] bus: support HMS Anybus-S bus thesven73
2018-11-15 0:19 ` kbuild test robot
2018-10-31 19:44 ` [PATCH anybus v2 4/5] dt-bindings: anybuss-host: document devicetree binding thesven73
2018-10-31 19:44 ` [PATCH anybus v2 5/5] misc: support HMS Profinet IRT industrial controller thesven73
2018-11-01 16:03 ` kbuild test robot
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=CACRpkdZkv6ikrFmJptBTwftj7TkR5Bce9e2R1ceTw_pLqH1LcA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--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=johan@kernel.org \
--cc=john.garry@huawei.com \
--cc=lee.jones@linaro.org \
--cc=mark.rutland@arm.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).