From: Frank Li <Frank.li@nxp.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: alexandre.belloni@bootlin.com, linux-i3c@lists.infradead.org
Subject: Re: [PATCH 08/13] i3c: mipi-i3c-hci-pci: Allocate a structure for mipi_i3c_hci_pci device information
Date: Wed, 12 Nov 2025 15:17:14 -0500 [thread overview]
Message-ID: <aRTrSjchN8vbkhf8@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <2c4c5eee-9228-4790-9954-07e9e9ecfcde@intel.com>
On Wed, Nov 12, 2025 at 09:25:14PM +0200, Adrian Hunter wrote:
> On 12/11/2025 18:41, Frank Li wrote:
> > On Wed, Nov 12, 2025 at 12:03:34PM +0200, Adrian Hunter wrote:
> >> Allocate a structure for mipi_i3c_hci_pci device information, in
> >> preparation for additional changes that need to store mipi_i3c_hci_pci
> >> device-specific information.
> >>
> >> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
> >> ---
> >> .../master/mipi-i3c-hci/mipi-i3c-hci-pci.c | 29 ++++++++++++-------
> >> 1 file changed, 19 insertions(+), 10 deletions(-)
> >>
> >> diff --git a/drivers/i3c/master/mipi-i3c-hci/mipi-i3c-hci-pci.c b/drivers/i3c/master/mipi-i3c-hci/mipi-i3c-hci-pci.c
> >> index b3b6b6f43af2..9fa89af7479f 100644
> >> --- a/drivers/i3c/master/mipi-i3c-hci/mipi-i3c-hci-pci.c
> >> +++ b/drivers/i3c/master/mipi-i3c-hci/mipi-i3c-hci-pci.c
> >> @@ -14,6 +14,10 @@
> >> #include <linux/pci.h>
> >> #include <linux/platform_device.h>
> >>
> >> +struct mipi_i3c_hci_pci {
> >> + struct platform_device *pdev;
> >> +};
> >> +
> >
> > Is it simpler by using platform_device_register_data(), pass down platform
> > related information by void *data?
>
> No, this is just a normal allocated structure for the PCI driver
> (mipi_i3c_hci_pci) to put information related to the PCI device.
> It is later used to store the current Latency Tolerance Reporting (LTR)
> register values.
Is it static value, or does it change after boot in other words?
>
> So it is not the same thing as platform_data.
Base on your code to create platform data is duplicate what's did by
platform_device_register_data().
The pci device create platform devices, platform driver should not use
pci's information directly. platform driver should be reused if it probe
from acpi or dt-tree.
I think it'd better pass down platform data information, which can include
callback to fetch needed information for difference's parent devices.
Frank
>
> >
> > Frank
> >> struct mipi_i3c_hci_pci_info {
> >> int (*init)(struct pci_dev *pci);
> >> };
> >> @@ -71,10 +75,14 @@ static int mipi_i3c_hci_pci_probe(struct pci_dev *pci,
> >> const struct pci_device_id *id)
> >> {
> >> const struct mipi_i3c_hci_pci_info *info;
> >> - struct platform_device *pdev;
> >> + struct mipi_i3c_hci_pci *hci;
> >> struct resource res[2];
> >> int dev_id, ret;
> >>
> >> + hci = devm_kzalloc(&pci->dev, sizeof(*hci), GFP_KERNEL);
> >> + if (!hci)
> >> + return -ENOMEM;
> >> +
> >> ret = pcim_enable_device(pci);
> >> if (ret)
> >> return ret;
> >> @@ -95,14 +103,14 @@ static int mipi_i3c_hci_pci_probe(struct pci_dev *pci,
> >> if (dev_id < 0)
> >> return dev_id;
> >>
> >> - pdev = platform_device_alloc("mipi-i3c-hci", dev_id);
> >> - if (!pdev)
> >> + hci->pdev = platform_device_alloc("mipi-i3c-hci", dev_id);
> >> + if (!hci->pdev)
> >> return -ENOMEM;
> >>
> >> - pdev->dev.parent = &pci->dev;
> >> - device_set_node(&pdev->dev, dev_fwnode(&pci->dev));
> >> + hci->pdev->dev.parent = &pci->dev;
> >> + device_set_node(&hci->pdev->dev, dev_fwnode(&pci->dev));
> >>
> >> - ret = platform_device_add_resources(pdev, res, ARRAY_SIZE(res));
> >> + ret = platform_device_add_resources(hci->pdev, res, ARRAY_SIZE(res));
> >> if (ret)
> >> goto err;
> >>
> >> @@ -113,23 +121,24 @@ static int mipi_i3c_hci_pci_probe(struct pci_dev *pci,
> >> goto err;
> >> }
> >>
> >> - ret = platform_device_add(pdev);
> >> + ret = platform_device_add(hci->pdev);
> >> if (ret)
> >> goto err;
> >>
> >> - pci_set_drvdata(pci, pdev);
> >> + pci_set_drvdata(pci, hci);
> >>
> >> return 0;
> >>
> >> err:
> >> - platform_device_put(pdev);
> >> + platform_device_put(hci->pdev);
> >> ida_free(&mipi_i3c_hci_pci_ida, dev_id);
> >> return ret;
> >> }
> >>
> >> static void mipi_i3c_hci_pci_remove(struct pci_dev *pci)
> >> {
> >> - struct platform_device *pdev = pci_get_drvdata(pci);
> >> + struct mipi_i3c_hci_pci *hci = pci_get_drvdata(pci);
> >> + struct platform_device *pdev = hci->pdev;
> >> int dev_id = pdev->id;
> >>
> >> platform_device_unregister(pdev);
> >> --
> >> 2.51.0
> >>
> >>
> >> --
> >> linux-i3c mailing list
> >> linux-i3c@lists.infradead.org
> >> http://lists.infradead.org/mailman/listinfo/linux-i3c
>
>
> --
> linux-i3c mailing list
> linux-i3c@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-i3c
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2025-11-12 20:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 10:03 [PATCH 00/13] i3c: mipi-i3c-hci-pci: Add LTR support for Intel controllers Adrian Hunter
2025-11-12 10:03 ` [PATCH 01/13] i3c: mipi-i3c-hci-pci: Set 64-bit DMA mask " Adrian Hunter
2025-11-12 15:51 ` Frank Li
2025-11-12 10:03 ` [PATCH 02/13] i3c: mipi-i3c-hci-pci: Move all Intel-related definitions together Adrian Hunter
2025-11-12 15:53 ` Frank Li
2025-11-13 12:58 ` Adrian Hunter
2025-11-12 10:03 ` [PATCH 03/13] i3c: mipi-i3c-hci-pci: Rename some Intel-related identifiers Adrian Hunter
2025-11-12 15:57 ` Frank Li
2025-11-13 13:01 ` Adrian Hunter
2025-11-13 16:19 ` Frank Li
2025-11-13 16:57 ` Adrian Hunter
2025-11-13 17:17 ` Frank Li
2025-11-12 10:03 ` [PATCH 04/13] i3c: mipi-i3c-hci-pci: Use readl_poll_timeout() Adrian Hunter
2025-11-12 15:59 ` Frank Li
2025-11-14 16:02 ` Alexandre Belloni
2025-11-14 16:43 ` Frank Li
2025-11-14 17:20 ` Alexandre Belloni
2025-11-12 10:03 ` [PATCH 05/13] i3c: mipi-i3c-hci-pci: Constify driver data Adrian Hunter
2025-11-12 16:01 ` Frank Li
2025-11-12 10:03 ` [PATCH 06/13] i3c: mipi-i3c-hci-pci: Factor out private registers ioremapping Adrian Hunter
2025-11-12 16:09 ` Frank Li
2025-11-13 13:02 ` Adrian Hunter
2025-11-12 10:03 ` [PATCH 07/13] i3c: mipi-i3c-hci-pci: Factor out intel_reset() Adrian Hunter
2025-11-12 16:13 ` Frank Li
2025-11-12 10:03 ` [PATCH 08/13] i3c: mipi-i3c-hci-pci: Allocate a structure for mipi_i3c_hci_pci device information Adrian Hunter
2025-11-12 16:41 ` Frank Li
2025-11-12 19:25 ` Adrian Hunter
2025-11-12 20:17 ` Frank Li [this message]
2025-11-13 13:15 ` Adrian Hunter
2025-11-13 16:25 ` Frank Li
2025-11-12 10:03 ` [PATCH 09/13] i3c: mipi-i3c-hci-pci: Change callback parameter Adrian Hunter
2025-11-12 10:03 ` [PATCH 10/13] i3c: mipi-i3c-hci-pci: Add exit callback Adrian Hunter
2025-11-12 10:03 ` [PATCH 11/13] i3c: mipi-i3c-hci-pci: Allocate a structure for Intel controller information Adrian Hunter
2025-11-12 10:03 ` [PATCH 12/13] i3c: mipi-i3c-hci-pci: Add LTR support for Intel controllers Adrian Hunter
2025-11-12 10:03 ` [PATCH 13/13] i3c: mipi-i3c-hci-pci: Set d3cold_delay to 0 " Adrian Hunter
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=aRTrSjchN8vbkhf8@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=adrian.hunter@intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-i3c@lists.infradead.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).