From: Saravana Kannan <saravanak@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Len Brown <lenb@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: Saravana Kannan <saravanak@google.com>,
kernel-team@android.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-acpi@vger.kernel.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Marc Zyngier <maz@kernel.org>,
Tudor Ambarus <Tudor.Ambarus@microchip.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Martin Kaiser <martin@kaiser.cx>
Subject: [PATCH v3 0/4] Make fw_devlink=on more forgiving
Date: Thu, 4 Feb 2021 14:39:17 -0800 [thread overview]
Message-ID: <20210204223921.1693487-1-saravanak@google.com> (raw)
I dropped a few patches from v2 of the series that are still work in
progress. So v3 of the series only includes definitive patches and the
patch numbering has changed.
Patch 1/4 and 2/4 addresses the issue of firmware nodes that look like
they'll have struct devices created for them, but will never actually
have struct devices added for them. For example, DT nodes with a
compatible property that don't have devices added for them.
Patch 3/4 and 4/4 allow for handling optional DT bindings.
v1 -> v2:
Patch 1: Added a flag to fwnodes that aren't devices.
Patch 3: New patch to ise the flag set in patch 1 to not create bad links.
v2 -> v3:
- Patch 1: Added Rafael's Ack
- New patches 3 and 4
Saravana Kannan (4):
driver core: fw_devlink: Detect supplier devices that will never be
added
of: property: Don't add links to absent suppliers
driver core: Add fw_devlink.strict kernel param
of: property: Add fw_devlink support for optional properties
.../admin-guide/kernel-parameters.txt | 5 +++
drivers/base/core.c | 43 +++++++++++++++++--
drivers/of/property.c | 16 +++++--
include/linux/fwnode.h | 3 ++
4 files changed, 60 insertions(+), 7 deletions(-)
--
2.30.0.365.g02bc693789-goog
next reply other threads:[~2021-02-04 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 22:39 Saravana Kannan [this message]
2021-02-04 22:39 ` [PATCH v3 1/4] driver core: fw_devlink: Detect supplier devices that will never be added Saravana Kannan
2021-02-04 22:39 ` [PATCH v3 2/4] of: property: Don't add links to absent suppliers Saravana Kannan
2021-02-04 22:39 ` [PATCH v3 3/4] driver core: Add fw_devlink.strict kernel param Saravana Kannan
2021-02-04 22:39 ` [PATCH v3 4/4] of: property: Add fw_devlink support for optional properties Saravana Kannan
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=20210204223921.1693487-1-saravanak@google.com \
--to=saravanak@google.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=bgolaszewski@baylibre.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=lenb@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=martin@kaiser.cx \
--cc=maz@kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).