From: "Marek Behún" <kabel@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>, soc@kernel.org
Cc: arm@kernel.org, "Andy Shevchenko" <andy@kernel.org>,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Marek Behún" <kabel@kernel.org>
Subject: [PATCH 0/4] Make turris-omnia-mcu driver parts optional
Date: Fri, 19 Jul 2024 10:57:52 +0200 [thread overview]
Message-ID: <20240719085756.30598-1-kabel@kernel.org> (raw)
Hi Arnd,
this series solves the Kconfig dependency issues of the turris-omnia-mcu
driver by making the GPIO, poweroff & wakeup, watchdog and TRNG parts of
the driver optional, under new Kconfig options. The dependencies to
subsystems are moved under these new options.
Marek
Marek Behún (4):
platform: cznic: turris-omnia-mcu: Make watchdog code optional
platform: cznic: turris-omnia-mcu: Make TRNG code optional
platform: cznic: turris-omnia-mcu: Make poweroff and wakeup code
optional
platform: cznic: turris-omnia-mcu: Make GPIO code optional
drivers/platform/cznic/Kconfig | 80 +++++++++++++------
drivers/platform/cznic/Makefile | 8 +-
.../platform/cznic/turris-omnia-mcu-base.c | 4 +
drivers/platform/cznic/turris-omnia-mcu.h | 42 +++++++++-
4 files changed, 103 insertions(+), 31 deletions(-)
--
2.44.2
next reply other threads:[~2024-07-19 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 8:57 Marek Behún [this message]
2024-07-19 8:57 ` [PATCH 1/4] platform: cznic: turris-omnia-mcu: Make watchdog code optional Marek Behún
2024-07-19 8:57 ` [PATCH 2/4] platform: cznic: turris-omnia-mcu: Make TRNG " Marek Behún
2024-07-19 8:57 ` [PATCH 3/4] platform: cznic: turris-omnia-mcu: Make poweroff and wakeup " Marek Behún
2024-07-19 8:57 ` [PATCH 4/4] platform: cznic: turris-omnia-mcu: Make GPIO " Marek Behún
2024-08-06 20:08 ` [PATCH 0/4] Make turris-omnia-mcu driver parts optional patchwork-bot+linux-soc
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=20240719085756.30598-1-kabel@kernel.org \
--to=kabel@kernel.org \
--cc=andy@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=soc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.