From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Shen Jianping (ME-SE/EAD2)" <Jianping.Shen@de.bosch.com>,
"jic23@kernel.org" <jic23@kernel.org>,
"lars@metafoo.de" <lars@metafoo.de>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"dima.fedrau@gmail.com" <dima.fedrau@gmail.com>,
"marcelo.schmitt1@gmail.com" <marcelo.schmitt1@gmail.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Lorenz Christian (ME-SE/EAD2)" <Christian.Lorenz3@de.bosch.com>,
"Frauendorf Ulrike (ME/PJ-SW3)" <Ulrike.Frauendorf@de.bosch.com>,
"Dolde Kai (ME-SE/PAE-A3)" <Kai.Dolde@de.bosch.com>
Subject: Re: [PATCH v2 2/2] iio: imu: smi240: imu driver
Date: Tue, 13 Aug 2024 11:46:32 +0200 [thread overview]
Message-ID: <bb33aeb0-7134-45ec-8536-47c524ec9e4b@kernel.org> (raw)
In-Reply-To: <AM8PR10MB47217665274B9848EB21FA65CD862@AM8PR10MB4721.EURPRD10.PROD.OUTLOOK.COM>
On 13/08/2024 11:41, Shen Jianping (ME-SE/EAD2) wrote:
> Hi
>
> On 09/08/2024 13:16, Jianping.Shen@de.bosch.com wrote:
>> From: "Shen Jianping (ME-SE/EAD2)" <Jianping.Shen@de.bosch.com>
>>
>> iio: imu: smi240: driver improvements
>
> ?????
> Did not get your point, what is wrong here? how it shall be?
See submitting patches. This does not match your commit at all. I do not
see any driver improvements done here. If so, please list all your
improvements against existing kernel driver.
>
>> Signed-off-by: Shen Jianping (ME-SE/EAD2) <Jianping.Shen@de.bosch.com>
>> ---
>>
>
>
> ...
>
>> + ret = regmap_read(data->regmap, SMI240_CHIP_ID_REG, &response);
>> + if (ret)
>> + return dev_err_probe(dev, ret, "Read chip id failed\n");
>> +
>> + if (response != SMI240_CHIP_ID)
>> + dev_info(dev, "Unknown chip id: 0x%04x\n", response);
>> +
>> + ret = smi240_init(data);
>> + if (ret)
>> + return dev_err_probe(dev, ret,
>> + "Device initialization failed\n");
>> +
>> + indio_dev->channels = smi240_channels;
>> + indio_dev->num_channels = ARRAY_SIZE(smi240_channels);
>> + indio_dev->name = "smi240";
>> + indio_dev->modes = INDIO_DIRECT_MODE;
>> + indio_dev->info = &smi240_info;
>> +
>> + ret = devm_iio_triggered_buffer_setup(dev, indio_dev,
>> + iio_pollfunc_store_time,
>> + smi240_trigger_handler, NULL);
>> + if (ret)
>> + return dev_err_probe(dev, ret,
>> + "Setup triggered buffer failed\n");
>> +
>> + ret = devm_iio_device_register(dev, indio_dev);
>> + if (ret)
>> + return dev_err_probe(dev, ret, "Register IIO device failed\n");
>> +
>> + return 0;
>> +}
>> +EXPORT_SYMBOL_GPL(smi240_core_probe);
>> +
>> +MODULE_AUTHOR("Markus Lochmann <markus.lochmann@de.bosch.com>");
>> +MODULE_AUTHOR("Stefan Gutmann <stefan.gutmann@de.bosch.com>");
>> +MODULE_DESCRIPTION("Bosch SMI240 driver"); MODULE_LICENSE("Dual
>> +BSD/GPL");
>
> Hm? How many modules do you have here? What are their names?
>
> We have one module, named "Bosch SMI240 driver". Any problem here?
Yes, you put MODULE_* to how many files? Two? Three? Why is it needed
everywhere?
>
>
>
>> +
>> +static const struct spi_device_id smi240_spi_id[] = { { "smi240", 0
>> +}, {} };
>
> Don't wrap it.
>
> We don't , git send-mail did it automatically for us.
>
>
>> +MODULE_DEVICE_TABLE(spi, smi240_spi_id);
>> +
>> +static const struct of_device_id smi240_of_match[] = {
>> + { .compatible = "bosch,smi240" },
>> + {},
>> +};
>> +MODULE_DEVICE_TABLE(of, smi240_of_match);
>> +
>> +static struct spi_driver smi240_spi_driver = {
>> + .probe = smi240_spi_probe,
>> + .id_table = smi240_spi_id,
>> + .driver = {
>> + .of_match_table = of_match_ptr(smi240_of_match),
>
> Why did it appear? You introduce now warnings.
>
> Did not get your point, why we introduce now warnings here ?
Fix your quoting. It's impossible to figure out what is here my quote
and what is yours.
Why? Test your code properly... Drop the of_match_ptr.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-13 9:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 11:16 [PATCH v2 0/2] iio: imu: smi240: cover-letter Jianping.Shen
2024-08-09 11:16 ` [PATCH v2 1/2] dt-bindings: iio: imu: smi240: devicetree binding Jianping.Shen
2024-08-09 14:19 ` Conor Dooley
2024-08-09 11:16 ` [PATCH v2 2/2] iio: imu: smi240: imu driver Jianping.Shen
2024-08-09 12:07 ` Christophe JAILLET
2024-08-09 12:18 ` Shen Jianping (ME-SE/EAD2)
2024-08-10 12:45 ` Krzysztof Kozlowski
2024-08-12 10:13 ` Shen Jianping (ME-SE/EAD2)
2024-08-10 12:44 ` Krzysztof Kozlowski
2024-08-13 9:41 ` Shen Jianping (ME-SE/EAD2)
2024-08-13 9:46 ` Krzysztof Kozlowski [this message]
2024-08-13 13:54 ` Shen Jianping (ME-SE/EAD2)
2024-08-13 14:37 ` Krzysztof Kozlowski
2024-08-13 14:51 ` Shen Jianping (ME-SE/EAD2)
2024-08-13 15:53 ` Krzysztof Kozlowski
2024-08-13 15:59 ` Krzysztof Kozlowski
2024-08-14 11:22 ` Shen Jianping (ME-SE/EAD2)
2024-08-13 15:57 ` Krzysztof Kozlowski
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=bb33aeb0-7134-45ec-8536-47c524ec9e4b@kernel.org \
--to=krzk@kernel.org \
--cc=Christian.Lorenz3@de.bosch.com \
--cc=Jianping.Shen@de.bosch.com \
--cc=Kai.Dolde@de.bosch.com \
--cc=Ulrike.Frauendorf@de.bosch.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dima.fedrau@gmail.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.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