Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp905021imm; Wed, 11 Jul 2018 13:07:44 -0700 (PDT) X-Google-Smtp-Source: AAOMgpc3z+cQV13buy6PrsStzMuOaFjHZ+HEZAenTAYKUyfhrF3TrY5VXosWc3yLSG10n3nw2a/N X-Received: by 2002:a65:4841:: with SMTP id i1-v6mr56733pgs.75.1531339664251; Wed, 11 Jul 2018 13:07:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531339664; cv=none; d=google.com; s=arc-20160816; b=JiBsbUeYmCSwdI1yosHrI1VLmO8lP4DOWwdJxJg6g2QSybJRHt3VWW6YcLuttmxrCI 7o1uKcB3/+J9LqdaZF7k2zRZStUI6/3x8Flvz6inwjzx7GLFyuFLla3iFLpKfySwq86m PyrNSsLUWcNyoX4jziLwQNBsPkk2P4VZhQWbXISE9fbMZoOHLSywFBNB8KFBN0kgy9lz ckK93qx4y7IZ1X+qGvV6yGsHl6PNX7ITFQx1Fg5N3pobrxcMNkD+jJ+ZbaOs1gqZfgSZ M5o6yPHnuZ5HBXYoXZPi6QPQJcoAFfO3no4+OXNggjU+V2IOEFON1cI8jSZVcI94MAfW ehGg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=8n6dHyy8SY6Z4H4meT5y6KRmvJHCP8De9mLiq2KOp0I=; b=G/3pW95ZL/Z7fTprcZDxOYXV/79tBsPkU1pKL2Bf0+aeyjgo4YRsDDd8X/AYLLEbu9 InoJVRj3HW357TxufBTdTO/elPoTYy6UoORp6atd9a7wyT1xQPg9j+4bUPgAMfd269xG 4DksuAWpgwNgpRenGbny3UVzHXjPSHrgjYP9VHJOKviji/8RNYhrQP+pvYRQoFHLdoyv 3NI0i8OJkIpt60tCGiIORvhRrsBIPWmQpRfrm53qCLCYJ1qekOrptMMAzaGzr6CIWPJT eWfebl30nyxdWuAuPjT8s4XeA0/LuIPBx9Pj8hYK2nDlL07Ti6U5e3pVdmGuHtA2KT4H eMEw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u76-v6si22762379pfj.58.2018.07.11.13.07.28; Wed, 11 Jul 2018 13:07:44 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388543AbeGKTmP (ORCPT + 99 others); Wed, 11 Jul 2018 15:42:15 -0400 Received: from mail-oi0-f68.google.com ([209.85.218.68]:36403 "EHLO mail-oi0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726783AbeGKTmP (ORCPT ); Wed, 11 Jul 2018 15:42:15 -0400 Received: by mail-oi0-f68.google.com with SMTP id r16-v6so51431097oie.3; Wed, 11 Jul 2018 12:36:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=8n6dHyy8SY6Z4H4meT5y6KRmvJHCP8De9mLiq2KOp0I=; b=ISwCUm7Qnal4xuZlpA3J75zwKHejIzNCfAIg00zffdppp/mjBl9zF3h5iWDAN3T5d4 SkSs5GoQYXjFp/bA63Gq1+yzl7WcjRZFNHbPMn7P0IqIlmXhaRR/U49gRqbjCH4q6aW3 XxYMW401a/uximhbw2/6gIBz+psLg0VlLr2GFjiztlbHx7Dhwr/MvTrzixPyd0OljFc3 O8cOFhDp/bCNFBZli2wIY2RAvNw1FYxN//oOSrBToHg7NxqXpdwMsI6I4Pes3aM0WuwJ 8akgxgvBFZgmzp0kaFUr1SI4KX8tUZFispQNOgqzy9mzwJPxyvpKFMr3cmV41qW5Go3s +oDg== X-Gm-Message-State: AOUpUlEMnAqdkOkMwigU6gOkyi3PMPGsqGz0x+mVSD9081fSR8VrneOo t6WOrDhtRPKiJjJKEm7PdA== X-Received: by 2002:aca:7c5:: with SMTP id 188-v6mr2797oih.58.1531337786915; Wed, 11 Jul 2018 12:36:26 -0700 (PDT) Received: from localhost (24-223-123-72.static.usa-companies.net. [24.223.123.72]) by smtp.gmail.com with ESMTPSA id 1-v6sm6126976oir.19.2018.07.11.12.36.25 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 11 Jul 2018 12:36:26 -0700 (PDT) Date: Wed, 11 Jul 2018 13:36:25 -0600 From: Rob Herring To: Sujeev Dias Cc: Greg Kroah-Hartman , Arnd Bergmann , linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, Tony Truong , Siddartha Mohanadoss Subject: Re: [PATCH v2 6/7] mhi_bus: controller: MHI support for QCOM modems Message-ID: <20180711193625.GC8659@rob-hp-laptop> References: <1524795811-21399-1-git-send-email-sdias@codeaurora.org> <1531166894-30984-1-git-send-email-sdias@codeaurora.org> <1531166894-30984-7-git-send-email-sdias@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1531166894-30984-7-git-send-email-sdias@codeaurora.org> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 09, 2018 at 01:08:13PM -0700, Sujeev Dias wrote: > QCOM PCIe based modems uses MHI as the communication protocol. > MHI control driver is the bus master for such modems. As the bus > master driver, it oversees power management operations > such as suspend, resume, powering on and off the device. > > Signed-off-by: Sujeev Dias > Reviewed-by: Tony Truong > Signed-off-by: Siddartha Mohanadoss > --- > Documentation/devicetree/bindings/bus/mhi_qcom.txt | 58 +++ And this one in it's own patch. > arch/arm64/configs/defconfig | 1 + > drivers/bus/Kconfig | 1 + > drivers/bus/mhi/Makefile | 1 + > drivers/bus/mhi/controllers/Kconfig | 13 + > drivers/bus/mhi/controllers/Makefile | 1 + > drivers/bus/mhi/controllers/mhi_qcom.c | 461 +++++++++++++++++++++ > drivers/bus/mhi/controllers/mhi_qcom.h | 67 +++ > 8 files changed, 603 insertions(+) > create mode 100644 Documentation/devicetree/bindings/bus/mhi_qcom.txt > create mode 100644 drivers/bus/mhi/controllers/Kconfig > create mode 100644 drivers/bus/mhi/controllers/Makefile > create mode 100644 drivers/bus/mhi/controllers/mhi_qcom.c > create mode 100644 drivers/bus/mhi/controllers/mhi_qcom.h > > diff --git a/Documentation/devicetree/bindings/bus/mhi_qcom.txt b/Documentation/devicetree/bindings/bus/mhi_qcom.txt > new file mode 100644 > index 0000000..0a48a50 > --- /dev/null > +++ b/Documentation/devicetree/bindings/bus/mhi_qcom.txt > @@ -0,0 +1,58 @@ > +Qualcomm Technologies Inc MHI Bus controller > + > +MHI control driver enables clients to communicate with external mode > +using MHI protocol. > + > +============== > +Node Structure > +============== > + > +Main node properties: > + > +- reg > + Usage: required > + Value type: Array (5-cell PCI resource) of > + Definition: First cell is devfn, which is determined by pci bus topology. > + Assign the other cells 0 since they are not used. > + > +- qcom,smmu-cfg This should probably be part of the SMMU binding? > + Usage: required > + Value type: > + Definition: Required SMMU configuration bitmask for PCIe bus. > + BIT mask: > + BIT(0) : Attach address mapping to endpoint device > + BIT(1) : Set attribute S1_BYPASS > + BIT(2) : Set attribute FAST > + BIT(3) : Set attribute ATOMIC > + BIT(4) : Set attribute FORCE_COHERENT > + > +- qcom,addr-win > + Usage: required if SMMU S1 translation is enabled > + Value type: Array of > + Definition: Pair of values describing iova start and stop address > + > +- MHI bus settings > + Usage: required > + Values: as defined by mhi.txt > + Definition: Per definition of devicetree/bindings/bus/mhi.txt, define device > + specific MHI configuration parameters. > + > +======== > +Example: > +======== > + > +/* pcie domain (root complex) modem connected to */ > +&pcie1 { > + /* pcie bus modem connected to */ > + pci,bus@1 { > + reg = <0 0 0 0 0>; > + > + qcom,mhi { > + reg = <0 0 0 0 0>; 2 levels of PCI addresses doesn't look right, but I can't really tell in your example. The addresses don't look valid. > + qcom,smmu-cfg = <0x3d>; > + qcom,addr-win = <0x0 0x20000000 0x0 0x3fffffff>; > + > + > + }; > + }; > +};