Received: by 2002:a05:6359:6284:b0:131:369:b2a3 with SMTP id se4csp4524172rwb; Tue, 8 Aug 2023 09:39:39 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEYO50WLoX2TUgbdcydNg+j97Qm0zPlrAYHhnq1JzZb7fWNG8nzaC8g/AVohO+39e+CakcJ X-Received: by 2002:a17:903:1247:b0:1bb:c64f:9a5e with SMTP id u7-20020a170903124700b001bbc64f9a5emr289921plh.5.1691512778831; Tue, 08 Aug 2023 09:39:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1691512778; cv=none; d=google.com; s=arc-20160816; b=upo9nGu2T34gT74WaBaimqzlTwhxIQ/INUCSLAVZZ++liSMN01UTuetuSQ8hfgyDin T2ShdSX2rzSjNAaIFHaysDKqIY6NJflm8TtibDC5qSZPg5fHJ3tcR4K981juBwz9N7Rf IXYAfWtVVEU/g6DxTELGwpJUXwA0ksCDDnxCXeQCZtYY1X2rA3jySZQxoAK/DJBbq8nk rORDWxoLW/rRU3hh9BRuiMQkRoNIC+5PKVpQ2vMclkbAbDVfNGvinh2nNnPscNhVbmww kA4AkvC9KzZ2A4jtK2ScX9GI4hJEGRXWGObEBoo0dk6SD1NlO4krCpK1kFRkDBJoRmaR nmlA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=fp878F0hmKDeXFH9UOVDCQEqGxOPYfiUa5nOqxrxFG0=; fh=kCP8R/Q/QnCQgqoKBHt8aMfBwJ9zbxvnDBLTOt6Dk4c=; b=kAmqOvCz9yWNoF3L7pI7GYyeyzXMKGKi6iZ2OARq7S7Ykps66+vFIDrerSmKHoqNye 8lcuWPepctXf8pwGh/ekTUxo8Bg2Csq479UIwug4VnJ9xqzkRPQJMEiCcaNreSBcx7NC D8cXKW1hc/LpgSfzQ+ZK1cw6bwIBQsYaReIJCC2C3e896j38Gl7zMXQxLVqSI41NrO9g U8V6kA1/te9Pe7SSoCbg8yKwLwgVHS/8Hg6NZYO4vJou+u+I7z+8KTOLiXDYsM9GEAs4 EYNACAuQ6y/1/i4s3rz7iUYsCs/N4TM50VJ25nvRuhT/svnJmHt/oSPmYTC0CsWkBGDY GVXg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=vI5llFbv; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b14-20020a170902650e00b001b3eeaad177si5023252plk.99.2023.08.08.09.39.25; Tue, 08 Aug 2023 09:39:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=vI5llFbv; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231612AbjHHQHb (ORCPT + 99 others); Tue, 8 Aug 2023 12:07:31 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46242 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229669AbjHHQFw (ORCPT ); Tue, 8 Aug 2023 12:05:52 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3BB3B10CA; Tue, 8 Aug 2023 08:45:37 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 6BC10624BA; Tue, 8 Aug 2023 10:59:42 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id AD1D6C433C7; Tue, 8 Aug 2023 10:59:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1691492381; bh=VotGcBSEYZDEARbAEuumU9Pwvb8zJMGSKr4IEav+kbc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=vI5llFbvkjg587mNFW4eWev9eaAoawqlJIG+0KeGyknUR52Pd3WRfHl3qep8ewm5W 3zX8CuIHMFwiG+nuof9hVPTD7dx4m1lYRjFN1ze56kO2+ZeWe4a6tQkta/gRNtZLup Tqk3OgBvICnhGJJVLyYWoGOufdapycC6Jn3bSwxAftEllsicTuMlAd3aLEr47kEJpk 1s2vzLKRzK8vi7bcuDjQaUlEe4SNp0Lsmj/WQceyDwaFlvQeCI5XYUa+pQtZ1E4ceP UQzhVOOnlY0v53suZiNbBU7eLg8xGNan6f0V2cX6UhzVglz2PaIv6Xp+JdbvkR1GmX eoK/ytAIKn8LA== Date: Tue, 8 Aug 2023 16:29:28 +0530 From: Manivannan Sadhasivam To: Qiang Yu Cc: Manivannan Sadhasivam , quic_jhugo@quicinc.com, mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, quic_cang@quicinc.com, quic_mrana@quicinc.com Subject: Re: [PATCH] bus: mhi: host: pci_generic: Add SDX75 based modem support Message-ID: <20230808105928.GF4990@thinkpad> References: <1691460215-45383-1-git-send-email-quic_qianyu@quicinc.com> <20230808075103.GD4990@thinkpad> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, RCVD_IN_DNSWL_BLOCKED,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 08, 2023 at 04:53:32PM +0800, Qiang Yu wrote: > > On 8/8/2023 3:51 PM, Manivannan Sadhasivam wrote: > > On Tue, Aug 08, 2023 at 10:03:35AM +0800, Qiang Yu wrote: > > > Add generic info for SDX75 based modems. SDX75 takes longer than expected > > > (default, 8 seconds) to set ready after reboot. Hence add optional ready > > > timeout parameter to wait enough for device ready as part of power up > > > sequence. > > > > > > Signed-off-by: Qiang Yu > > > --- > > > drivers/bus/mhi/host/init.c | 1 + > > > drivers/bus/mhi/host/main.c | 7 ++++++- > > > drivers/bus/mhi/host/pci_generic.c | 22 ++++++++++++++++++++++ > > > drivers/bus/mhi/host/pm.c | 6 +++++- > > > include/linux/mhi.h | 4 ++++ > > > 5 files changed, 38 insertions(+), 2 deletions(-) > > > > > > diff --git a/drivers/bus/mhi/host/init.c b/drivers/bus/mhi/host/init.c > > > index f78aefd..65ceac1 100644 > > > --- a/drivers/bus/mhi/host/init.c > > > +++ b/drivers/bus/mhi/host/init.c > > > @@ -881,6 +881,7 @@ static int parse_config(struct mhi_controller *mhi_cntrl, > > > if (!mhi_cntrl->timeout_ms) > > > mhi_cntrl->timeout_ms = MHI_TIMEOUT_MS; > > > + mhi_cntrl->ready_timeout_ms = config->ready_timeout_ms; > > > mhi_cntrl->bounce_buf = config->use_bounce_buf; > > > mhi_cntrl->buffer_len = config->buf_len; > > > if (!mhi_cntrl->buffer_len) > > > diff --git a/drivers/bus/mhi/host/main.c b/drivers/bus/mhi/host/main.c > > > index 74a7543..8590926 100644 > > > --- a/drivers/bus/mhi/host/main.c > > > +++ b/drivers/bus/mhi/host/main.c > > > @@ -43,8 +43,13 @@ int __must_check mhi_poll_reg_field(struct mhi_controller *mhi_cntrl, > > > u32 mask, u32 val, u32 delayus) > > > { > > > int ret; > > > - u32 out, retry = (mhi_cntrl->timeout_ms * 1000) / delayus; > > > + u32 out, retry; > > > + u32 timeout_ms = mhi_cntrl->timeout_ms; > > > + if (mhi_cntrl->ready_timeout_ms && mask == MHISTATUS_READY_MASK) > > > + timeout_ms = mhi_cntrl->ready_timeout_ms; > > Instead of handling the timeout inside mhi_poll_reg_field(), you should pass the > > appropriate timeout value to this function. > OK, will do. > > > > > + > > > + retry = (timeout_ms * 1000) / delayus; > > > while (retry--) { > > > ret = mhi_read_reg_field(mhi_cntrl, base, offset, mask, &out); > > > if (ret) > > > diff --git a/drivers/bus/mhi/host/pci_generic.c b/drivers/bus/mhi/host/pci_generic.c > > > index fcd80bc..9c601f0 100644 > > > --- a/drivers/bus/mhi/host/pci_generic.c > > > +++ b/drivers/bus/mhi/host/pci_generic.c > > > @@ -269,6 +269,16 @@ static struct mhi_event_config modem_qcom_v1_mhi_events[] = { > > > MHI_EVENT_CONFIG_HW_DATA(5, 2048, 101) > > > }; > > > +static const struct mhi_controller_config modem_qcom_v2_mhiv_config = { > > > + .max_channels = 128, > > > + .timeout_ms = 8000, > > > + .ready_timeout_ms = 50000, > > > + .num_channels = ARRAY_SIZE(modem_qcom_v1_mhi_channels), > > > + .ch_cfg = modem_qcom_v1_mhi_channels, > > > + .num_events = ARRAY_SIZE(modem_qcom_v1_mhi_events), > > > + .event_cfg = modem_qcom_v1_mhi_events, > > > +}; > > > + > > > static const struct mhi_controller_config modem_qcom_v1_mhiv_config = { > > > .max_channels = 128, > > > .timeout_ms = 8000, > > > @@ -278,6 +288,16 @@ static const struct mhi_controller_config modem_qcom_v1_mhiv_config = { > > > .event_cfg = modem_qcom_v1_mhi_events, > > > }; > > > +static const struct mhi_pci_dev_info mhi_qcom_sdx75_info = { > > > + .name = "qcom-sdx75m", > > > + .fw = "qcom/sdx75m/xbl.elf", > > > + .edl = "qcom/sdx75m/edl.mbn", > > > + .config = &modem_qcom_v2_mhiv_config, > > > + .bar_num = MHI_PCI_DEFAULT_BAR_NUM, > > > + .dma_data_width = 32, > > > + .sideband_wake = false, > > > +}; > > > + > > > static const struct mhi_pci_dev_info mhi_qcom_sdx65_info = { > > > .name = "qcom-sdx65m", > > > .fw = "qcom/sdx65m/xbl.elf", > > > @@ -597,6 +617,8 @@ static const struct pci_device_id mhi_pci_id_table[] = { > > > .driver_data = (kernel_ulong_t) &mhi_telit_fn990_info }, > > > { PCI_DEVICE(PCI_VENDOR_ID_QCOM, 0x0308), > > > .driver_data = (kernel_ulong_t) &mhi_qcom_sdx65_info }, > > > + { PCI_DEVICE(PCI_VENDOR_ID_QCOM, 0x0309), > > > + .driver_data = (kernel_ulong_t) &mhi_qcom_sdx75_info }, > > > { PCI_DEVICE(PCI_VENDOR_ID_QUECTEL, 0x1001), /* EM120R-GL (sdx24) */ > > > .driver_data = (kernel_ulong_t) &mhi_quectel_em1xx_info }, > > > { PCI_DEVICE(PCI_VENDOR_ID_QUECTEL, 0x1002), /* EM160R-GL (sdx24) */ > > > diff --git a/drivers/bus/mhi/host/pm.c b/drivers/bus/mhi/host/pm.c > > > index 8a4362d..6f049e0 100644 > > > --- a/drivers/bus/mhi/host/pm.c > > > +++ b/drivers/bus/mhi/host/pm.c > > > @@ -1202,14 +1202,18 @@ EXPORT_SYMBOL_GPL(mhi_power_down); > > > int mhi_sync_power_up(struct mhi_controller *mhi_cntrl) > > > { > > > int ret = mhi_async_power_up(mhi_cntrl); > > > + u32 timeout_ms; > > > if (ret) > > > return ret; > > > + /* Some devices need more time to set ready during power up */ > > > + timeout_ms = mhi_cntrl->ready_timeout_ms ? > > > + mhi_cntrl->ready_timeout_ms : mhi_cntrl->timeout_ms; > > Since you are using this extended timeout value in a couple of places (not just > > for checking READY_STATE), it is better to use the existing "timeout_ms" > > parameter. > > > > - Mani > > We use ready_timeout_ms here is because READY_STATE is polled in a > workqueue,  in parallel with waiting valid EE. > > That means we start to wait valid EE and poll ready like at same time > instead of starting to wait EE after ready state. > > Thus the total time it takes to wait valid EE is about the time for polling > ready. > Yes, but why can't you still increase "timeout_ms" for SDX75 and use the same? Btw, please do not send another version while the discussion is going on for the current one. - Mani > > > wait_event_timeout(mhi_cntrl->state_event, > > > MHI_IN_MISSION_MODE(mhi_cntrl->ee) || > > > MHI_PM_IN_ERROR_STATE(mhi_cntrl->pm_state), > > > - msecs_to_jiffies(mhi_cntrl->timeout_ms)); > > > + msecs_to_jiffies(timeout_ms)); > > > ret = (MHI_IN_MISSION_MODE(mhi_cntrl->ee)) ? 0 : -ETIMEDOUT; > > > if (ret) > > > diff --git a/include/linux/mhi.h b/include/linux/mhi.h > > > index f6de4b6..a43e5f8 100644 > > > --- a/include/linux/mhi.h > > > +++ b/include/linux/mhi.h > > > @@ -266,6 +266,7 @@ struct mhi_event_config { > > > * struct mhi_controller_config - Root MHI controller configuration > > > * @max_channels: Maximum number of channels supported > > > * @timeout_ms: Timeout value for operations. 0 means use default > > > + * @ready_timeout_ms: Timeout value for waiting device to be ready (optional) > > > * @buf_len: Size of automatically allocated buffers. 0 means use default > > > * @num_channels: Number of channels defined in @ch_cfg > > > * @ch_cfg: Array of defined channels > > > @@ -277,6 +278,7 @@ struct mhi_event_config { > > > struct mhi_controller_config { > > > u32 max_channels; > > > u32 timeout_ms; > > > + u32 ready_timeout_ms; > > > u32 buf_len; > > > u32 num_channels; > > > const struct mhi_channel_config *ch_cfg; > > > @@ -326,6 +328,7 @@ struct mhi_controller_config { > > > * @pm_mutex: Mutex for suspend/resume operation > > > * @pm_lock: Lock for protecting MHI power management state > > > * @timeout_ms: Timeout in ms for state transitions > > > + * @ready_timeout_ms: Timeout in ms for waiting device to be ready (optional) > > > * @pm_state: MHI power management state > > > * @db_access: DB access states > > > * @ee: MHI device execution environment > > > @@ -413,6 +416,7 @@ struct mhi_controller { > > > struct mutex pm_mutex; > > > rwlock_t pm_lock; > > > u32 timeout_ms; > > > + u32 ready_timeout_ms; > > > u32 pm_state; > > > u32 db_access; > > > enum mhi_ee_type ee; > > > -- > > > 2.7.4 > > > > -- மணிவண்ணன் சதாசிவம்