From: Greg KH <gregkh@linuxfoundation.org>
To: Kumaravel.Thiagarajan@microchip.com
Cc: lee.jones@linaro.org, Pragash.Mangalapandian@microchip.com,
Sundararaman.H@microchip.com, axboe@kernel.dk,
linux-block@vger.kernel.org, miquel.raynal@bootlin.com,
richard@nod.at, vigneshr@ti.com, linux-mtd@lists.infradead.org,
LakshmiPraveen.Kopparthi@microchip.com,
Ronnie.Kunin@microchip.com
Subject: Re: Reg: New MFD Driver for my PCIe Device
Date: Fri, 19 Nov 2021 15:53:00 +0100 [thread overview]
Message-ID: <YZe6TPrf4Drh7HpI@kroah.com> (raw)
In-Reply-To: <CH0PR11MB5380439460BADE102D91C18AE99C9@CH0PR11MB5380.namprd11.prod.outlook.com>
On Fri, Nov 19, 2021 at 09:16:29AM +0000, Kumaravel.Thiagarajan@microchip.com wrote:
> Dear Greg KH,
>
> I went through the documentation of aux bus and felt that it would be the correct way to go as you said.
> I will migrate from MFD to aux bus.
>
> I have one more architectural question as below.
> I have written the driver such that it enumerates the OTP memory and EEPROM memory as two separate block devices or disks each of size 8KB and this enables me to use the linux dd command with "direct" option to dump the configuration binary onto OTP or EEPROM devices.
> Also, this enables me to use the application like hexedit to view the OTP or EEPROM devices in raw binary format.
> These devices are not based on mtd (memory technology device) architecture as we don't have any erase functionality here.
> Can you please let me know a suitable location in kernel source tree for my block or disk device driver?
So they are a read-only block device?
Why use a block device and not just the "normal" eeprom driver? Or a
char device node and mmap the memory?
Anyway, no idea where to put them, drivers/misc/ ?
thanks,
greg k-h
next prev parent reply other threads:[~2021-11-19 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CH0PR11MB5380F5BD18F15014BA8B8479E9919@CH0PR11MB5380.namprd11.prod.outlook.com>
2021-11-08 11:04 ` Reg: New MFD Driver for my PCIe Device Lee Jones
2021-11-08 11:14 ` Greg KH
2021-11-08 11:27 ` Lee Jones
2021-11-08 12:03 ` Greg KH
2021-11-16 11:34 ` Kumaravel.Thiagarajan
2021-11-16 14:20 ` Greg KH
2021-11-19 9:16 ` Kumaravel.Thiagarajan
2021-11-19 14:53 ` Greg KH [this message]
2021-11-23 18:33 ` Kumaravel.Thiagarajan
2021-11-30 17:42 ` Kumaravel.Thiagarajan
2021-12-01 7:11 ` Greg KH
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=YZe6TPrf4Drh7HpI@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Kumaravel.Thiagarajan@microchip.com \
--cc=LakshmiPraveen.Kopparthi@microchip.com \
--cc=Pragash.Mangalapandian@microchip.com \
--cc=Ronnie.Kunin@microchip.com \
--cc=Sundararaman.H@microchip.com \
--cc=axboe@kernel.dk \
--cc=lee.jones@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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