From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Dixit Parmar <dixitparmar19@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] iio: magnetometer: add support for Infineon TLV493D 3D Magentic sensor
Date: Thu, 31 Jul 2025 14:04:09 +0100 [thread overview]
Message-ID: <20250731140409.00000029@huawei.com> (raw)
In-Reply-To: <aImVLWJP08_g23xu@dixit>
Please crop to the remaining discussion points.
> > > > > +
> > > > > +#define TLV493D_DATA_X_GET(b) \
> > > > > + sign_extend32(FIELD_GET(TLV493D_VAL_MAG_X_AXIS_MSB, b[TLV493D_RD_REG_BX]) << 4 | \
> > > > > + (FIELD_GET(TLV493D_VAL_MAG_X_AXIS_LSB, b[TLV493D_RD_REG_BX2]) >> 4), 11)
> > > >
> > > > These are odd enough I'd make them c functions rather than macros. Burn a few lines
> > > > for better readability.
> > > >
> > > I saw this kind of data retrival and formation from registers as macros so I sticked to
> > > it. Having all these as function will also require a seperate function
> > > for each channel coz the masks and the layout of the bits changes over
> > > the register. Do you still recommend it as c functions?
> >
> > Is it more than 4 short functions? I'd burn the few lines that costs.
> >
> > s32 tlv493d_data_y_get(u8 *buff)
> > {
> > u16 val = FIELD_GET(TLV493D_VAL_MAG_Y_AXIS_MSB, b[TLV493D_RD_REG_BY]) << 4 |
> > FIELD_GET(TLV493D_VAL_MAG_Y_AXIS_LSB, b[TLV493D_RD_REG_BX2]);
> >
> > return sign_extend32(val, 11);
> > }
> Okay.
> Will a single function with channel as arguments will be better?
IIRC I gave that a go as my first try before falling back to this.
You either need a look up table, or you need to pass
a lot of parameters. In the end it felt simpler to just have 4 small functions.
If you can come up with a clean and readable way of doing so, go for it!
Jonathan
next prev parent reply other threads:[~2025-07-31 13:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-26 9:37 [PATCH 0/2] iio: magnetometer: add support for Infineon TLV493D 3D Magnetic Sensor Dixit Parmar
2025-07-26 9:37 ` [PATCH 1/2] iio: magnetometer: add support for Infineon TLV493D 3D Magentic sensor Dixit Parmar
2025-07-26 20:44 ` David Lechner
2025-07-27 12:38 ` Jonathan Cameron
2025-07-29 3:27 ` Dixit Parmar
2025-07-29 3:26 ` Dixit Parmar
2025-07-29 7:49 ` Andy Shevchenko
2025-07-29 18:47 ` Jonathan Cameron
2025-07-29 18:51 ` David Lechner
2025-07-26 22:03 ` Christophe JAILLET
2025-07-29 3:28 ` Dixit Parmar
2025-07-27 13:05 ` Jonathan Cameron
2025-07-29 3:49 ` Dixit Parmar
2025-07-29 19:05 ` Jonathan Cameron
2025-07-30 3:44 ` Dixit Parmar
2025-07-31 13:04 ` Jonathan Cameron [this message]
2025-07-26 9:37 ` [PATCH 2/2] dt-bindings: iio: magnetometer: document Infineon TLV493D 3D Magnetic sensor Dixit Parmar
2025-07-26 20:43 ` David Lechner
2025-07-29 3:03 ` Dixit Parmar
2025-07-27 2:09 ` kernel test robot
2025-07-27 9:23 ` Krzysztof Kozlowski
2025-07-29 3:05 ` Dixit Parmar
2025-07-27 20:27 ` Rob Herring (Arm)
2025-07-29 3:09 ` Dixit Parmar
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=20250731140409.00000029@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dixitparmar19@gmail.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).