Received: by 10.213.65.68 with SMTP id h4csp2288318imn; Thu, 5 Apr 2018 12:14:36 -0700 (PDT) X-Google-Smtp-Source: AIpwx48VH50qNZ6tNPtktHsyfCJUuCDXcLAjHYQr5PX0ZgBmEOkinT3dIodavLNGd4WOr47S93n+ X-Received: by 10.99.142.201 with SMTP id k192mr15595998pge.278.1522955676055; Thu, 05 Apr 2018 12:14:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522955675; cv=none; d=google.com; s=arc-20160816; b=pnV9w+SigmW9RqWrznJHgCYkpx1Fp1wDeR+zi3UYVDBDlY9gxpqjZfCZcl/jXdZH76 2iitNir3EiAqlKFLV3a3uxbwV6SdIYIbXDdHKhdmWJHdnWISeKDKzdV6gLE4ApHEACOe ZKpQyqpTrmaqWwRVd2xAEb+0F9cNhMc59T6T86PfMSU40GMJE+eAb5A9luB3ADnxIE27 Q4DgLuVAgjv1L/DiaueOLetMQjzYD4JzGLi/fHWdWLicaeqPJ0NVQOmkkx6FVnntmtGx kRiaeWYCV54gyDlemL2ZbRnZ3pRIEjeeeB3yW/XGYZ2qK26kpifGGrFWHR+LfKoua3I+ YVdg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject:dkim-signature:arc-authentication-results; bh=d/SiKebTT/50ojN9efpOGqKTAE+nQtO43X/dSCjeON8=; b=kQzm0aValyIqxwCCCi/Cmaza+kEEgwpExIuG4e234ZA56U2k1Rh9Fq9MBXIdB7qBTr NH1MaLRZKWTXK3lWRpk0mvHXGyifa+wFO17LUdhrDekupID2/GELWD3wHeaqE4v9UooF vltCMzt9HiCCiNtuoeGYlmBj5N7vsUuqVEWlYqMCQmn71Z+zeYL/mOj1r+09d2R4JBK6 LLcLbnk9n+5hMRWL4MQSicuUROUvB2S5IFcNOUNwZVe99ksCEBLG0+/wdWv3amoxY+1Q iohFkjINz151fO0AFmyKu3TZ8w6mGi/GwdtsBv7KuQMrE8qQBU0fZ5kqXt+el31lLa7S xWiA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@broadcom.com header.s=google header.b=LEtakEVW; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=broadcom.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u21si6501941pfl.143.2018.04.05.12.14.21; Thu, 05 Apr 2018 12:14:35 -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=@broadcom.com header.s=google header.b=LEtakEVW; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=broadcom.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752830AbeDETL6 (ORCPT + 99 others); Thu, 5 Apr 2018 15:11:58 -0400 Received: from mail-wm0-f66.google.com ([74.125.82.66]:33665 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752729AbeDETLz (ORCPT ); Thu, 5 Apr 2018 15:11:55 -0400 Received: by mail-wm0-f66.google.com with SMTP id o23so4722101wmf.0 for ; Thu, 05 Apr 2018 12:11:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=d/SiKebTT/50ojN9efpOGqKTAE+nQtO43X/dSCjeON8=; b=LEtakEVWMHLWP4oVBzI0XMaMGhgqDcT9a5VPMPghEEU2P5HqID1kSFtd7Cyhza3Fz4 Y3/bINDBnuztYweFdJOmtu7j7fEBFhyXeElHRdfhofmhxKwB11ub8BKv1+KAZd7uAllc v/pSHdQer0oFjSYB/bhYsODBQ6Dr4wWx3b53I= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=d/SiKebTT/50ojN9efpOGqKTAE+nQtO43X/dSCjeON8=; b=lDXuCpkQ8xl+9/Z5N5gpKNX24xvO4i3D6Ih8dmxDp2xsL23CyfsF+IMq2t+FC1RS7i buXO+A6iL6VyhLZp3wZm54Z0ZZgjj2+XTrPx1q3py9PIRv8ilgPdy171UkV9lxb/1pom V1ypvvvwb5G8cpl4mDWq3F24zFLZ5CQ0bGsev3SsBXajCR1XuF8kjyEXf0veLG5zv9se DCecf+1Vi3EHDi3MkZAcNn5/qhcvh6EsPd55rRpLy3iI2+V2oKlcS3CzKlfMck72aMw2 TCTof/MvzxqB9k6lUWZsH0O63Y8bx11hLY4xWcDOKZKQAJIEgp3f5mKpKro9mZcQNUXM SV6A== X-Gm-Message-State: ALQs6tC+Zmxxh6aXQcjJjn/4OA6id0icMpKH2CHu4aEvnK7y7eULnMQD aPPcwWsDWUqxXt3LlyNSYwkLXw== X-Received: by 10.80.179.230 with SMTP id t35mr4089729edd.173.1522955514036; Thu, 05 Apr 2018 12:11:54 -0700 (PDT) Received: from [192.168.178.129] (f140230.upc-f.chello.nl. [80.56.140.230]) by smtp.gmail.com with ESMTPSA id y4sm5376510edi.4.2018.04.05.12.11.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Apr 2018 12:11:53 -0700 (PDT) Subject: Re: [PATCH net-next v2 2/2] dt: bindings: add new dt entries for brcmfmac To: Kalle Valo , Ulf Hansson References: <20180319014032.9394-1-alexey.roslyakov@gmail.com> <20180319014032.9394-3-alexey.roslyakov@gmail.com> <5AAF838D.2030105@broadcom.com> <817418fd-6446-57ea-b03d-383b4df9a979@gmail.com> <5AB044C0.9060701@broadcom.com> <87po3zxe9n.fsf@kamboji.qca.qualcomm.com> <87lge1er31.fsf@kamboji.qca.qualcomm.com> Cc: Florian Fainelli , Alexey Roslyakov , Andrew Lunn , Rob Herring , Mark Rutland , Franky Lin , Hante Meuleman , Chi-Hsien Lin , Wright Feng , netdev@vger.kernel.org, linux-wireless@vger.kernel.org, devicetree@vger.kernel.org, Linux Kernel Mailing List , brcm80211-dev-list.pdl@broadcom.com, brcm80211-dev-list@cypress.com From: Arend van Spriel Message-ID: <5AC674F8.7080100@broadcom.com> Date: Thu, 5 Apr 2018 21:11:52 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <87lge1er31.fsf@kamboji.qca.qualcomm.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/5/2018 3:10 PM, Kalle Valo wrote: > Ulf Hansson writes: > >> On 20 March 2018 at 10:55, Kalle Valo wrote: >>> Arend van Spriel writes: >>> >>>>>> If I get it right, you mean something like this: >>>>>> >>>>>> mmc3: mmc@1c12000 { >>>>>> ... >>>>>> broken-sg-support; >>>>>> sd-head-align = 4; >>>>>> sd-sgentry-align = 512; >>>>>> >>>>>> brcmf: wifi@1 { >>>>>> ... >>>>>> }; >>>>>> }; >>>>>> >>>>>> Where dt: bindings documentation for these entries should reside? >>>>>> In generic MMC bindings? Well, this is the very special case and >>>>>> mmc-linux maintainer will unlikely to accept these changes. >>>>>> Also, extra kernel code modification might be required. It could make >>>>>> quite trivial change much more complex. >>>>> >>>>> If the MMC maintainers are not copied on this patch series, it will >>>>> likely be hard for them to identify this patch series and chime in... >>>> >>>> The main question is whether this is indeed a "very special case" as >>>> Alexey claims it to be or that it is likely to be applicable to other >>>> device and host combinations as you are suggesting. >>>> >>>> If these properties are imposed by the host or host controller it >>>> would make sense to have these in the mmc bindings. >>> >>> BTW, last year we were discussing something similar (I mean related to >>> alignment requirements) with ath10k SDIO patches and at the time the >>> patch submitter was proposing to have a bounce buffer in ath10k to >>> workaround that. I don't remember the details anymore, they are on the >>> ath10k mailing list archive if anyone is curious to know, but I would >>> not be surprised if they are similar as here. So there might be a need >>> to solve this in a generic way (but not sure of course as I haven't >>> checked the details). >> >> I re-call something about these as well, here are the patches. Perhaps >> I should pick some of them up... >> >> https://patchwork.kernel.org/patch/10123137/ >> https://patchwork.kernel.org/patch/10123139/ >> https://patchwork.kernel.org/patch/10123141/ >> https://patchwork.kernel.org/patch/10123143/ > > Actually I was talking about a different patch, found it now: > > ath10k_sdio: DMA bounce buffers for read write > > https://patchwork.kernel.org/patch/9979543/ The patches Uffe mentions are related to this. In brcmfmac we simply implemented functionality to create a scatter list and send it through the MMC stack using SDIO CMD53. It is in the creation of the scatter list that these alignment properties are needed. Moving the whole functionality to the MMC stack will also move those properties into their right context, ie. SDIO host controller. Our broker_sg_support property is basically doing the bounce buffer thing if I understand it correctly. Regards, Arend