From: Wolfram Sang <wsa@the-dreams.de>
To: "Björn Ardö" <bjorn.ardo@axis.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
patrick@stwcx.xyz, kernel@axis.com
Subject: Re: [PATCHv2] i2c: slave-eeprom: Make it possible to pre-load eeprom data
Date: Fri, 24 Apr 2020 12:03:07 +0200 [thread overview]
Message-ID: <20200424100307.GB1959@kunai> (raw)
In-Reply-To: <20200424090443.26316-1-bjorn.ardo@axis.com>
[-- Attachment #1: Type: text/plain, Size: 2289 bytes --]
On Fri, Apr 24, 2020 at 11:04:43AM +0200, Björn Ardö wrote:
> If the slave eeprom has a "firmware-name" in devicetree, then
> pre-load the data in the eeprom with this file. Otherwise we
> init the eeprom with 0xFF.
>
> Signed-off-by: Björn Ardö <bjorn.ardo@axis.com>
I like it a lot, thanks! Maybe we could add a SoB from Patrick for his
0xff-suggestion (but keeping you as the patch author).
Is this okay for everyone?
> ---
> drivers/i2c/i2c-slave-eeprom.c | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/drivers/i2c/i2c-slave-eeprom.c b/drivers/i2c/i2c-slave-eeprom.c
> index cb415b10642f..c846c96c25c9 100644
> --- a/drivers/i2c/i2c-slave-eeprom.c
> +++ b/drivers/i2c/i2c-slave-eeprom.c
> @@ -18,6 +18,7 @@
> */
>
> #include <linux/bitfield.h>
> +#include <linux/firmware.h>
> #include <linux/i2c.h>
> #include <linux/init.h>
> #include <linux/module.h>
> @@ -120,6 +121,26 @@ static ssize_t i2c_slave_eeprom_bin_write(struct file *filp, struct kobject *kob
> return count;
> }
>
> +static int i2c_slave_init_eeprom_data(struct eeprom_data *eeprom, struct i2c_client *client,
> + unsigned int size)
> +{
> + const struct firmware *fw;
> + const char *eeprom_data;
> + int error = device_property_read_string(&client->dev, "firmware-name", &eeprom_data);
> +
> + if (!error) {
> + int ret = request_firmware_into_buf(&fw, eeprom_data, &client->dev,
> + eeprom->buffer, size);
> + if (ret)
> + return ret;
> + release_firmware(fw);
> + } else {
> + /* An empty eeprom typically has all bits set to 1 */
> + memset(eeprom->buffer, 0xFF, size);
> + }
> + return 0;
> +}
> +
> static int i2c_slave_eeprom_probe(struct i2c_client *client, const struct i2c_device_id *id)
> {
> struct eeprom_data *eeprom;
> @@ -138,6 +159,10 @@ static int i2c_slave_eeprom_probe(struct i2c_client *client, const struct i2c_de
> spin_lock_init(&eeprom->buffer_lock);
> i2c_set_clientdata(client, eeprom);
>
> + ret = i2c_slave_init_eeprom_data(eeprom, client, size);
> + if (ret)
> + return ret;
> +
> sysfs_bin_attr_init(&eeprom->bin);
> eeprom->bin.attr.name = "slave-eeprom";
> eeprom->bin.attr.mode = S_IRUSR | S_IWUSR;
> --
> 2.11.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-24 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 9:04 [PATCHv2] i2c: slave-eeprom: Make it possible to pre-load eeprom data Björn Ardö
2020-04-24 10:03 ` Wolfram Sang [this message]
2020-04-24 10:06 ` Bjorn Ardo
2020-04-24 15:32 ` Patrick Williams
2020-04-24 11:13 ` Wolfram Sang
2020-04-24 11:22 ` Bjorn Ardo
2020-04-24 11:27 ` Wolfram Sang
2020-04-24 11:31 ` Bjorn Ardo
-- strict thread matches above, loose matches on Subject: below --
2020-04-24 11:29 Björn Ardö
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=20200424100307.GB1959@kunai \
--to=wsa@the-dreams.de \
--cc=bjorn.ardo@axis.com \
--cc=kernel@axis.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@stwcx.xyz \
/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