From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-pwm@vger.kernel.org, kernel@pengutronix.de
Subject: [PATCH 1/3] pwm: Drop unused member "pwm" from struct pwm_device
Date: Tue, 14 Nov 2023 12:20:11 +0100 [thread overview]
Message-ID: <20231114112009.340168-2-u.kleine-koenig@pengutronix.de> (raw)
In-Reply-To: <20231114112009.340168-1-u.kleine-koenig@pengutronix.de>
This member is only assigned to and never read. So drop it.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
---
drivers/pwm/core.c | 1 -
include/linux/pwm.h | 1 -
2 files changed, 2 deletions(-)
diff --git a/drivers/pwm/core.c b/drivers/pwm/core.c
index 29078486534d..24bb796d15f6 100644
--- a/drivers/pwm/core.c
+++ b/drivers/pwm/core.c
@@ -265,7 +265,6 @@ int __pwmchip_add(struct pwm_chip *chip, struct module *owner)
pwm = &chip->pwms[i];
pwm->chip = chip;
- pwm->pwm = chip->base + i;
pwm->hwpwm = i;
}
diff --git a/include/linux/pwm.h b/include/linux/pwm.h
index cda3597b84f2..8cadf9ee8d26 100644
--- a/include/linux/pwm.h
+++ b/include/linux/pwm.h
@@ -79,7 +79,6 @@ struct pwm_device {
const char *label;
unsigned long flags;
unsigned int hwpwm;
- unsigned int pwm;
struct pwm_chip *chip;
struct pwm_args args;
--
2.42.0
next prev parent reply other threads:[~2023-11-14 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 11:20 [PATCH 0/3] pwm: Reorganize PWM identification Uwe Kleine-König
2023-11-14 11:20 ` Uwe Kleine-König [this message]
2023-11-14 11:20 ` [PATCH 2/3] pwm: Replace PWM chip unique base by unique ID Uwe Kleine-König
2023-11-14 11:20 ` [PATCH 3/3] pwm: Mention PWM chip ID in /sys/kernel/debug/pwm Uwe Kleine-König
2023-11-28 16:59 ` [PATCH 0/3] pwm: Reorganize PWM identification Thierry Reding
2023-12-06 17:51 ` Uwe Kleine-König
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=20231114112009.340168-2-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).