[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdU_90EhPng0NYPVmWAwDt2NOowB3thPB+jJarme-A7eew@mail.gmail.com>
Date: Fri, 11 Oct 2013 08:52:00 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc: Greg KH <gregkh@...uxfoundation.org>, Tejun Heo <tj@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: sysfs for my chips
On Thu, Oct 10, 2013 at 11:30 PM, Benjamin Herrenschmidt
<benh@...nel.crashing.org> wrote:
> On Thu, 2013-10-10 at 22:26 +0200, Geert Uytterhoeven wrote:
>> > This is not CPUs. CPUs are threads really. Even if they were cores,
>> that
>> > still wouldn't cut it. I'm looking at chips here and not all of them
>> > actually processor chips. The SCOM bus address space is global to a
>> > physical chip and allows to access various resources that are only
>> > remotely related to the cores on it.
>>
>> What about a "bus" for the sideband bus? That allows to decouple it
>> from cores, and allows to support non-processor chips, too?
>
> 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).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists