From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Joseph Telaak <joseph@telaak.dev>
Cc: Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Chuanhong Guo <gch981213@gmail.com>, Yao Zi <me@ziyao.cc>,
linux-mips@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] clk: siflower: Add SF19A2890 peripheral clock and reset manager driver
Date: Fri, 6 Nov 2026 18:00:25 +0100 [thread overview]
Message-ID: <au4Hc7LAXH-ujDPj@monoceros> (raw)
In-Reply-To: <20261104-sf19a2890-sysm-v1-4-a4fac07df823@telaak.dev>
[-- Attachment #1: Type: text/plain, Size: 1746 bytes --]
On Wed, Nov 04, 2026 at 02:21:01AM -0500, Joseph Telaak wrote:
> +#include <linux/mod_devicetable.h>
> +#include <linux/platform_device.h>
Please don't use <linux/mod_devicetable.h>. <linux/platform_device.h> is
good enough to provide of_device_id already. If you insist on full iwyu,
please use <linux/device-id/of.h> instead.
> +static const struct of_device_id sf19a2890_periphcrm_dt_ids[] = {
> + { .compatible = "siflower,sf19a2890-gmac-crm", .data = &sf19a2890_gmac_crm },
> + { .compatible = "siflower,sf19a2890-gpio-crm", .data = &sf19a2890_gpio_crm },
> + { .compatible = "siflower,sf19a2890-i2c-crm", .data = &sf19a2890_i2c0_crm },
> + { .compatible = "siflower,sf19a2890-pwm-crm", .data = &sf19a2890_pwm_crm },
> + { .compatible = "siflower,sf19a2890-rf-crm", .data = &sf19a2890_rf_crm },
> + { .compatible = "siflower,sf19a2890-spi-crm", .data = &sf19a2890_spi_crm },
> + { .compatible = "siflower,sf19a2890-timer-crm", .data = &sf19a2890_timer_crm },
> + { .compatible = "siflower,sf19a2890-uart-crm", .data = &sf19a2890_uart_crm },
> + { .compatible = "siflower,sf19a2890-usb-crm", .data = &sf19a2890_usb_crm },
> + { .compatible = "siflower,sf19a2890-wdt-crm", .data = &sf19a2890_wdt_crm },
> + { .compatible = "siflower,sf19a2890-wlan24-crm", .data = &sf19a2890_wlan24_crm },
> + { .compatible = "siflower,sf19a2890-wlan5-crm", .data = &sf19a2890_wlan5_crm },
> + { /* sentinel */ },
Please drop the trailing , after the list terminator.
> +};
> +
> +static struct platform_driver sf19a2890_periphcrm_driver = {
> + .probe = sf19a2890_periphcrm_probe,
> + .driver = {
> + .name = "sf19a2890-periph-crm",
> + .of_match_table = sf19a2890_periphcrm_dt_ids,
> + },
> +};
> +builtin_platform_driver(sf19a2890_periphcrm_driver);
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-11-06 17:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 7:20 [PATCH 0/4] clk: Add the Siflower SF19A2890 clock manager and peripheral clock and reset managers Joseph Telaak
2026-11-04 7:20 ` Joseph Telaak via B4 Relay
2026-11-04 7:20 ` [PATCH 1/4] dt-bindings: clock: Add Siflower SF19A2890 clock manager Joseph Telaak
2026-11-04 7:20 ` Joseph Telaak via B4 Relay
2026-11-05 0:04 ` Conor Dooley
2026-11-04 7:20 ` [PATCH 2/4] clk: siflower: Add SF19A2890 clock manager driver Joseph Telaak
2026-11-04 7:20 ` Joseph Telaak via B4 Relay
2026-11-04 7:34 ` sashiko-bot
2026-11-04 7:21 ` [PATCH 3/4] dt-bindings: clock: Add Siflower SF19A2890 peripheral clock/reset managers Joseph Telaak
2026-11-04 7:21 ` Joseph Telaak via B4 Relay
2026-11-04 7:27 ` sashiko-bot
2026-11-05 0:03 ` Conor Dooley
2026-11-05 1:08 ` Joseph Telaak
2026-11-05 1:19 ` Conor Dooley
2026-11-05 3:36 ` Joseph Telaak
2026-11-06 0:12 ` Conor Dooley
2026-11-06 0:34 ` Joseph Telaak
2026-11-04 7:21 ` [PATCH 4/4] clk: siflower: Add SF19A2890 peripheral clock and reset manager driver Joseph Telaak
2026-11-04 7:21 ` Joseph Telaak via B4 Relay
2026-11-04 9:25 ` Philipp Zabel
2026-11-04 13:37 ` Chuanhong Guo
2026-11-04 20:10 ` Joseph Telaak
2026-11-04 13:32 ` Chuanhong Guo
2026-11-04 20:12 ` Joseph Telaak
2026-11-06 17:00 ` Uwe Kleine-König [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=au4Hc7LAXH-ujDPj@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=bmasney+clk@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gch981213@gmail.com \
--cc=jbrunet+clk@baylibre.com \
--cc=joseph@telaak.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=me@ziyao.cc \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sboyd@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.