Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1810183pxb; Sat, 27 Feb 2021 00:35:23 -0800 (PST) X-Google-Smtp-Source: ABdhPJzD5vxy7htTZepKDJkMqrwQysaCPCMsPDQ1v74cOsTiTxMr5rrwdEMmS3q59RZ7roaxyEJv X-Received: by 2002:aa7:ce1a:: with SMTP id d26mr994428edv.206.1614414923299; Sat, 27 Feb 2021 00:35:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614414923; cv=none; d=google.com; s=arc-20160816; b=VEEM21tVygBHNqj4nVXjBGN5LsYuRD0RmWeICYXTRJR0F5hdlZwJWvEckqDrfZdkRf 9TVfXMS2ub8ywG28Te73BDaysW8LvcXmUzaCAfe6kUIDWkz3dp4tx//cMaU9jM482Kv0 i0zwXQ3PIkNutkF2NyqenNhqZlxNpGoOTZmXqU6rBnjThLtWkuCWcGuMLyyzGo4UkfdG J9IKBL1ouLa9jPYkivtOiK/KgjWWAkXRkeemzUXJg7qh5ig48eHnWREqlvELkoo8vYnl zwKgwWh6yplMVsJEmk6T5vEzWgFhEnZOdteOHuR2eTvrcD+qgnw9NeX3we1CaaF6/U+Q HdNg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:message-id:references:in-reply-to :subject:cc:to:from:date:content-transfer-encoding:mime-version :sender:dkim-signature; bh=vTSvXCBTxMLKclBkDKtSO8OPYx3V4W4y9TZ3gbaKO4g=; b=QyCfg5cs2ZTeRPVCvCURRUZqXyoee1+Brpz+VM+1Do/IdKTFHldwT4M5i7epVkQSRd vW8W0R1J946P49QYvAna8EWO62qTNl/OmRcT3a/NPTHYHeq+VYDPn5i+A+QIpU5Q/tuG TONOLVXuW86M6BKLKsIZzE1Nf4Hsc8xxprR+THJnDW1Mcg5y25XWKV7m/as9H/Qp90C6 w65bZNhELxDJHy0dJVvgz/+KPGMy1dNkxnPEgr9GnmAeCicnMuK5m9vhayi+GEGpi3kl 77BftwBUpWy8tuIx732avlOVgWwFM6A2eOcPU2eutOgHRiRYvWPIch1oxnPTQuOyUlp1 YiRA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@mg.codeaurora.org header.s=smtp header.b=CnZ6Oilt; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k2si7384871ejg.379.2021.02.27.00.34.28; Sat, 27 Feb 2021 00:35:23 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@mg.codeaurora.org header.s=smtp header.b=CnZ6Oilt; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229864AbhB0I0E (ORCPT + 99 others); Sat, 27 Feb 2021 03:26:04 -0500 Received: from m42-2.mailgun.net ([69.72.42.2]:27449 "EHLO m42-2.mailgun.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229795AbhB0I0C (ORCPT ); Sat, 27 Feb 2021 03:26:02 -0500 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mg.codeaurora.org; q=dns/txt; s=smtp; t=1614414341; h=Message-ID: References: In-Reply-To: Subject: Cc: To: From: Date: Content-Transfer-Encoding: Content-Type: MIME-Version: Sender; bh=vTSvXCBTxMLKclBkDKtSO8OPYx3V4W4y9TZ3gbaKO4g=; b=CnZ6Oiltt8iKTiDAgwxb7whFM8q/vE1Yw+oRGQ3iykvXL/kHBjDD7n6iqFfZbHVWY2UWMUTv 2ppbRv8Q7ABONUsEMWhTCGT3EUIpM4nSQd9eRzy+ArUUsuqI0lWdW9TCaa7WiYYYEW5lT5lh Q61DEmFZJqGj6ooQ9E5aJvTotzw= X-Mailgun-Sending-Ip: 69.72.42.2 X-Mailgun-Sid: WyI0MWYwYSIsICJsaW51eC1rZXJuZWxAdmdlci5rZXJuZWwub3JnIiwgImJlOWU0YSJd Received: from smtp.codeaurora.org (ec2-35-166-182-171.us-west-2.compute.amazonaws.com [35.166.182.171]) by smtp-out-n07.prod.us-west-2.postgun.com with SMTP id 603a01ea8f0d5ba6c5e9b77b (version=TLS1.2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256); Sat, 27 Feb 2021 08:25:14 GMT Sender: gokulsri=codeaurora.org@mg.codeaurora.org Received: by smtp.codeaurora.org (Postfix, from userid 1001) id BBCACC43461; Sat, 27 Feb 2021 08:25:13 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-caf-mail-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=2.0 tests=ALL_TRUSTED,BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gokulsri) by smtp.codeaurora.org (Postfix) with ESMTPSA id D83BDC433CA; Sat, 27 Feb 2021 08:25:12 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 27 Feb 2021 13:55:12 +0530 From: gokulsri@codeaurora.org To: bbhatt@codeaurora.org, Manivannan Sadhasivam , jhugo@codeaurora.org Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, hemantk@codeaurora.org, sricharan@codeaurora.org, bjorn.andersson@linaro.org Subject: Re: [PATCH v2] bus: mhi: core: Add unique qrtr node id support In-Reply-To: References: <1614336169-31467-1-git-send-email-gokulsri@codeaurora.org> <1614336169-31467-2-git-send-email-gokulsri@codeaurora.org> <20210226145245.GB70936@thinkpad> Message-ID: <444e646b9781e24f9e2f95f7db85fcbd@codeaurora.org> X-Sender: gokulsri@codeaurora.org User-Agent: Roundcube Webmail/1.3.9 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi On 2021-02-26 23:01, Bhaumik Bhatt wrote: > On 2021-02-26 06:52 AM, Manivannan Sadhasivam wrote: >> On Fri, Feb 26, 2021 at 04:12:49PM +0530, Gokul Sriram Palanisamy >> wrote: >>> On platforms with two or more identical mhi >>> devices, qmi service will run with identical >>> qrtr-node-id. Because of this identical ID, >>> host qrtr-lookup cannot register more than one >>> qmi service with identical node ID. Ultimately, >>> only one qmi service will be avilable for the >>> underlying drivers to communicate with. >>> >>> On QCN9000, it implements a unique qrtr-node-id >>> and qmi instance ID using a unique instance ID >>> written to a debug register from host driver >>> soon after SBL is loaded. >>> >>> This change generates a unique instance ID from >>> PCIe domain number and bus number, writes to the >>> given debug register just after SBL is loaded so >>> that it is available for FW when the QMI service >>> is spawned. >>> >>> sample: >>> root@OpenWrt:/# qrtr-lookup >>> Service Version Instance Node Port >>> 15 1 0 8 1 Test service >>> 69 1 8 8 2 ATH10k WLAN firmware service >>> 15 1 0 24 1 Test service >>> 69 1 24 24 2 ATH10k WLAN firmware service >>> >>> Here 8 and 24 on column 3 (QMI Instance ID) >>> and 4 (QRTR Node ID) are the node IDs that >>> is unique per mhi device. >>> >>> Signed-off-by: Gokul Sriram Palanisamy >>> --- >>> drivers/bus/mhi/core/boot.c | 14 ++++++++++++++ >>> 1 file changed, 14 insertions(+) >>> >>> diff --git a/drivers/bus/mhi/core/boot.c >>> b/drivers/bus/mhi/core/boot.c >>> index c2546bf..5e5dad5 100644 >>> --- a/drivers/bus/mhi/core/boot.c >>> +++ b/drivers/bus/mhi/core/boot.c >>> @@ -16,8 +16,12 @@ >>> #include >>> #include >>> #include >>> +#include >>> #include "internal.h" >>> >>> +#define QRTR_INSTANCE_MASK 0x000000FF >>> +#define QRTR_INSTANCE_SHIFT 0 >>> + >>> /* Setup RDDM vector table for RDDM transfer and program RXVEC */ >>> void mhi_rddm_prepare(struct mhi_controller *mhi_cntrl, >>> struct image_info *img_info) >>> @@ -391,6 +395,9 @@ void mhi_fw_load_handler(struct mhi_controller >>> *mhi_cntrl) >>> const struct firmware *firmware = NULL; >>> struct image_info *image_info; >>> struct device *dev = &mhi_cntrl->mhi_dev->dev; >>> + struct pci_dev *pci_dev = to_pci_dev(mhi_cntrl->cntrl_dev); >>> + struct pci_bus *bus = pci_dev->bus; >>> + uint32_t instance; >>> const char *fw_name; >>> void *buf; >>> dma_addr_t dma_addr; >>> @@ -466,6 +473,13 @@ void mhi_fw_load_handler(struct mhi_controller >>> *mhi_cntrl) >>> return; >>> } >>> >>> + instance = ((pci_domain_nr(bus) & 0xF) << 4) | (bus->number & 0xF); >>> + instance &= QRTR_INSTANCE_MASK; >>> + >>> + mhi_write_reg_field(mhi_cntrl, mhi_cntrl->bhi, >>> + BHI_ERRDBG2, QRTR_INSTANCE_MASK, >>> + QRTR_INSTANCE_SHIFT, instance); >> >> You cannot not do this in MHI stack. Why can't you do this in the MHI >> controller >> specific to QCN9000? And btw, is QCN9000 supported in mainline? >> >> Thanks, >> Mani >> >>> + >>> write_lock_irq(&mhi_cntrl->pm_lock); >>> mhi_cntrl->dev_state = MHI_STATE_RESET; >>> write_unlock_irq(&mhi_cntrl->pm_lock); >>> -- >>> 2.7.4 >>> > > As others have stated, please refrain from adding protocol specific > code (such as PCIe) > in the MHI core driver. Please have this change in your controller. > > If there is access to BHI registers required prior to power up from > MHI core, it is not > exposed right now. We can talk about how you can achieve that, so you > can do this write > in your controller after mhi_prepare_for_power_up(). > > Thanks, > Bhaumik > --- > The Qualcomm Innovation Center, Inc. is a member of the Code Aurora > Forum, > a Linux Foundation Collaborative Project Thank you Jeffrey, Manivannan and Bhaumik. Adding Bjorn for his review and suggestions. Thanks, Gokul