From: Lizhi Hou <lizhi.hou@amd.com>
To: Jeffrey Hugo <quic_jhugo@quicinc.com>, <quic_carlv@quicinc.com>,
<manivannan.sadhasivam@linaro.org>, <quic_yabdulra@quicinc.com>,
<quic_mattleun@quicinc.com>, <quic_thanson@quicinc.com>
Cc: <ogabbay@kernel.org>, <jacek.lawrynowicz@linux.intel.com>,
<linux-arm-msm@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>, <mhi@lists.linux.dev>
Subject: Re: [PATCH 7/7] accel/qaic: Add AIC200 support
Date: Fri, 20 Dec 2024 09:33:15 -0800 [thread overview]
Message-ID: <ce41ab48-a923-7a29-1c50-3338fed39ea6@amd.com> (raw)
In-Reply-To: <dd83ba8c-0b37-7d1e-39a7-4b25ef7e5faf@quicinc.com>
On 12/20/24 09:26, Jeffrey Hugo wrote:
> On 12/13/2024 5:49 PM, Lizhi Hou wrote:
>>
>> On 12/13/24 13:33, Jeffrey Hugo wrote:
>>> @@ -573,6 +898,13 @@ struct mhi_controller
>>> *qaic_mhi_register_controller(struct pci_dev *pci_dev, voi
>>> mhi_cntrl->nr_irqs = 1;
>>> mhi_cntrl->irq = devm_kmalloc(&pci_dev->dev,
>>> sizeof(*mhi_cntrl->irq), GFP_KERNEL);
>>> + if (family == FAMILY_AIC200) {
>>> + mhi_cntrl->name = "AIC200";
>>> + mhi_cntrl->seg_len = SZ_512K;
>>> + } else {
>>> + mhi_cntrl->name = "AIC100";
>>> + }
>>> +
>>
>> Only AIC200 needs to set 'seg_len'? Maybe these hard coded settings
>> can also be in qaic_device_config?
>
> Yes, seg_len is related to the BHIe loading, which is new from AIC100
> to AIC200.
>
> For the moment, I think I'd like to keep the MHI details
> "encapsulated" within this portion of the driver. With the continuing
> development of AIC200, I'm expecting a bit of volitility here which I
> hope doesn't leak into the rest of the driver.
>
>> It might be better to move after the following check at least.
>
> I agree.
>
>>
>>> if (!mhi_cntrl->irq)
>>> return ERR_PTR(-ENOMEM);
>>> @@ -581,11 +913,11 @@ struct mhi_controller
>>> *qaic_mhi_register_controller(struct pci_dev *pci_dev, voi
>>> if (shared_msi) /* MSI shared with data path, no
>>> IRQF_NO_SUSPEND */
>>> mhi_cntrl->irq_flags = IRQF_SHARED;
>>> - mhi_cntrl->fw_image = "qcom/aic100/sbl.bin";
>>> + mhi_cntrl->fw_image = fw_image_paths[family];
>> Maybe fw_image path in qaic_device_config?
>>> /* use latest configured timeout */
>>> - aic100_config.timeout_ms = mhi_timeout_ms;
>>> - ret = mhi_register_controller(mhi_cntrl, &aic100_config);
>>> + mhi_config.timeout_ms = mhi_timeout_ms;
>>> + ret = mhi_register_controller(mhi_cntrl, &mhi_config);
>>> if (ret) {
>>> pci_err(pci_dev, "mhi_register_controller failed %d\n", ret);
>>> return ERR_PTR(ret);
>>> diff --git a/drivers/accel/qaic/mhi_controller.h
>>> b/drivers/accel/qaic/mhi_controller.h
>>> index 500e7f4af2af..8939f6ae185e 100644
>>> --- a/drivers/accel/qaic/mhi_controller.h
>>> +++ b/drivers/accel/qaic/mhi_controller.h
>>> @@ -8,7 +8,7 @@
>>> #define MHICONTROLLERQAIC_H_
>>> struct mhi_controller *qaic_mhi_register_controller(struct pci_dev
>>> *pci_dev, void __iomem *mhi_bar,
>>> - int mhi_irq, bool shared_msi);
>>> + int mhi_irq, bool shared_msi, int family);
>>> void qaic_mhi_free_controller(struct mhi_controller *mhi_cntrl,
>>> bool link_up);
>>> void qaic_mhi_start_reset(struct mhi_controller *mhi_cntrl);
>>> void qaic_mhi_reset_done(struct mhi_controller *mhi_cntrl);
>>> diff --git a/drivers/accel/qaic/qaic.h b/drivers/accel/qaic/qaic.h
>>> index cf97fd9a7e70..0dbb8e32e4b9 100644
>>> --- a/drivers/accel/qaic/qaic.h
>>> +++ b/drivers/accel/qaic/qaic.h
>>> @@ -34,6 +34,7 @@
>>> enum aic_families {
>>> FAMILY_AIC100,
>>> + FAMILY_AIC200,
>>> FAMILY_MAX,
>>> };
>>> diff --git a/drivers/accel/qaic/qaic_drv.c
>>> b/drivers/accel/qaic/qaic_drv.c
>>> index 4e63e475b389..3b415e2c9431 100644
>>> --- a/drivers/accel/qaic/qaic_drv.c
>>> +++ b/drivers/accel/qaic/qaic_drv.c
>>> @@ -36,6 +36,7 @@ MODULE_IMPORT_NS("DMA_BUF");
>>> #define PCI_DEVICE_ID_QCOM_AIC080 0xa080
>>> #define PCI_DEVICE_ID_QCOM_AIC100 0xa100
>>> +#define PCI_DEVICE_ID_QCOM_AIC200 0xa110
>>> #define QAIC_NAME "qaic"
>>> #define QAIC_DESC "Qualcomm Cloud AI Accelerators"
>>> #define CNTL_MAJOR 5
>>> @@ -66,6 +67,13 @@ static const struct qaic_device_config
>>> aic100_config = {
>>> .dbc_bar_idx = 2,
>>> };
>>> +static const struct qaic_device_config aic200_config = {
>>> + .family = FAMILY_AIC200,
>>> + .bar_mask = BIT(0) | BIT(1) | BIT(2) | BIT(4),
>>
>> Will this pass the BAR mask check in init_pci()?
>
> Yes, BITs 0, 1, 2, 4 would be 0x17 and that value is & with 0x3f
> (masking off upper bits). The result would be 0x17.
It seems BIT(1) is not expected in init_pci?
if (bars != (BIT(0) | BIT(2) | BIT(4))) {
Lizhi
>
>>
>> Thanks,
>>
>> Lizhi
>>
next prev parent reply other threads:[~2024-12-20 17:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 21:33 [PATCH 0/7] accel/qaic: Initial AIC200 support Jeffrey Hugo
2024-12-13 21:33 ` [PATCH 1/7] bus: mhi: host: Refactor BHI/BHIe based firmware loading Jeffrey Hugo
2025-01-07 11:06 ` Jacek Lawrynowicz
2025-01-08 5:24 ` Manivannan Sadhasivam
2025-01-17 16:21 ` Jeffrey Hugo
2024-12-13 21:33 ` [PATCH 2/7] bus: mhi: host: Add a policy to enable image transfer via BHIe in PBL Jeffrey Hugo
2025-01-07 11:12 ` Jacek Lawrynowicz
2025-01-08 5:42 ` Manivannan Sadhasivam
2025-01-17 16:45 ` Jeffrey Hugo
2024-12-13 21:33 ` [PATCH 3/7] accel/qaic: Allocate an exact number of MSIs Jeffrey Hugo
2024-12-13 23:43 ` Lizhi Hou
2024-12-13 21:33 ` [PATCH 4/7] accel/qaic: Add support for MSI-X Jeffrey Hugo
2024-12-13 23:49 ` Lizhi Hou
2024-12-13 21:33 ` [PATCH 5/7] accel/qaic: Mask out SR-IOV PCI resources Jeffrey Hugo
2024-12-14 0:20 ` Lizhi Hou
2024-12-13 21:33 ` [PATCH 6/7] accel/qaic: Add config structs for supported cards Jeffrey Hugo
2024-12-14 0:35 ` Lizhi Hou
2024-12-20 17:15 ` Jeffrey Hugo
2024-12-20 18:08 ` Lizhi Hou
2024-12-13 21:33 ` [PATCH 7/7] accel/qaic: Add AIC200 support Jeffrey Hugo
2024-12-14 0:49 ` Lizhi Hou
2024-12-20 17:26 ` Jeffrey Hugo
2024-12-20 17:33 ` Lizhi Hou [this message]
2024-12-20 17:50 ` Jeffrey Hugo
2024-12-20 18:07 ` Lizhi Hou
2024-12-28 0:19 ` kernel test robot
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=ce41ab48-a923-7a29-1c50-3338fed39ea6@amd.com \
--to=lizhi.hou@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mhi@lists.linux.dev \
--cc=ogabbay@kernel.org \
--cc=quic_carlv@quicinc.com \
--cc=quic_jhugo@quicinc.com \
--cc=quic_mattleun@quicinc.com \
--cc=quic_thanson@quicinc.com \
--cc=quic_yabdulra@quicinc.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