Received: by 2002:a05:6a10:2785:0:0:0:0 with SMTP id ia5csp2554995pxb; Mon, 11 Jan 2021 12:49:02 -0800 (PST) X-Google-Smtp-Source: ABdhPJyU3QfUvjaGaepgGH+bwC0JxN6mIVXE7mLCHURfYqYWyzM/nn5SNDJP2iAov3n9hK+usN2F X-Received: by 2002:a17:907:a96:: with SMTP id by22mr819919ejc.171.1610398141860; Mon, 11 Jan 2021 12:49:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610398141; cv=none; d=google.com; s=arc-20160816; b=utp2ujYS57cJg6uYEs/QzKNw6eH1+E++0Zhis2EjagCr6i99/cKkwgqSdcU+3T0MFk X/W0Gm0Ecgm465CzyFd9o2g4Xw4yxUtpBCd/SSA9c8GNRpzr7KpXBirnc9Sjy8EaYn84 w6i81UXB5RMe6Td46rpGbb2rKEtgT7OrtwPrJk+BcD9xTvvUNNuiu/Hin3F5E8aqTGPX fQRMoACUcDu+nFsVbq06QsO50QoXXPhBu9QJoseb3CtktVlfBLu9/FAeswh2+YlCwjPC XMosIVfOq5a0wS4WqgMa763Lm08Srs/VkIfg1HeyejskcJeadZE0wxGPJqCCeTwLShw4 XcrA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=8c6CHut8/gJsFnDeRtVVl0pJsHR7OirWPJ/4UQakPRk=; b=aL50fDluC4Shbr51BTTQ5l8gps4gUupUulT3L270ddlyz7+5HKR27M9/g+oEya3WrF 9hAd+lhBn6pm1ZL49kYK08eUyLo5xA4Eia2qu38mydsFfodIJ5N8JiPiNr9zh9fz4jcc rtcU1RwGzfogeXO2Ind3g9XaskPNE/KGIc03gM2RalrDGFoEtUeG8mAKUNg8ZqKs7aw3 2WB1Q7rJFKhOmr1DKScEnaZTvxkAS8wyuI+q23K5/rAPRgJTH5OBIDF9emG9/i4bM3PL Xj2DY5V78AQ+5L1jTAOBLp3I5VVU9T6k05PtCB5L8IbT9GkuFLkRrdyPhHoT2uZ4im6J S+Ag== ARC-Authentication-Results: i=1; mx.google.com; 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 d19si343614eds.173.2021.01.11.12.48.38; Mon, 11 Jan 2021 12:49:01 -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; 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 S2391280AbhAKUpz (ORCPT + 99 others); Mon, 11 Jan 2021 15:45:55 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34136 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2391209AbhAKUpw (ORCPT ); Mon, 11 Jan 2021 15:45:52 -0500 Received: from relay05.th.seeweb.it (relay05.th.seeweb.it [IPv6:2001:4b7a:2000:18::166]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3766CC06179F; Mon, 11 Jan 2021 12:45:12 -0800 (PST) Received: from [192.168.1.101] (abaf53.neoplus.adsl.tpnet.pl [83.6.169.53]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by m-r2.th.seeweb.it (Postfix) with ESMTPSA id 670233E80D; Mon, 11 Jan 2021 21:45:09 +0100 (CET) Subject: Re: [PATCH 7/7] arm64: dts: qcom: sdm845: enable dma for spi To: Vinod Koul Cc: Bjorn Andersson , Mark Brown , Wolfram Sang , linux-arm-msm@vger.kernel.org, Andy Gross , Matthias Kaehlcke , Douglas Anderson , Sumit Semwal , Amit Pundir , linux-spi@vger.kernel.org, linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org References: <20210111151651.1616813-1-vkoul@kernel.org> <20210111151651.1616813-8-vkoul@kernel.org> <6cc90f43-f2c8-85f7-3d1c-f96468aab196@somainline.org> <20210111174649.GC2771@vkoul-mobl> From: Konrad Dybcio Message-ID: <12aae061-3a7e-883f-9b82-0b608ccf9441@somainline.org> Date: Mon, 11 Jan 2021 21:45:03 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <20210111174649.GC2771@vkoul-mobl> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > If it is working without GPI enabled, it would work.. GPI for QUP is > something that requires firmware and would have to be enabled by > firmware I think with the new code of yours: mas->tx = dma_request_slave_channel(mas->dev, "tx"); + if (IS_ERR_OR_NULL(mas->tx)) { + dev_err(mas->dev, "Failed to get tx DMA ch %ld", PTR_ERR(mas->tx)); ret = PTR_ERR(mas->tx); + goto out_pm; it *may* fail to probe with the channels assigned in the "dmas=" property but with the engine having "status=disabled", but as I don't have any hardware to test that driver on, please confirm whether my concerns are right.. > Since DMA support may not be available on certain targets (firmware > support), so enabling per board would make sense Oh really, are there SDM845 boards shipping with GPI DMA *disabled to all peripherals*? Konrad