From: "Rémi ESSAISSI" <remi@remi.lu>
To: kernelnewbies@kernelnewbies.org
Subject: Re: Handling I2C eeprom devices
Date: Fri, 17 May 2024 18:23:17 +0200 [thread overview]
Message-ID: <3c32b4cc-7db7-4220-abef-e0bf3c366ff9@remi.lu> (raw)
In-Reply-To: <CA+DkFDbQccsKn0Uud1Xkpqpwh2G8n07g_Lnq-gMfw3OEg4G4mw@mail.gmail.com>
Le 17/05/2024 à 15:33, Patryk a écrit :
> 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
Those chips may look the "same", but they differ in the magic sequences
to interact with them.
I mean, they have to be exactly the same to work, up to the timing that
has to follow the specs by the milli or micro second for example.
(and sometimes even weird voltages to apply on this or that pin ... )
So your best friend is the Datasheet of your IC delivered by the
vendor/constructor of that chip, that will give you the magic sequences
to interact with it .
Your case should be easy as you already have more than a working
"skeleton" ... .
Regards
>
> 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
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2024-05-17 16:25 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 [this message]
2024-05-17 20:31 ` jim.cromie
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=3c32b4cc-7db7-4220-abef-e0bf3c366ff9@remi.lu \
--to=remi@remi.lu \
--cc=kernelnewbies@kernelnewbies.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 read-only IMAP folder(s) and NNTP newsgroup(s).