From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0C71DC282CE for ; Tue, 4 Jun 2019 22:00:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D8F3F2075B for ; Tue, 4 Jun 2019 22:00:46 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="Z/qtMwfk" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726416AbfFDWAm (ORCPT ); Tue, 4 Jun 2019 18:00:42 -0400 Received: from mail-wm1-f66.google.com ([209.85.128.66]:40115 "EHLO mail-wm1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726179AbfFDWAm (ORCPT ); Tue, 4 Jun 2019 18:00:42 -0400 Received: by mail-wm1-f66.google.com with SMTP id v19so257976wmj.5; Tue, 04 Jun 2019 15:00:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=H1nfjWsjj7CcjHrqjJ43IW33X8D3A0ct0KZAGjNqblo=; b=Z/qtMwfk4lK6AmtTyPAY/E/vJB41YlpMPQa2clHBtlLVCruOt1rXc87nJh7BOdnK8V sWQxrsebfthQdJMq83HxY3ZjFNOsVdgBK3WK8VBGDxn2iRah5d2mU6OL3/kozF4Sihii JVXXMcExnPpFg2OyfIif53TvmgpcSidG5NL8n94Sp2PlYBymE8D0UwGu5/qBA0L9ZDMV oksKaEXaq434Vt3O8QabQr8JC6F+fnANhK9spSBZI7sClHHsI9DkfwXHk+qHdFgKGIxs fNK14K/EJFwDHDwwMm7bu5uvMPj0PyHgf2+xjN0IIyBcay32zJhtK1YEK2vOSQOhELjb f2Og== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=H1nfjWsjj7CcjHrqjJ43IW33X8D3A0ct0KZAGjNqblo=; b=rTr7a1Pr21ccBqDjqZDCiXmatr7fk4nh4wJPVRyIZhSanS5PKUyLhxZHMow2CcAV4f 2ddh2OMlnTn9YFlWPfJS49zvTU+I7pPK9cte1zRoR8S5f+E5asg9hj6Gw3XZqKZmbOaz NQQ7MBosjAUqz+3YsC6KGMfkFrR1/ZXnqUpSYQyuxI/Xlr70tKz3SUioPuOVo3JMAua2 I89CHS2A4VFN3GZHs1JyZLcLVzP4n5eYFSRgJdv2yyUw4Td0awhaeiDnZnF90iMa+viX L1nANicW6HHVVxnQThIQhnnGaKRx3BRGnbbgAz2Fdsee/nUjaejNQGPZOLg0hims++E3 u8OQ== X-Gm-Message-State: APjAAAVvVCzdnd3xomV2aQ0DL+e6kwqHDLtsK1nrjC2jUFGh/3QbeCCt Ba/7/1ytaxnAX23QnR7SKKP70NTqs1TPTlRMOs4= X-Google-Smtp-Source: APXvYqyX30ywLnMQ8nvn1uQnwLslcG5XWRzwmgbAtETaF0akz0jnaQJra30R0ULNfpY4zC+FNuOmIrYzVF3kRhNf9ag= X-Received: by 2002:a1c:eb16:: with SMTP id j22mr7126678wmh.56.1559685639703; Tue, 04 Jun 2019 15:00:39 -0700 (PDT) MIME-Version: 1.0 References: <20190604072001.9288-1-bjorn.andersson@linaro.org> In-Reply-To: <20190604072001.9288-1-bjorn.andersson@linaro.org> From: John Stultz Date: Tue, 4 Jun 2019 15:00:27 -0700 Message-ID: Subject: Re: [PATCH 0/3] (Qualcomm) UFS device reset support To: Bjorn Andersson Cc: 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 Content-Type: text/plain; charset="UTF-8" Sender: linux-arm-msm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org 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 thanks -john