Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp6335353ybi; Tue, 4 Jun 2019 23:03:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqwYgzB33+t3j3tYIJdJBRE09EHZyEY3RGTi9K1W/+vdy4GkE6rG/6ZjAQ2jh4nc99ZxCHJ5 X-Received: by 2002:a65:638a:: with SMTP id h10mr2224507pgv.64.1559714580228; Tue, 04 Jun 2019 23:03:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559714580; cv=none; d=google.com; s=arc-20160816; b=O6Vmgiyfu06sfXvx3PIlZKpHSxzysbHOKZy5oNau44FDRDdt/NvYsygYoK5Bo5G/gZ gd7M5bL98pxGQuBS6hcJYDxW5/W7mnL8QGl88keZlbpNG2tvOdrs/ik6WJ8jOYtY82MN g54RTwka4ps5MGERZa7OQqdjp26TSHuBI9oFILcu/qWsYc//mT6ByRkzoRnES6/PLOGj XegX4KcDxzglS+CkV6vmjQmST+NgUdzndI7JsIeUqbZj0HbYDVVzHfeB9hW1+1i+M25s 6EJaPx0BUbzvULfGY7gqqRO/oUGGgzTqRmKqjUMcUlqsgyEc7P4Jtmb/Ic883EhhJurj VTZQ== 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:dkim-signature; bh=XhgXHLObV5Vbqo0Ol1dr/K9C6PfbnIr6P+CU31xn0uk=; b=0EYP6fbXIrxaCQNMJUSvgj4uX8YldJbtM7YsbzuLujZ1KrlksJrhS9K1kDQlJMWra+ JIk3Xj/2xxPR/xmOmL+0x63YfZKG0Y1tchXCsVnIbO4aaKIDrLk+ex0EyU9zIa7u5uLQ 2sY5lQDutNtP7m4UoNrlfxkHCrHGi7M0Dukd1MybGwuOcd8DeAuvebLF05R34nSw41Vf dJpsAb0PVew4uN3RfahtB6ARwmvBKAr/YB/HU46ydhZxrsTN0sDY/zkwJ8NY+92fNou9 4qYWHICPy+M+JiSenfvOZr8rmOFdYqfVvnUH1IdmHqphsp2Rq+TM27d76MFT96rEC2e0 CGcA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=JMDtt3o4; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c3si24654034pgi.358.2019.06.04.23.02.42; Tue, 04 Jun 2019 23:03:00 -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; dkim=pass header.i=@linaro.org header.s=google header.b=JMDtt3o4; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726682AbfFEGBL (ORCPT + 99 others); Wed, 5 Jun 2019 02:01:11 -0400 Received: from mail-pg1-f194.google.com ([209.85.215.194]:40047 "EHLO mail-pg1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726648AbfFEGBK (ORCPT ); Wed, 5 Jun 2019 02:01:10 -0400 Received: by mail-pg1-f194.google.com with SMTP id d30so11779386pgm.7 for ; Tue, 04 Jun 2019 23:01:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=XhgXHLObV5Vbqo0Ol1dr/K9C6PfbnIr6P+CU31xn0uk=; b=JMDtt3o4OpRyNKqkIsA2AAl8veHAMN2+KlqcyzaxHwpNI6+UJ79YrJx/oC0KuKGwN4 uLEguOKwpu/0TSXjxpVrV9ohcTpmW1vkIcHcIVFgf/wP1efqPouTguYWm4hBw/s9V3XE aw5GVUVx5BjtFgTryP1pejwqui5+CG9DuIUr2Ev5/THCjVKRvJBSeEgLJSQ/KuXmabKK 8imeg+KY2S7LywceHrI7pk9u1toSQeENkXq3lHGZjPFcoLpEOYr1s0TZGtu8CjO/sgnV mzVHrj+TjeVEHvdU1/i3c4QDrjusE5znnwztyeYOiLl5Loaz8upXQeqBR5ZaH4KbdnXP iplA== 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=XhgXHLObV5Vbqo0Ol1dr/K9C6PfbnIr6P+CU31xn0uk=; b=tqfmwrO4s4chrHgB553UK0nuQ9kZkHeM4ecn7NhRrcVD0V5sfBPcszsElZTn7lMV4i 7SIdPbi1Jov/0BVfviKMwFJitMYy+8apjzlkVLkmexb+/3ejL8XClzCMRbUAGYFy9Pd2 lauR7WH3thtgfrzdSYPvj6y3YTRdHweK24xxApc4V7W69OgCQP2WKjRaz9jw7O8f32/5 LJxROIvIJlXHDAogtHcHhOqpoGVxmyVsFWTmB3tqpYqaCNAdU5riXfl3mpWuYKQrSFJC osQT9GBSLud6JMywJ67sp4HBMFSGhnrtHBDvl5rFb95t03x3OjqfYlvCXCgRrvL+jzkc WIBQ== X-Gm-Message-State: APjAAAVg2ThNkoVNpvlP/UcEkWtgdTEj61b83ikmgzhj9VEwnvSVIERY R3NlbhanCu3VIblWrT3YeWF95w== X-Received: by 2002:a17:90a:2ec9:: with SMTP id h9mr43058272pjs.130.1559714469980; Tue, 04 Jun 2019 23:01:09 -0700 (PDT) Received: from tuxbook-pro (104-188-17-28.lightspeed.sndgca.sbcglobal.net. [104.188.17.28]) by smtp.gmail.com with ESMTPSA id q22sm2332383pff.63.2019.06.04.23.01.08 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 04 Jun 2019 23:01:09 -0700 (PDT) Date: Tue, 4 Jun 2019 23:01:54 -0700 From: Bjorn Andersson To: Avri Altman Cc: John Stultz , Andy Gross , Linus Walleij , Rob Herring , Mark Rutland , Pedro Sousa , "James E.J. Bottomley" , "Martin K. Petersen" , "linux-arm-msm@vger.kernel.org" , "linux-gpio@vger.kernel.org" , "devicetree@vger.kernel.org" , Linux Kernel Mailing List , "linux-scsi@vger.kernel.org" Subject: Re: [PATCH 0/3] (Qualcomm) UFS device reset support Message-ID: <20190605060154.GJ22737@tuxbook-pro> References: <20190604072001.9288-1-bjorn.andersson@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 04 Jun 22:50 PDT 2019, Avri Altman wrote: > Hi, > > > > > On Tue, Jun 4, 2019 at 12:22 AM Bjorn Andersson > > wrote: > > > > > > This series exposes the ufs_reset line as a gpio, adds support for ufshcd to > > > acquire and toggle this and then adds this to SDM845 MTP. > > > > > > Bjorn Andersson (3): > > > pinctrl: qcom: sdm845: Expose ufs_reset as gpio > > > scsi: ufs: Allow resetting the UFS device > > > arm64: dts: qcom: sdm845-mtp: Specify UFS device-reset GPIO > > > > Adding similar change as in sdm845-mtp to the not yet upstream > > blueline dts, I validated this allows my micron UFS pixel3 to boot. > > > > Tested-by: John Stultz > Maybe ufs_hba_variant_ops would be the proper place to add this? > Are you saying that these memories only need a reset when they are paired with the Qualcomm host controller? The way it's implemented it here is that the device-reset GPIO is optional and only if you specify it we'll toggle the reset. So if your board design has a UFS memory that requires a reset pulse during initialization you specify this, regardless of which vendor your SoC comes from. Regards, Bjorn