From: jim.cromie@gmail.com
To: Patryk <pbiel7@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Handling I2C eeprom devices
Date: Fri, 17 May 2024 14:31:58 -0600 [thread overview]
Message-ID: <CAJfuBxy1kxc-drAr6RrKUdt7gcc2T4PNcXfhzFX6hnjfvXW90w@mail.gmail.com> (raw)
In-Reply-To: <CA+DkFDbQccsKn0Uud1Xkpqpwh2G8n07g_Lnq-gMfw3OEg4G4mw@mail.gmail.com>
On Fri, May 17, 2024 at 7:35 AM Patryk <pbiel7@gmail.com> wrote:
>
> Hi,
> I've got a question regarding how to handle I2C eeprom devices. I see
> that in the kernel/drivers/misc/eeprom there are not that many drivers
> available. Does it mean that they support various chips that do not
> necessarily come from one vendor?
> Looking at example at24.c, in the compatible properties I see that all
> of them refers to atmel, however when I compared the following
> devices: AT24C04C and BRCB008GWZ, at the first glance they look kinda
> similar:
> - they are organized internally in the same way - 1024 x 8 (8K)
> - read/write commands looks the same
>
> I'm not asking you to tell me whether or not it's possible this driver
> at24 with the device I need (BRCB008GWZ), rather I would like to get a
> suggestion on how to approach this and what factors I should take into
> account to make the right decision.
>
> Best regards
> Patryk
>
$ git ls-files | grep eprom | wc -l
89
[jimc@frodo linux.git]$ git ls-files | grep eprom\.h | wc -l
29
[jimc@frodo linux.git]$ git ls-files | grep eprom | grep include
arch/parisc/include/asm/eisa_eeprom.h
arch/sparc/include/asm/eeprom.h
drivers/staging/rtl8723bs/include/rtw_eeprom.h
include/linux/eeprom_93cx6.h
include/linux/eeprom_93xx46.h
include/linux/spi/eeprom.h
include/media/tveeprom.h
Id look at those headers for similarity,
then the 2 c files in misc for similarity.
also the files under devicetree - thats ALL interface defn
you didnt say if those parts are I2C or SPI or what.
do you have the hardware ?
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2024-05-17 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 13:33 Handling I2C eeprom devices Patryk
2024-05-17 16:23 ` Rémi ESSAISSI
2024-05-17 20:31 ` jim.cromie [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=CAJfuBxy1kxc-drAr6RrKUdt7gcc2T4PNcXfhzFX6hnjfvXW90w@mail.gmail.com \
--to=jim.cromie@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=pbiel7@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).