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
Subject: Re: Reg: New MFD Driver for my PCIe Device
Date: Tue, 16 Nov 2021 15:20:26 +0100 [thread overview]
Message-ID: <YZO+KktO3OhDEtlq@kroah.com> (raw)
In-Reply-To: <CH0PR11MB5380791976D5837E024D5679E9999@CH0PR11MB5380.namprd11.prod.outlook.com>
On Tue, Nov 16, 2021 at 11:34:24AM +0000, Kumaravel.Thiagarajan@microchip.com wrote:
> Dear Greg K-H & Lee Jones,
>
> Thanks for your inputs and I need more of your help to understand things better.
>
> I took this MFD route not just based on the recommendation from Linus Walleij but also based on the kernel documentation @ /Documentation/driver-api/driver-model/platform.rst which states as below.
>
> "Rarely, a platform_device will be connected through a segment of some other kind of bus; but its registers will still be directly addressable."
>
> I visualized these two (GPIO controller & OTP/EEPROM controller) devices as platform devices present on the same PCI function and these two devices are not detectable unless the base PCI function driver enumerates them and anyway their registers are directly addressable.
> Hence, I thought that the platform driver architecture is inclusive of devices like this.
Sorry, but no. Again, platform devices are ONLY for actual platform
devices, not "things on a device that happens to be on another bus
device". Like PCI devices.
That is what the auxiliary bus code was written for, please read
Documentation/driver-api/auxiliary_bus.rst for how to use it.
> Please let me know your comments.
>
> Also please let me know if I can talk to any of you over a webex call to get clarifications on my further doubts.
Email works best, video chats for every patch review does not scale at
all :)
thanks,
greg k-h
next prev parent reply other threads:[~2021-11-16 14:20 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 [this message]
2021-11-19 9:16 ` Kumaravel.Thiagarajan
2021-11-19 14:53 ` Greg KH
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=YZO+KktO3OhDEtlq@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Kumaravel.Thiagarajan@microchip.com \
--cc=LakshmiPraveen.Kopparthi@microchip.com \
--cc=Pragash.Mangalapandian@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