From: Florian Fainelli <f.fainelli@gmail.com>
To: Zev Weiss <zev@bewilderbeest.net>, openbmc@lists.ozlabs.org
Cc: "Krzysztof Wilczyński" <kw@linux.com>,
linux-aspeed@lists.ozlabs.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Jeremy Kerr" <jk@codeconstruct.com.au>,
"Francis Laniel" <laniel_francis@privacyrequired.com>,
"Frank Rowand" <frowand.list@gmail.com>,
"Andrey Konovalov" <andreyknvl@gmail.com>,
"Alexey Dobriyan" <adobriyan@gmail.com>,
devicetree@vger.kernel.org, "Kees Cook" <keescook@chromium.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"Dan Williams" <dan.j.williams@intel.com>,
linux-arm-kernel@lists.infradead.org,
"Daniel Axtens" <dja@axtens.net>,
"Andy Shevchenko" <andy@kernel.org>,
"Andrew Jeffery" <andrew@aj.id.au>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>,
"Heiner Kallweit" <hkallweit1@gmail.com>
Subject: Re: [PATCH 0/9] Dynamic DT device nodes
Date: Wed, 6 Oct 2021 19:46:08 -0700 [thread overview]
Message-ID: <99b43bbf-b63e-d684-dd61-3087e9f22dc4@gmail.com> (raw)
In-Reply-To: <20211007000954.30621-1-zev@bewilderbeest.net>
On 10/6/2021 5:09 PM, Zev Weiss wrote:
> Hello,
>
> This patch series is in some ways kind of a v2 for the "Dynamic
> aspeed-smc flash chips via 'reserved' DT status" series I posted
> previously [0], but takes a fairly different approach suggested by Rob
> Herring [1] and doesn't actually touch the aspeed-smc driver or
> anything in the MTD subsystem, so I haven't marked it as such.
>
> To recap a bit of the context from that series, in OpenBMC there's a
> need for certain devices (described by device-tree nodes) to be able
> to be attached and detached at runtime (for example the SPI flash for
> the host's firmware, which is shared between the BMC and the host but
> can only be accessed by one or the other at a time). To provide that
> ability, this series adds support for a new common device-tree
> property, a boolean "dynamic" that indicates that the device may come
> and go at runtime. When present on a node, the sysfs file for that
> node's "status" property is made writable, allowing userspace to do
> things like:
>
> $ echo okay > /sys/firmware/devicetree/.../status
> $ echo reserved > /sys/firmware/devicetree/.../status
>
> to activate and deactivate a dynamic device.
This is a completely drive by comment here, but cannot you already
achieve what you want today by making the SPI-NOR to be loaded as a
module, probe it when you need it from the BMC, and unbind or rmmod the
drive when you need it on the server/host attached to the BMC?
Looking at [0] there appears to be enough signaling visible by the BMC's
user-space that it ought to be possible?
Assuming that there may be multiple flash chips and you somehow need to
access one in order to complete the BMC device boot, but not the other
one(s), you could imagine unbinding the spi-nor driver from the ones you
don't want to drive and wait until you have appropriate signaling made
available to your or is there a risk of racing with the host in doing so?
--
Florian
next prev parent reply other threads:[~2021-10-07 2:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 0:09 [PATCH 0/9] Dynamic DT device nodes Zev Weiss
2021-10-07 0:09 ` [PATCH 1/9] sysfs: add sysfs_remove_bin_file_self() function Zev Weiss
2021-10-07 5:23 ` Greg Kroah-Hartman
2021-10-07 5:58 ` Zev Weiss
2021-10-07 6:12 ` Greg Kroah-Hartman
2021-10-07 6:55 ` Zev Weiss
2021-10-07 0:09 ` [PATCH 2/9] sysfs: add growable flag to struct bin_attribute Zev Weiss
2021-10-07 0:09 ` [PATCH 3/9] lib/string: add sysfs_buf_streq() Zev Weiss
2021-10-07 0:09 ` [PATCH 4/9] of: add self parameter to __of_sysfs_remove_bin_file() Zev Weiss
2021-10-07 5:25 ` Greg Kroah-Hartman
2021-10-07 0:09 ` [PATCH 5/9] of: add self parameter to of_update_property() Zev Weiss
2021-10-07 5:26 ` Greg Kroah-Hartman
2021-10-07 0:09 ` [PATCH 6/9] of: add support for 'dynamic' DT property Zev Weiss
2021-10-08 18:51 ` Frank Rowand
2021-10-08 19:19 ` Frank Rowand
2021-10-11 13:58 ` Frank Rowand
2021-10-11 14:46 ` Frank Rowand
2021-10-11 17:35 ` Zev Weiss
2021-10-07 0:09 ` [PATCH 7/9] of: make OF_DYNAMIC selectable independently of OF_UNITTEST Zev Weiss
2021-10-08 19:01 ` Frank Rowand
2021-10-07 0:09 ` [PATCH 8/9] dt-bindings: document new 'dynamic' common property Zev Weiss
2021-10-07 5:26 ` Greg Kroah-Hartman
2021-10-07 6:03 ` Zev Weiss
2021-10-07 0:09 ` [PATCH 9/9] ARM: dts: aspeed: Add e3c246d4i BIOS flash device Zev Weiss
2021-10-07 2:46 ` Florian Fainelli [this message]
2021-10-07 5:44 ` [PATCH 0/9] Dynamic DT device nodes Zev Weiss
2021-10-07 7:04 ` Andy Shevchenko
2021-10-07 9:05 ` Zev Weiss
2021-10-07 10:31 ` Greg Kroah-Hartman
2021-10-07 15:41 ` Zev Weiss
2021-10-07 20:03 ` Rob Herring
2021-10-08 5:41 ` Greg Kroah-Hartman
2021-10-08 19:43 ` Frank Rowand
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=99b43bbf-b63e-d684-dd61-3087e9f22dc4@gmail.com \
--to=f.fainelli@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrew@aj.id.au \
--cc=andreyknvl@gmail.com \
--cc=andy@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dja@axtens.net \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=jk@codeconstruct.com.au \
--cc=keescook@chromium.org \
--cc=kw@linux.com \
--cc=laniel_francis@privacyrequired.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=openbmc@lists.ozlabs.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=zev@bewilderbeest.net \
/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).