From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg KH <gregkh@linuxfoundation.org>, Tejun Heo <tj@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: sysfs for my chips
Date: Fri, 11 Oct 2013 20:06:40 +1100 [thread overview]
Message-ID: <1381482400.5630.79.camel@pasglop> (raw)
In-Reply-To: <CAMuHMdU_90EhPng0NYPVmWAwDt2NOowB3thPB+jJarme-A7eew@mail.gmail.com>
On Fri, 2013-10-11 at 08:52 +0200, Geert Uytterhoeven wrote:
> > Not sure what you mean .... create a linux bus type with devices on
> > it ?
>
> Yes, that's what I meant.
>
> >From the nodes on that bus you can have symlinks in sysfs to e.g. the CPUs
> in the rest of the sysfs tree.
>
> It's a bit like smbus/i2c connecting various peripherals that may also be
> connected in some other way (e.g. media devices).
It's fairly overkill though ... we don't really plan to expose much of
these things to Linux anyway, it's mostly buried in firmware, I just
want scom access to userspace for debug/diagnostics.
I don't want it in debugfs however because we might want some "health
monitoring" daemon running in userspace that uses it to check some of
the built-in CE statistics etc... in the various chips and handle some
of the repair work. I prefer having that stuff in userspace (it's fairly
complex) than in firmware but it will get all the data it needs from the
device-tree, there's no point trying to reproduce the whole chip
hierarchy and sub hierarchy in Linux.
Cheers,
Ben.
prev parent reply other threads:[~2013-10-11 9:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 4:19 sysfs for my chips Benjamin Herrenschmidt
2013-10-10 7:03 ` [PATCH] sysfs/bin: Fix size handling overflow for bin_attribute Benjamin Herrenschmidt
2013-10-10 17:38 ` Greg KH
2013-10-10 17:40 ` Greg KH
2013-10-10 20:02 ` Benjamin Herrenschmidt
2013-10-10 17:44 ` sysfs for my chips Greg KH
2013-10-10 20:01 ` Benjamin Herrenschmidt
2013-10-10 20:26 ` Geert Uytterhoeven
2013-10-10 21:30 ` Benjamin Herrenschmidt
2013-10-11 6:52 ` Geert Uytterhoeven
2013-10-11 9:06 ` Benjamin Herrenschmidt [this message]
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=1381482400.5630.79.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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