From: Lee Jones <lee@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <chris.paterson2@renesas.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v11 2/6] clocksource/drivers: Add Renesas RZ/G2L MTU3a core driver
Date: Thu, 26 Jan 2023 14:41:26 +0000 [thread overview]
Message-ID: <Y9KRFnc207xAeVvJ@google.com> (raw)
In-Reply-To: <9f722f37-15da-0384-c059-a4af0f1dab10@linaro.org>
On Thu, 26 Jan 2023, Daniel Lezcano wrote:
> On 13/01/2023 17:17, Biju Das wrote:
>
> [ ... ]
>
> > +config RZ_MTU3
> > + bool "Renesas RZ/G2L MTU3a core driver"
> > + select MFD_CORE
> > + depends on (ARCH_RZG2L && OF) || COMPILE_TEST
> > + help
> > + Select this option to enable Renesas RZ/G2L MTU3a core driver for
> > + the Multi-Function Timer Pulse Unit 3 (MTU3a) hardware available
> > + on SoCs from Renesas. The core driver shares the clk and channel
> > + register access for the other child devices like Counter, PWM,
> > + Clock Source, and Clock event.
>
> Do you really want to have this option manually selectable? Usually we try
> to avoid that and keep a silent option which is selected by the platform
> config.
>
> [ ... ]
>
> > +
> > + ret = mfd_add_devices(&pdev->dev, 0, rz_mtu3_devs,
> > + ARRAY_SIZE(rz_mtu3_devs), NULL, 0, NULL);
> > + if (ret < 0)
> > + goto err_assert;
> > +
> > + return devm_add_action_or_reset(&pdev->dev, rz_mtu3_reset_assert,
> > + &pdev->dev);
> > +
> > +err_assert:
> > + reset_control_assert(ddata->rstc);
> > + return ret;
> > +}
>
> I'm not sure this driver falls under the clocksource umbrella but under mfd
> [cc'ed Lee Jones]
Thanks Daniel.
Please do not use the mfd_* API outside of drivers/mfd.
If you require MFD functionality, write an MFD driver.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-01-26 14:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 16:17 [PATCH v11 0/6] Add RZ/G2L MTU3a Core, Counter and pwm driver Biju Das
2023-01-13 16:17 ` [PATCH v11 1/6] dt-bindings: timer: Document RZ/G2L MTU3a bindings Biju Das
2023-01-13 16:17 ` [PATCH v11 2/6] clocksource/drivers: Add Renesas RZ/G2L MTU3a core driver Biju Das
2023-01-26 10:53 ` Daniel Lezcano
2023-01-26 11:14 ` Biju Das
2023-01-26 14:51 ` Lee Jones
2023-01-26 15:11 ` Biju Das
2023-01-26 16:33 ` Lee Jones
2023-01-26 16:56 ` Biju Das
2023-01-26 20:35 ` Biju Das
2023-02-02 16:22 ` Biju Das
2023-01-26 14:41 ` Lee Jones [this message]
2023-01-13 16:17 ` [PATCH v11 3/6] Documentation: ABI: sysfs-bus-counter: add cascade_counts_enable and external_input_phase_clock_select Biju Das
2023-01-13 16:17 ` [PATCH v11 4/6] counter: Add Renesas RZ/G2L MTU3a counter driver Biju Das
2023-01-13 16:17 ` [PATCH v11 5/6] MAINTAINERS: Add entries for " Biju Das
2023-01-13 16:17 ` [PATCH v11 6/6] pwm: Add Renesas RZ/G2L MTU3a PWM driver Biju Das
2023-01-25 19:48 ` [PATCH v11 0/6] Add RZ/G2L MTU3a Core, Counter and pwm driver Biju Das
2023-01-26 10:44 ` Daniel Lezcano
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=Y9KRFnc207xAeVvJ@google.com \
--to=lee@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=chris.paterson2@renesas.com \
--cc=daniel.lezcano@linaro.org \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=tglx@linutronix.de \
/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