From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linux ACPI <linux-acpi@vger.kernel.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-rtc@vger.kernel.org, Linux PM <linux-pm@vger.kernel.org>
Subject: [PATCH v1 1/7] ACPI: TAD: Create one attribute group
Date: Wed, 04 Mar 2026 19:12:22 +0100 [thread overview]
Message-ID: <2412153.ElGaqSPkdT@rafael.j.wysocki> (raw)
In-Reply-To: <5092662.31r3eYUQgx@rafael.j.wysocki>
From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Instead of creating three attribute groups, one for each supported
subset of capabilities, create just one and use an .is_visible()
callback in it to decide which attributes to use.
No intentional functional impact.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
drivers/acpi/acpi_tad.c | 80 +++++++++++++++++++++---------------------------
1 file changed, 35 insertions(+), 45 deletions(-)
--- a/drivers/acpi/acpi_tad.c
+++ b/drivers/acpi/acpi_tad.c
@@ -249,14 +249,6 @@ static ssize_t time_show(struct device *
static DEVICE_ATTR_RW(time);
-static struct attribute *acpi_tad_time_attrs[] = {
- &dev_attr_time.attr,
- NULL,
-};
-static const struct attribute_group acpi_tad_time_attr_group = {
- .attrs = acpi_tad_time_attrs,
-};
-
static int acpi_tad_wake_set(struct device *dev, char *method, u32 timer_id,
u32 value)
{
@@ -486,17 +478,6 @@ static ssize_t ac_status_show(struct dev
static DEVICE_ATTR_RW(ac_status);
-static struct attribute *acpi_tad_attrs[] = {
- &dev_attr_caps.attr,
- &dev_attr_ac_alarm.attr,
- &dev_attr_ac_policy.attr,
- &dev_attr_ac_status.attr,
- NULL,
-};
-static const struct attribute_group acpi_tad_attr_group = {
- .attrs = acpi_tad_attrs,
-};
-
static ssize_t dc_alarm_store(struct device *dev, struct device_attribute *attr,
const char *buf, size_t count)
{
@@ -545,14 +526,44 @@ static ssize_t dc_status_show(struct dev
static DEVICE_ATTR_RW(dc_status);
-static struct attribute *acpi_tad_dc_attrs[] = {
+static struct attribute *acpi_tad_attrs[] = {
+ &dev_attr_caps.attr,
+ &dev_attr_ac_alarm.attr,
+ &dev_attr_ac_policy.attr,
+ &dev_attr_ac_status.attr,
&dev_attr_dc_alarm.attr,
&dev_attr_dc_policy.attr,
&dev_attr_dc_status.attr,
+ &dev_attr_time.attr,
NULL,
};
-static const struct attribute_group acpi_tad_dc_attr_group = {
- .attrs = acpi_tad_dc_attrs,
+
+static umode_t acpi_tad_attr_is_visible(struct kobject *kobj,
+ struct attribute *a, int n)
+{
+ struct acpi_tad_driver_data *dd = dev_get_drvdata(kobj_to_dev(kobj));
+
+ if (a == &dev_attr_caps.attr)
+ return a->mode;
+
+ if (a == &dev_attr_ac_alarm.attr || a == &dev_attr_ac_policy.attr ||
+ a == &dev_attr_ac_status.attr)
+ return a->mode;
+
+ if ((dd->capabilities & ACPI_TAD_DC_WAKE) &&
+ (a == &dev_attr_dc_alarm.attr || a == &dev_attr_dc_policy.attr ||
+ a == &dev_attr_dc_status.attr))
+ return a->mode;
+
+ if ((dd->capabilities & ACPI_TAD_RT) && a == &dev_attr_time.attr)
+ return a->mode;
+
+ return 0;
+}
+
+static const struct attribute_group acpi_tad_attr_group = {
+ .attrs = acpi_tad_attrs,
+ .is_visible = acpi_tad_attr_is_visible,
};
static int acpi_tad_disable_timer(struct device *dev, u32 timer_id)
@@ -567,12 +578,6 @@ static void acpi_tad_remove(struct platf
device_init_wakeup(dev, false);
- if (dd->capabilities & ACPI_TAD_RT)
- sysfs_remove_group(&dev->kobj, &acpi_tad_time_attr_group);
-
- if (dd->capabilities & ACPI_TAD_DC_WAKE)
- sysfs_remove_group(&dev->kobj, &acpi_tad_dc_attr_group);
-
sysfs_remove_group(&dev->kobj, &acpi_tad_attr_group);
scoped_guard(pm_runtime_noresume, dev) {
@@ -633,6 +638,7 @@ static int acpi_tad_probe(struct platfor
device_init_wakeup(dev, true);
dev_pm_set_driver_flags(dev, DPM_FLAG_SMART_SUSPEND |
DPM_FLAG_MAY_SKIP_RESUME);
+
/*
* The platform bus type layer tells the ACPI PM domain powers up the
* device, so set the runtime PM status of it to "active".
@@ -643,24 +649,8 @@ static int acpi_tad_probe(struct platfor
ret = sysfs_create_group(&dev->kobj, &acpi_tad_attr_group);
if (ret)
- goto fail;
-
- if (caps & ACPI_TAD_DC_WAKE) {
- ret = sysfs_create_group(&dev->kobj, &acpi_tad_dc_attr_group);
- if (ret)
- goto fail;
- }
-
- if (caps & ACPI_TAD_RT) {
- ret = sysfs_create_group(&dev->kobj, &acpi_tad_time_attr_group);
- if (ret)
- goto fail;
- }
-
- return 0;
+ acpi_tad_remove(pdev);
-fail:
- acpi_tad_remove(pdev);
return ret;
}
next prev parent reply other threads:[~2026-03-04 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 18:11 [PATCH v1 0/7] ACPI: TAD: Assorted improvements and RTC class device interface Rafael J. Wysocki
2026-03-04 18:12 ` Rafael J. Wysocki [this message]
2026-03-04 18:13 ` [PATCH v1 2/7] ACPI: TAD: Support RTC without wakeup Rafael J. Wysocki
2026-03-04 18:14 ` [PATCH v1 3/7] ACPI: TAD: Use __free() for cleanup in time_store() Rafael J. Wysocki
2026-03-04 18:14 ` [PATCH v1 4/7] ACPI: TAD: Rearrange RT data validation checking Rafael J. Wysocki
2026-03-04 18:15 ` [PATCH v1 5/7] ACPI: TAD: Clear unused RT data in acpi_tad_set_real_time() Rafael J. Wysocki
2026-03-04 18:16 ` [PATCH v1 6/7] ACPI: TAD: Add RTC class device interface Rafael J. Wysocki
2026-03-05 7:48 ` Alexandre Belloni
2026-03-04 18:16 ` [PATCH v1 7/7] ACPI: TAD: Update the driver description comment Rafael J. Wysocki
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=2412153.ElGaqSPkdT@rafael.j.wysocki \
--to=rafael@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rtc@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox