From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752504AbeADJZe (ORCPT + 1 other); Thu, 4 Jan 2018 04:25:34 -0500 Received: from mail-wm0-f53.google.com ([74.125.82.53]:37750 "EHLO mail-wm0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752340AbeADJZ3 (ORCPT ); Thu, 4 Jan 2018 04:25:29 -0500 X-Google-Smtp-Source: ACJfBouP3ZLtQDmvlCRUOqEZzPOr5wAr4Xigr+UWibIHkH3Mr+KaqrustsFwdfmHDP//WNsPuYx0pQ== Subject: Re: [RESEND PATCH v2 14/15] ASoC: qcom: apq8096: Add db820c machine driver To: Stephen Boyd Cc: Andy Gross , Mark Brown , linux-arm-msm@vger.kernel.org, alsa-devel@alsa-project.org, David Brown , Rob Herring , Mark Rutland , Liam Girdwood , Patrick Lai , Banajit Goswami , Jaroslav Kysela , Takashi Iwai , linux-soc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org References: <20171214173402.19074-1-srinivas.kandagatla@linaro.org> <20171214173402.19074-15-srinivas.kandagatla@linaro.org> <4db358ab-3171-bb08-ca26-ec9bf282e8d4@linaro.org> <20180103194151.GA21040@codeaurora.org> From: Srinivas Kandagatla Message-ID: Date: Thu, 4 Jan 2018 09:25:24 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20180103194151.GA21040@codeaurora.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On 03/01/18 19:41, Stephen Boyd wrote: >>>> + ret = dma_coerce_mask_and_coherent(card->dev, DMA_BIT_MASK(32)); >>> Why do we need to do this? Can you add some sort of comment in the code >>> about why? >> Even though dsp supports 64 bit addresses, but the sid sits at >> offset of 32, which brings this restriction of supporting only 32 >> bit iova. >> > Doesn't the dsp have an iommu in place to make the address > translation from 64 to 32 bits transparent? I thought this was > what dma-ranges and iommu binding was for, but I'm not well > versed on all the details here. Thanks for reminding, dma-ranges would work too, I will give that a go in next version. --srini