From: Greg KH <gregkh@linuxfoundation.org>
To: Kumaravel.Thiagarajan@microchip.com
Cc: arnd@arndb.de, linux-gpio@vger.kernel.org, michael@walle.cc,
srinivas.kandagatla@linaro.org, linux-kernel@vger.kernel.org,
UNGLinuxDriver@microchip.com,
Tharunkumar.Pasumarthi@microchip.com
Subject: Re: [PATCH v5 char-misc-next] misc: microchip: pci1xxxx: Add OTP/EEPROM driver for the pci1xxxx switch
Date: Mon, 20 Feb 2023 10:45:11 +0100 [thread overview]
Message-ID: <Y/NBJ5xzUoNHEOm2@kroah.com> (raw)
In-Reply-To: <e1375c213b496b86df3f61d04003d94390c80240.camel@microchip.com>
On Mon, Feb 20, 2023 at 09:31:45AM +0000, Kumaravel.Thiagarajan@microchip.com wrote:
> > I do not recommend using a block interface for this at all. Why not
> > the
> > "normal" EEPROM interface that the kernel has today (i.e. a binary
> > sysfs
> > file)? That way you can mmap it and edit locations how ever you
> > want.
> Greg, I have one question about the sysfs interface. If OTP and EEPROM
> are enumerated as two sysfs files of 8KB each, will that start
> occupying the RAM permamently or is the swapping in and out of the RAM
> handled automatically by the kernel based on the user trying to access
> it.
It depends on exactly what you are doing here with the binary sysfs
file. Try it yourself and see how it works.
thanks,
greg k-h
prev parent reply other threads:[~2023-02-20 9:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 3:57 [PATCH v5 char-misc-next] misc: microchip: pci1xxxx: Add OTP/EEPROM driver for the pci1xxxx switch Tharun Kumar P
2023-02-12 7:09 ` Greg KH
2023-02-12 7:52 ` Tharunkumar.Pasumarthi
2023-02-13 12:00 ` Michael Walle
2023-02-14 6:25 ` Tharunkumar.Pasumarthi
2023-02-12 8:02 ` Christophe JAILLET
2023-02-14 6:37 ` Tharunkumar.Pasumarthi
2023-02-14 6:52 ` Tharunkumar.Pasumarthi
2023-02-14 8:28 ` Michael Walle
2023-02-15 4:37 ` Kumaravel.Thiagarajan
2023-02-15 8:20 ` Michael Walle
2023-02-15 8:58 ` Greg KH
2023-02-15 9:48 ` Kumaravel.Thiagarajan
2023-02-15 9:56 ` Kumaravel.Thiagarajan
2023-02-15 10:15 ` Michael Walle
2023-02-15 11:44 ` Greg KH
2023-02-16 11:39 ` Kumaravel.Thiagarajan
2023-02-16 11:49 ` Greg KH
2023-02-17 8:57 ` Kumaravel.Thiagarajan
2023-02-17 9:22 ` Greg KH
2023-02-20 9:31 ` Kumaravel.Thiagarajan
2023-02-20 9:45 ` Greg KH [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=Y/NBJ5xzUoNHEOm2@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Kumaravel.Thiagarajan@microchip.com \
--cc=Tharunkumar.Pasumarthi@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=arnd@arndb.de \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=srinivas.kandagatla@linaro.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