From: Saalim Quadri <danascape@gmail.com>
To: jic23@kernel.org
Cc: lars@metafoo.de, Michael.Hennerich@analog.com,
gregkh@linuxfoundation.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
Saalim Quadri <danascape@gmail.com>
Subject: [PATCH] staging: iio: ad5933: Fix CamelCase naming
Date: Mon, 3 Mar 2025 18:22:46 +0530 [thread overview]
Message-ID: <20250303125246.342704-1-danascape@gmail.com> (raw)
Reported by checkpatch:
CHECK: Avoid CamelCase
Signed-off-by: Saalim Quadri <danascape@gmail.com>
---
drivers/staging/iio/impedance-analyzer/ad5933.c | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/staging/iio/impedance-analyzer/ad5933.c b/drivers/staging/iio/impedance-analyzer/ad5933.c
index d5544fc2fe98..a1a5eee4f736 100644
--- a/drivers/staging/iio/impedance-analyzer/ad5933.c
+++ b/drivers/staging/iio/impedance-analyzer/ad5933.c
@@ -43,10 +43,10 @@
#define AD5933_CTRL_POWER_DOWN (0xA << 4)
#define AD5933_CTRL_STANDBY (0xB << 4)
-#define AD5933_CTRL_RANGE_2000mVpp (0x0 << 1)
-#define AD5933_CTRL_RANGE_200mVpp (0x1 << 1)
-#define AD5933_CTRL_RANGE_400mVpp (0x2 << 1)
-#define AD5933_CTRL_RANGE_1000mVpp (0x3 << 1)
+#define AD5933_CTRL_RANGE_2000MVPP (0x0 << 1)
+#define AD5933_CTRL_RANGE_200MVPP (0x1 << 1)
+#define AD5933_CTRL_RANGE_400MVPP (0x2 << 1)
+#define AD5933_CTRL_RANGE_1000MVPP (0x3 << 1)
#define AD5933_CTRL_RANGE(x) ((x) << 1)
#define AD5933_CTRL_PGA_GAIN_1 (0x1 << 0)
@@ -68,8 +68,8 @@
#define AD5933_I2C_ADDR_POINTER 0xB0
/* Device Specs */
-#define AD5933_INT_OSC_FREQ_Hz 16776000
-#define AD5933_MAX_OUTPUT_FREQ_Hz 100000
+#define AD5933_INT_OSC_FREQ_HZ 16776000
+#define AD5933_MAX_OUTPUT_FREQ_HZ 100000
#define AD5933_MAX_RETRIES 100
#define AD5933_OUT_RANGE 1
@@ -302,7 +302,7 @@ static ssize_t ad5933_store_frequency(struct device *dev,
if (ret)
return ret;
- if (val > AD5933_MAX_OUTPUT_FREQ_Hz)
+ if (val > AD5933_MAX_OUTPUT_FREQ_HZ)
return -EINVAL;
ret = iio_device_claim_direct_mode(indio_dev);
@@ -695,7 +695,7 @@ static int ad5933_probe(struct i2c_client *client)
st->mclk_hz = ext_clk_hz;
st->ctrl_lb = AD5933_CTRL_EXT_SYSCLK;
} else {
- st->mclk_hz = AD5933_INT_OSC_FREQ_Hz;
+ st->mclk_hz = AD5933_INT_OSC_FREQ_HZ;
st->ctrl_lb = AD5933_CTRL_INT_SYSCLK;
}
--
2.34.1
next reply other threads:[~2025-03-03 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 12:52 Saalim Quadri [this message]
2025-03-03 12:56 ` [PATCH] staging: iio: ad5933: Fix CamelCase naming Greg KH
2025-03-03 18:07 ` Saalim Quadri
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=20250303125246.342704-1-danascape@gmail.com \
--to=danascape@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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.