From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Vivek Pernamitta <quic_vpernami@quicinc.com>
Cc: mhi@lists.linux.dev, quic_qianyu@quicinc.com,
quic_vbadigan@quicinc.com, quic_krichai@quicinc.com,
quic_skananth@quicinc.com, quic_mrana@quicinc.com,
Slark Xiao <slark_xiao@163.com>,
Mank Wang <mank.wang@netprisma.us>,
Jeff Johnson <quic_jjohnson@quicinc.com>,
Fabio Porcedda <fabio.porcedda@gmail.com>,
"open list:MHI BUS" <linux-arm-msm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] bus: mhi: host: pci_generic: Add support for QDU100 device
Date: Thu, 10 Oct 2024 16:26:58 +0530 [thread overview]
Message-ID: <20241010105658.mckqvumjrglu6236@thinkpad> (raw)
In-Reply-To: <20241007081543.3475027-1-quic_vpernami@quicinc.com>
On Mon, Oct 07, 2024 at 01:45:41PM +0530, Vivek Pernamitta wrote:
> Add MHI controller configuration for QDU100 device.
>
> This Qualcomm QDU100 device is inline accelerator card
> which is an extension to QRU100 5G RAN platform.
> which is designed to simplify 5G deployments by offering
> a turnkey solution for ease of deployment with O-RAN
> fronthaul and 5G NR layer 1 High (L1 High) processing,
> and to accelerate operator and infrastructure vendor
> adoption of virtualized RAN platforms.
>
> Currently IP_SW1/2 channel support is not present in
> mhi_net driver, will be supporting them in future.
I don't know what column width you are using, but please use 75 columns for
patch descriptions.
>
> https://docs.qualcomm.com/bundle/publicresource/87-79371-1_REV_A_Qualcomm_X100_5G_RAN_Accelerator_Card_Product_Brief.pdf
> Signed-off-by: Vivek Pernamitta <quic_vpernami@quicinc.com>
>
> ---
> changes from V1:
> - Changing naming convention from modem_qcom_qdu100*
> to mhi_qcom_qdu100*
> - Added more commit test for IP_SW1/2 channels.
> - Fixed and corrected by passing mhi_pci_dev_info struct
> instead of mhi_controller_config.
> ---
> ---
> drivers/bus/mhi/host/pci_generic.c | 60 ++++++++++++++++++++++++++++++
> 1 file changed, 60 insertions(+)
>
> diff --git a/drivers/bus/mhi/host/pci_generic.c b/drivers/bus/mhi/host/pci_generic.c
> index 9938bb034c1c..b9b7dd8d9411 100644
> --- a/drivers/bus/mhi/host/pci_generic.c
> +++ b/drivers/bus/mhi/host/pci_generic.c
> @@ -245,6 +245,63 @@ struct mhi_pci_dev_info {
> .channel = ch_num, \
> }
>
> +static const struct mhi_channel_config mhi_qcom_qdu100_channels[] = {
> + MHI_CHANNEL_CONFIG_UL(0, "LOOPBACK", 32, 2),
> + MHI_CHANNEL_CONFIG_DL(1, "LOOPBACK", 32, 2),
> + MHI_CHANNEL_CONFIG_UL_SBL(2, "SAHARA", 128, 1),
> + MHI_CHANNEL_CONFIG_DL_SBL(3, "SAHARA", 128, 1),
> + MHI_CHANNEL_CONFIG_UL(4, "DIAG", 64, 3),
> + MHI_CHANNEL_CONFIG_DL(5, "DIAG", 64, 3),
> + MHI_CHANNEL_CONFIG_UL(9, "QDSS", 64, 3),
> + MHI_CHANNEL_CONFIG_UL(14, "NMEA", 32, 4),
> + MHI_CHANNEL_CONFIG_DL(15, "NMEA", 32, 4),
> + MHI_CHANNEL_CONFIG_UL(16, "CSM_CTRL", 32, 4),
> + MHI_CHANNEL_CONFIG_DL(17, "CSM_CTRL", 32, 4),
> + MHI_CHANNEL_CONFIG_UL(40, "MHI_PHC", 32, 4),
> + MHI_CHANNEL_CONFIG_DL(41, "MHI_PHC", 32, 4),
> + MHI_CHANNEL_CONFIG_UL(46, "IP_SW0", 256, 5),
> + MHI_CHANNEL_CONFIG_DL(47, "IP_SW0", 256, 5),
> + MHI_CHANNEL_CONFIG_UL(48, "IP_SW1", 256, 6),
> + MHI_CHANNEL_CONFIG_DL(49, "IP_SW1", 256, 6),
> + MHI_CHANNEL_CONFIG_UL(50, "IP_SW2", 256, 7),
> + MHI_CHANNEL_CONFIG_DL(51, "IP_SW2", 256, 7),
Please drop these unsupported IP_SW channels until you add support in mhi-net
driver.
> +};
> +
> +static struct mhi_event_config mhi_qcom_qdu100_events[] = {
> + /* first ring is control+data ring */
> + MHI_EVENT_CONFIG_CTRL(0, 64),
> + /* SAHARA dedicated event ring */
> + MHI_EVENT_CONFIG_SW_DATA(1, 256),
> + /* Software channels dedicated event ring */
> + MHI_EVENT_CONFIG_SW_DATA(2, 64),
> + MHI_EVENT_CONFIG_SW_DATA(3, 256),
> + MHI_EVENT_CONFIG_SW_DATA(4, 256),
> + /* Software IP channels dedicated event ring */
> + MHI_EVENT_CONFIG_SW_DATA(5, 512),
> + MHI_EVENT_CONFIG_SW_DATA(6, 512),
> + MHI_EVENT_CONFIG_SW_DATA(7, 512),
> +};
> +
> +static const struct mhi_controller_config mhi_qcom_qdu100_config = {
> + .max_channels = 128,
> + .timeout_ms = 120000,
> + .num_channels = ARRAY_SIZE(mhi_qcom_qdu100_channels),
> + .ch_cfg = mhi_qcom_qdu100_channels,
> + .num_events = ARRAY_SIZE(mhi_qcom_qdu100_events),
> + .event_cfg = mhi_qcom_qdu100_events,
> +};
> +
> +static const struct mhi_pci_dev_info mhi_qcom_qdu100_info = {
> + .name = "qcom-lassen",
I don't think you can use internal chip name in the drivers. Please use the
actual chip code like QDU100.
> + .fw = "qcom/lassen/xbl_s.melf",
> + .edl = "qcom/lassen/edl.mbn",
Could you please push these fw to linux-firmware repo? This is a requirement to
get this patch accepted. I should've imposed this at the start itself...
> + .edl_trigger = true,
> + .config = &mhi_qcom_qdu100_config,
> + .bar_num = MHI_PCI_DEFAULT_BAR_NUM,
> + .dma_data_width = 32,
> + .sideband_wake = false,
> +};
> +
> static const struct mhi_channel_config modem_qcom_v1_mhi_channels[] = {
> MHI_CHANNEL_CONFIG_UL(4, "DIAG", 16, 1),
> MHI_CHANNEL_CONFIG_DL(5, "DIAG", 16, 1),
> @@ -822,6 +879,9 @@ static const struct pci_device_id mhi_pci_id_table[] = {
> /* NETPRISMA FCUN69 (SDX6X) */
> { PCI_DEVICE(PCI_VENDOR_ID_NETPRISMA, 0x1001),
> .driver_data = (kernel_ulong_t) &mhi_netprisma_fcun69_info },
> + /* QDU100, x100-DU */
> + { PCI_DEVICE(PCI_VENDOR_ID_QCOM, 0x0601),
> + .driver_data = (kernel_ulong_t)&mhi_qcom_qdu100_info },
Spare after (kernel_ulong_t) and also sort the entries as per the comment above
mhi_pci_id_table[].
- Mani
--
மணிவண்ணன் சதாசிவம்
prev parent reply other threads:[~2024-10-10 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 8:15 Vivek Pernamitta
2024-10-10 10:56 ` Manivannan Sadhasivam [this message]
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=20241010105658.mckqvumjrglu6236@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=fabio.porcedda@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mank.wang@netprisma.us \
--cc=mhi@lists.linux.dev \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_krichai@quicinc.com \
--cc=quic_mrana@quicinc.com \
--cc=quic_qianyu@quicinc.com \
--cc=quic_skananth@quicinc.com \
--cc=quic_vbadigan@quicinc.com \
--cc=quic_vpernami@quicinc.com \
--cc=slark_xiao@163.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
all inboxes | Powered by JetHome®