mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Esteban Blanc <eblanc@baylibre.com>,
	a.zummo@towertech.it, alexandre.belloni@bootlin.com
Cc: andy.shevchenko@gmail.com, linux-kernel@vger.kernel.org,
	linux-rtc@vger.kernel.org, jpanis@baylibre.com,
	jneanne@baylibre.com, u-kumar1@ti.com
Subject: Re: [PATCH v8] rtc: tps6594: Add driver for TPS6594 RTC
Date: Fri, 3 Nov 2023 07:52:52 +0100	[thread overview]
Message-ID: <d5a18d7f-f327-48bb-8b64-cd53e74b4f04@kernel.org> (raw)
In-Reply-To: <20231102132616.1130960-1-eblanc@baylibre.com>

On 02/11/2023 14:26, Esteban Blanc wrote:
> TPS6594 PMIC is a MFD. This patch adds support for
> the RTC found inside TPS6594 family of PMIC.
> 
> Alarm is also supported.
> 
> Signed-off-by: Esteban Blanc <eblanc@baylibre.com>
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> Acked-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> ---

...

> +
> +static struct platform_driver tps6594_rtc_driver = {
> +	.probe		= tps6594_rtc_probe,
> +	.driver		= {
> +		.name	= "tps6594-rtc",
> +	},
> +};
> +
> +module_platform_driver(tps6594_rtc_driver);
> +MODULE_ALIAS("platform:tps6594-rtc");

You should not need MODULE_ALIAS() in normal cases. If you need it,
usually it means your device ID table is wrong (e.g. misses either
entries or MODULE_DEVICE_TABLE()). MODULE_ALIAS() is not a substitute
for incomplete ID table.

This applies also to your other driver: pinctrl. Maybe to all your
drivers... Don't use MODULE_ALIAS() as substitute for missing tables.

Best regards,
Krzysztof


      parent reply	other threads:[~2023-11-03  6:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 13:26 Esteban Blanc
2023-11-02 16:00 ` Andy Shevchenko
2023-11-02 16:17   ` Esteban Blanc
2023-11-02 16:46     ` Andy Shevchenko
2023-11-02 16:50       ` Alexandre Belloni
2023-11-02 17:00         ` Andy Shevchenko
2023-11-02 17:04           ` Alexandre Belloni
2023-11-03  8:55       ` Esteban Blanc
2023-11-03 14:10         ` Andy Shevchenko
2023-11-03  6:52 ` Krzysztof Kozlowski [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=d5a18d7f-f327-48bb-8b64-cd53e74b4f04@kernel.org \
    --to=krzk@kernel.org \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=eblanc@baylibre.com \
    --cc=jneanne@baylibre.com \
    --cc=jpanis@baylibre.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=u-kumar1@ti.com \
    /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

all inboxes | Powered by JetHome®