From: <VaibhaavRam.TL@microchip.com>
To: <gregkh@linuxfoundation.org>
Cc: <linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<UNGLinuxDriver@microchip.com>, <arnd@arndb.de>,
<Tharunkumar.Pasumarthi@microchip.com>
Subject: Re: [PATCH v8 char-misc-next 4/5] misc: microchip: pci1xxxx: Load auxiliary driver for OTP/EEPROM auxiliary device
Date: Thu, 30 Mar 2023 05:29:58 +0000 [thread overview]
Message-ID: <06f47b3f10ab08a6a93ffd7996b7f042845193e3.camel@microchip.com> (raw)
In-Reply-To: <ZCQMtUAWAeCDmXlK@kroah.com>
On Wed, 2023-03-29 at 12:02 +0200, Greg KH wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> On Tue, Mar 28, 2023 at 08:10:07PM +0530, Vaibhaav Ram T.L wrote:
> > From: Kumaravel Thiagarajan <kumaravel.thiagarajan@microchip.com>
> >
> > This patch contains driver to perform ioremap for the OTP/EEPROM
> > auxiliary device.
>
> What does this mean? What will it do? Why is this needed?
In PCI1XXXX, same PCIe function is used for gpio handling as well as
the OTP/EEPROM programming.
Hence, we are loading auxiliary bus driver for the PCIe function and
spawning two separate auxiliary devices for each purpose.
Auxiliary device for OTP/EEPROM includes OTP and EEPROM as separate bin
attributes in its device's attribute_group and maps them into sysfs.
But these bin attributes can be accessed only when the memory resource
of the auxiliary device is mapped into the virtual space of the kernel
which is done by this auxiliary device driver.
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2023-03-30 5:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230328144008.4113-1-vaibhaavram.tl@microchip.com>
[not found] ` <20230328144008.4113-2-vaibhaavram.tl@microchip.com>
2023-03-29 9:59 ` [PATCH v8 char-misc-next 1/5] misc: microchip: pci1xxxx: Fix error handling path in probe function Greg KH
2023-03-30 5:19 ` VaibhaavRam.TL
[not found] ` <20230328144008.4113-3-vaibhaavram.tl@microchip.com>
2023-03-29 10:01 ` [PATCH v8 char-misc-next 2/5] misc: microchip: pci1xxxx: Add OTP Functionality to read and write into OTP bin sysfs Greg KH
2023-03-30 5:27 ` VaibhaavRam.TL
[not found] ` <20230328144008.4113-4-vaibhaavram.tl@microchip.com>
2023-03-29 10:01 ` [PATCH v8 char-misc-next 3/5] misc: microchip: pci1xxxx: Add EEPROM Functionality to read and write into EEPROM " Greg KH
2023-03-30 5:28 ` VaibhaavRam.TL
2023-03-30 7:57 ` Greg KH
2023-03-30 9:51 ` Michael Walle
2023-03-30 17:21 ` Kumaravel.Thiagarajan
[not found] ` <20230328144008.4113-5-vaibhaavram.tl@microchip.com>
2023-03-29 10:02 ` [PATCH v8 char-misc-next 4/5] misc: microchip: pci1xxxx: Load auxiliary driver for OTP/EEPROM auxiliary device Greg KH
2023-03-30 5:29 ` VaibhaavRam.TL [this message]
[not found] ` <20230328144008.4113-6-vaibhaavram.tl@microchip.com>
2023-03-29 10:03 ` [PATCH v8 char-misc-next 5/5] misc: microchip: pci1xxxx: Add documentation for sysfs bin attributes Greg KH
2023-03-30 5:37 ` VaibhaavRam.TL
2023-03-29 10:03 ` [PATCH v8 char-misc-next 0/5] Fix error handling in probe Greg KH
2023-03-30 5:38 ` VaibhaavRam.TL
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=06f47b3f10ab08a6a93ffd7996b7f042845193e3.camel@microchip.com \
--to=vaibhaavram.tl@microchip.com \
--cc=Tharunkumar.Pasumarthi@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).