From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Akhil R <akhilrajeev@nvidia.com>
Cc: frank.li@nxp.com, acpica-devel@lists.linux.dev,
conor+dt@kernel.org, devicetree@vger.kernel.org,
ebiggers@kernel.org, krzk+dt@kernel.org, lenb@kernel.org,
linux-acpi@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
linux@roeck-us.net, miquel.raynal@bootlin.com,
p.zabel@pengutronix.de, rafael@kernel.org,
robert.moore@intel.com, robh@kernel.org,
sakari.ailus@linux.intel.com, wsa+renesas@sang-engineering.com
Subject: Re: [PATCH v2 09/13] i3c: dw-i3c-master: Add a quirk to skip clock and reset
Date: Mon, 13 Apr 2026 10:45:02 +0200 [thread overview]
Message-ID: <2026041308450274636352@mail.local> (raw)
In-Reply-To: <20260410060712.30377-1-akhilrajeev@nvidia.com>
On 10/04/2026 11:37:11+0530, Akhil R wrote:
> On Thu, 9 Apr 2026 22:45:09 -0400, Frank Li wrote:
> > On Thu, Apr 09, 2026 at 04:27:39PM +0530, Akhil R wrote:
> >> Some ACPI-enumerated devices like Tegra410 do not have clock and reset
> >> resources exposed via the clk/reset frameworks. Add a match data for
> >
> > why not export fix clock at ACPI?
> >
> >> such devices to skip acquiring clock and reset controls during probe.
> >>
> >> Move match data parsing before clock/reset acquisition so the quirk is
> >> available early enough. When the quirk is set, fall back to reading
> >> the clock rate from the "clock-frequency" device property instead.
> >
> > "clock-frequency" is legacy proptery.
>
> The document ACPI on ARMv8 Servers [1] suggests not to use clock or reset
> framework at all. I also could not find any proper way to export the clock
> to the kernel from the ACPI table. The same document suggests to use only
> _DSD properties, if to pass any data to the kernel.
>
> I can rename the property to 'default-clock-rate' if that sounds good.
> Please let me know your suggestion.
>
"clock-frequency" is fine for ACPI
> [1]: https://www.kernel.org/doc/html/v6.1/arm64/arm-acpi.html#programmable-power-control-resources
>
> Best Regards,
> Akhil
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Akhil R <akhilrajeev@nvidia.com>
Cc: frank.li@nxp.com, acpica-devel@lists.linux.dev,
conor+dt@kernel.org, devicetree@vger.kernel.org,
ebiggers@kernel.org, krzk+dt@kernel.org, lenb@kernel.org,
linux-acpi@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
linux@roeck-us.net, miquel.raynal@bootlin.com,
p.zabel@pengutronix.de, rafael@kernel.org,
robert.moore@intel.com, robh@kernel.org,
sakari.ailus@linux.intel.com, wsa+renesas@sang-engineering.com
Subject: Re: [PATCH v2 09/13] i3c: dw-i3c-master: Add a quirk to skip clock and reset
Date: Mon, 13 Apr 2026 10:45:02 +0200 [thread overview]
Message-ID: <2026041308450274636352@mail.local> (raw)
In-Reply-To: <20260410060712.30377-1-akhilrajeev@nvidia.com>
On 10/04/2026 11:37:11+0530, Akhil R wrote:
> On Thu, 9 Apr 2026 22:45:09 -0400, Frank Li wrote:
> > On Thu, Apr 09, 2026 at 04:27:39PM +0530, Akhil R wrote:
> >> Some ACPI-enumerated devices like Tegra410 do not have clock and reset
> >> resources exposed via the clk/reset frameworks. Add a match data for
> >
> > why not export fix clock at ACPI?
> >
> >> such devices to skip acquiring clock and reset controls during probe.
> >>
> >> Move match data parsing before clock/reset acquisition so the quirk is
> >> available early enough. When the quirk is set, fall back to reading
> >> the clock rate from the "clock-frequency" device property instead.
> >
> > "clock-frequency" is legacy proptery.
>
> The document ACPI on ARMv8 Servers [1] suggests not to use clock or reset
> framework at all. I also could not find any proper way to export the clock
> to the kernel from the ACPI table. The same document suggests to use only
> _DSD properties, if to pass any data to the kernel.
>
> I can rename the property to 'default-clock-rate' if that sounds good.
> Please let me know your suggestion.
>
"clock-frequency" is fine for ACPI
> [1]: https://www.kernel.org/doc/html/v6.1/arm64/arm-acpi.html#programmable-power-control-resources
>
> Best Regards,
> Akhil
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2026-04-13 8:45 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 10:57 [PATCH v2 00/13] Support ACPI and SETAASA device discovery Akhil R
2026-04-09 10:57 ` Akhil R
2026-04-09 10:57 ` [PATCH v2 01/13] dt-bindings: i3c: Add mipi-i3c-static-method to support SETAASA Akhil R
2026-04-09 10:57 ` Akhil R
2026-04-09 11:14 ` sashiko-bot
2026-04-10 2:00 ` Frank Li
2026-04-10 2:00 ` Frank Li
2026-04-10 4:30 ` Akhil R
2026-04-10 4:30 ` Akhil R
2026-04-16 11:59 ` Rob Herring
2026-04-16 11:59 ` Rob Herring
2026-04-09 10:57 ` [PATCH v2 02/13] ACPICA: Read LVR from the I2C resource descriptor Akhil R
2026-04-09 10:57 ` Akhil R
2026-04-09 11:07 ` Rafael J. Wysocki
2026-04-09 11:07 ` Rafael J. Wysocki
2026-04-09 11:20 ` sashiko-bot
2026-04-10 2:04 ` Frank Li
2026-04-10 2:04 ` Frank Li
2026-04-10 4:45 ` Akhil R
2026-04-10 4:45 ` Akhil R
2026-04-10 10:59 ` Rafael J. Wysocki
2026-04-10 10:59 ` Rafael J. Wysocki
2026-04-11 5:41 ` Akhil R
2026-04-11 5:41 ` Akhil R
2026-04-10 10:57 ` Rafael J. Wysocki
2026-04-10 10:57 ` Rafael J. Wysocki
2026-04-09 10:57 ` [PATCH v2 03/13] i3c: master: Use unified device property interface Akhil R
2026-04-09 10:57 ` Akhil R
2026-04-09 11:53 ` sashiko-bot
2026-04-09 10:57 ` [PATCH v2 04/13] i3c: master: Support ACPI enumeration of child devices Akhil R
2026-04-09 10:57 ` Akhil R
2026-04-09 11:43 ` sashiko-bot
2026-04-10 2:17 ` Frank Li
2026-04-10 2:17 ` Frank Li
2026-04-10 5:31 ` Akhil R
2026-04-10 5:31 ` Akhil R
2026-04-12 20:18 ` Alexandre Belloni
2026-04-12 20:18 ` Alexandre Belloni
2026-04-09 10:57 ` [PATCH v2 05/13] i3c: master: Add support for devices using SETAASA Akhil R
2026-04-09 10:57 ` Akhil R
2026-04-09 11:45 ` sashiko-bot
2026-04-10 2:25 ` Frank Li
2026-04-10 2:25 ` Frank Li
2026-04-09 10:57 ` [PATCH v2 06/13] i3c: master: Add support for devices without PID Akhil R
2026-04-09 10:57 ` Akhil R
2026-04-09 12:08 ` sashiko-bot
2026-04-10 2:37 ` Frank Li
2026-04-10 2:37 ` Frank Li
2026-04-09 10:57 ` [PATCH v2 07/13] i3c: master: match I3C device through DT and ACPI Akhil R
2026-04-09 10:57 ` Akhil R
2026-04-10 2:40 ` Frank Li
2026-04-10 2:40 ` Frank Li
2026-04-09 10:57 ` [PATCH v2 08/13] i3c: dw-i3c-master: Add SETAASA as supported CCC Akhil R
2026-04-09 10:57 ` Akhil R
2026-04-10 2:41 ` Frank Li
2026-04-10 2:41 ` Frank Li
2026-04-09 10:57 ` [PATCH v2 09/13] i3c: dw-i3c-master: Add a quirk to skip clock and reset Akhil R
2026-04-09 10:57 ` Akhil R
2026-04-09 11:51 ` sashiko-bot
2026-04-10 2:45 ` Frank Li
2026-04-10 2:45 ` Frank Li
2026-04-10 6:07 ` Akhil R
2026-04-10 6:07 ` Akhil R
2026-04-13 8:45 ` Alexandre Belloni [this message]
2026-04-13 8:45 ` Alexandre Belloni
2026-04-09 10:57 ` [PATCH v2 10/13] i3c: dw-i3c-master: Add ACPI ID for Tegra410 Akhil R
2026-04-09 10:57 ` Akhil R
2026-04-10 2:47 ` Frank Li
2026-04-10 2:47 ` Frank Li
2026-04-09 10:57 ` [PATCH v2 11/13] hwmon: spd5118: Remove 16-bit addressing Akhil R
2026-04-09 10:57 ` Akhil R
2026-04-09 14:11 ` Guenter Roeck
2026-04-09 14:11 ` Guenter Roeck
2026-04-09 10:57 ` [PATCH v2 12/13] hwmon: spd5118: Add I3C support Akhil R
2026-04-09 10:57 ` Akhil R
2026-04-09 12:36 ` sashiko-bot
2026-04-09 14:15 ` Guenter Roeck
2026-04-09 14:19 ` Guenter Roeck
2026-04-09 14:19 ` Guenter Roeck
2026-04-12 20:16 ` Alexandre Belloni
2026-04-12 20:16 ` Alexandre Belloni
2026-04-12 21:26 ` Guenter Roeck
2026-04-12 21:26 ` Guenter Roeck
2026-04-09 10:57 ` [PATCH v2 13/13] arm64: defconfig: Enable I3C and SPD5118 hwmon Akhil R
2026-04-09 10:57 ` Akhil R
2026-04-10 6:39 ` Krzysztof Kozlowski
2026-04-10 6:39 ` Krzysztof Kozlowski
2026-04-10 6:57 ` Guenter Roeck
2026-04-10 6:57 ` Guenter Roeck
2026-04-10 7:18 ` Krzysztof Kozlowski
2026-04-10 7:18 ` Krzysztof Kozlowski
2026-04-10 8:37 ` Akhil R
2026-04-10 8:37 ` Akhil R
2026-04-10 9:57 ` Krzysztof Kozlowski
2026-04-10 9:57 ` Krzysztof Kozlowski
2026-04-11 5:34 ` Akhil R
2026-04-11 5:34 ` Akhil R
2026-04-11 7:20 ` Guenter Roeck
2026-04-11 7:20 ` Guenter Roeck
2026-04-12 13:32 ` Krzysztof Kozlowski
2026-04-12 13:32 ` Krzysztof Kozlowski
2026-04-12 13:33 ` Krzysztof Kozlowski
2026-04-12 13:33 ` Krzysztof Kozlowski
2026-04-13 6:57 ` Akhil R
2026-04-13 6:57 ` Akhil R
2026-04-13 7:12 ` Krzysztof Kozlowski
2026-04-13 7:12 ` Krzysztof Kozlowski
2026-04-13 10:46 ` Akhil R
2026-04-13 10:46 ` Akhil R
2026-04-12 13:21 ` Krzysztof Kozlowski
2026-04-12 13:21 ` Krzysztof Kozlowski
2026-04-10 7:04 ` Akhil R
2026-04-10 7:04 ` Akhil R
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=2026041308450274636352@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=acpica-devel@lists.linux.dev \
--cc=akhilrajeev@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ebiggers@kernel.org \
--cc=frank.li@nxp.com \
--cc=krzk+dt@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=miquel.raynal@bootlin.com \
--cc=p.zabel@pengutronix.de \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=wsa+renesas@sang-engineering.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 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.