From: Han Xu <han.xu@nxp.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Haibo Chen <haibo.chen@nxp.com>, Sean Nyekjaer <sean@geanix.com>,
Clark Wang <xiaoning.wang@nxp.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH 1/2] iio: accel: add the new entry in driver for FXLS8967AF
Date: Mon, 12 Dec 2022 16:23:25 -0600 [thread overview]
Message-ID: <20221212222325.jmsg4m4swsqkesus@umbrella> (raw)
In-Reply-To: <20221211130920.47f1c684@jic23-huawei>
On 22/12/11 01:09PM, Jonathan Cameron wrote:
> On Wed, 7 Dec 2022 10:20:44 -0600
> Han Xu <han.xu@nxp.com> wrote:
>
> > Add this new device entry in the driver id table.
> >
> > Signed-off-by: Han Xu <han.xu@nxp.com>
> Hi Han,
>
> I went to apply this and discovered the FXLs8974CF_DEVICE_ID etc
> isn't yet present in the upstream driver. Have a I missed a patch
> set somewhere?
>
> One comment inline.
>
There is another local patch not upstreamed, just sent them out as a patch set.
>
> > ---
> > drivers/iio/accel/fxls8962af-core.c | 7 +++++++
> > drivers/iio/accel/fxls8962af-i2c.c | 2 ++
> > drivers/iio/accel/fxls8962af.h | 1 +
> > 3 files changed, 10 insertions(+)
> >
> > diff --git a/drivers/iio/accel/fxls8962af-core.c b/drivers/iio/accel/fxls8962af-core.c
> > index 17a6f4f4e06c..ddeb1b153499 100644
> > --- a/drivers/iio/accel/fxls8962af-core.c
> > +++ b/drivers/iio/accel/fxls8962af-core.c
> > @@ -127,6 +127,7 @@
> > #define FXLS8962AF_DEVICE_ID 0x62
> > #define FXLS8964AF_DEVICE_ID 0x84
> > #define FXLS8974CF_DEVICE_ID 0x86
> > +#define FXLS8967AF_DEVICE_ID 0x87
> Fine with these being in numeric value order...
> >
> > /* Raw temp channel offset */
> > #define FXLS8962AF_TEMP_CENTER_VAL 25
> > @@ -772,6 +773,12 @@ static const struct fxls8962af_chip_info fxls_chip_info_table[] = {
> > .channels = fxls8962af_channels,
> > .num_channels = ARRAY_SIZE(fxls8962af_channels),
> > },
> > + [fxls8967af] = {
>
> I'd rather everything else was in 'alphabetical order as anyone looking down
> the lists will expect that ordering rather than one based on IDs that they
> probably won't have reason to know.
fixed in v2.
>
> > + .chip_id = FXLS8967AF_DEVICE_ID,
> > + .name = "fxls8967af",
> > + .channels = fxls8962af_channels,
> > + .num_channels = ARRAY_SIZE(fxls8962af_channels),
> > + },
> > };
> >
> > static const struct iio_info fxls8962af_info = {
> > diff --git a/drivers/iio/accel/fxls8962af-i2c.c b/drivers/iio/accel/fxls8962af-i2c.c
> > index 4a755a39d702..fd21f524e04f 100644
> > --- a/drivers/iio/accel/fxls8962af-i2c.c
> > +++ b/drivers/iio/accel/fxls8962af-i2c.c
> > @@ -31,6 +31,7 @@ static const struct i2c_device_id fxls8962af_id[] = {
> > { "fxls8962af", fxls8962af },
> > { "fxls8964af", fxls8964af },
> > { "fxls8974cf", fxls8974cf },
> > + { "fxls8967af", fxls8967af },
> > {}
> > };
> > MODULE_DEVICE_TABLE(i2c, fxls8962af_id);
> > @@ -39,6 +40,7 @@ static const struct of_device_id fxls8962af_of_match[] = {
> > { .compatible = "nxp,fxls8962af" },
> > { .compatible = "nxp,fxls8964af" },
> > { .compatible = "nxp,fxls8974cf" },
> > + { .compatible = "nxp,fxls8967af" },
> > {}
> > };
> > MODULE_DEVICE_TABLE(of, fxls8962af_of_match);
> > diff --git a/drivers/iio/accel/fxls8962af.h b/drivers/iio/accel/fxls8962af.h
> > index 45c7e57412e0..7de924d15694 100644
> > --- a/drivers/iio/accel/fxls8962af.h
> > +++ b/drivers/iio/accel/fxls8962af.h
> > @@ -12,6 +12,7 @@ enum {
> > fxls8962af,
> > fxls8964af,
> > fxls8974cf,
> > + fxls8967af,
> > };
> >
> > int fxls8962af_core_probe(struct device *dev, struct regmap *regmap, int irq);
>
prev parent reply other threads:[~2022-12-12 22:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 16:20 [PATCH 1/2] iio: accel: add the new entry in driver for FXLS8967AF Han Xu
2022-12-07 16:20 ` [PATCH 2/2] dt-bindings: iio: accel: fxls8962af: add new compatible string Han Xu
2022-12-07 16:24 ` Krzysztof Kozlowski
2022-12-08 7:42 ` sean
2022-12-08 7:41 ` [PATCH 1/2] iio: accel: add the new entry in driver for FXLS8967AF sean
2022-12-11 13:09 ` Jonathan Cameron
2022-12-12 22:23 ` Han Xu [this message]
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=20221212222325.jmsg4m4swsqkesus@umbrella \
--to=han.xu@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=haibo.chen@nxp.com \
--cc=imx@lists.linux.dev \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=sean@geanix.com \
--cc=xiaoning.wang@nxp.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