Re: [PATCH v2 0/5] scmi: Log client subsystem entity counts
Alex Tran <[email protected]> Wed, 1 Jul 2026 13:15:12 -0700
| Newsgroups | org.kernel.vger.arm-scmi,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-gpio,org.kernel.vger.linux-hwmon,org.kernel.vger.linux-iio,org.kernel.vger.linux-kernel,org.kernel.vger.linux-pm |
|---|---|
| Message-ID | <[email protected]> |
On 5/15/2026 1:29 AM, Sudeep Holla wrote: > On Thu, May 14, 2026 at 02:23:56PM -0700, Alex Tran wrote: >> On 5/14/2026 8:44 AM, Jonathan Cameron wrote: >> >>> On Wed, 13 May 2026 10:16:53 -0700 >>> Alex Tran <[email protected]> wrote: >>> >>>> SCMI client drivers do not consistently log the number of supported >>>> entities discovered from firmware. This information is useful during >>>> debugging because it shows which domains or resources were exposed by >>>> firmware during probe. >>>> >>>> Add logging of the number of supported entities to the SCMI cpufreq, >>>> pinctrl, reset, hwmon, and powercap client drivers after a successful >>>> probe. This aligns these drivers with the existing logging in the SCMI >>>> power and performance domain drivers. >>>> >>>> Signed-off-by: Alex Tran <[email protected]> >>> Hi Alex, >>> >>> Just curious but why +CC linux-iio and IIO folk? >>> >>> May be you had a false suggestion to add them from get maintainers. >>> If so be sure to check it's suggestions make sense! >>> >>> Not to worry - we can all hit the delete button ;) >>> >>> Jonathan >> Hi Jonathan, >> >> Originally, there was another patch in this series to add the same >> functionality to scmi_iio probe but it was dropped. Apparently running b4 >> prep --auto-to-cc does not prune stale entries from the cover letter. Will >> manually remove all entries and rerun the command in the future. >> > I guessed so, but why was it dropped ? I don't agree to adding them elsewhere > just curious about why it was dropped in this case. > We could not determine whether to log the sensor count provided by SCMI or the number of sensors that were registered in probe since the driver appears to only support 3-axis accel and gyro sensors, skipping the rest.