Received: by 10.213.65.68 with SMTP id h4csp1925938imn; Thu, 5 Apr 2018 06:13:53 -0700 (PDT) X-Google-Smtp-Source: AIpwx49jffKanRavXQ1ChO4N6YyoIAujUwU3fdsunN69tmPAv08z6zRhGyF80b5VBbSa9XqBcmxa X-Received: by 10.98.133.139 with SMTP id m11mr17065391pfk.49.1522934033060; Thu, 05 Apr 2018 06:13:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522934033; cv=none; d=google.com; s=arc-20160816; b=Di5LZgkFdNiPblQFthJxjdvI8DKLKci8nAGQK4yPwDfX6SYNo2xi1QC/h0HU0gZU6T pfIuBccaA41ZMsrRJoGiiqA/oMlJAFdDIEwmBzRMQ2zXRYHz6onFob6Q0E2dnZTcSV+0 gZZEwAm0BRfL4kmWIjTNOAuPJM+pDpSgA6PCZTV/lwW65bHaPQJvMZhubsAmAWZdTANb PkBHgbQukdyyW3X6Tg/CIKfB7msXk99DuTKU46cVdCZFVhnth6jOBGnhLATQZCeR4PlB iUSG951czxZlAZaoNoiU1pMg9bcKonpAS/T93bMqIM3Y9UGOvUFnG9odN5AuWyFR6lGg FYnQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:message-id :in-reply-to:date:references:subject:cc:to:from:dmarc-filter :dkim-signature:dkim-signature:arc-authentication-results; bh=DWEwJ8NO7U2Xn25FBbR1r89YkGPgRUTZMSsC4S3a7VA=; b=vx/0IbJEJRmM7T+X7+XrZlMM3LLA+Ts0J+3XcsTsZsH+GtKzYadEoMMMWMSL8n13KC 5tajJ0sK0C/fd+s4t46BJ6hfYduecWlDbsaPoKEa3pQUIIGD5jT3DlX210i+xVpo+vE8 HvoO8MEVp0F65vnz3cV8HnyL1W1iLxqYfmqZZ2+g0RDVuT383NAsBv1JmxYIcY4vaDnI oxVoZpTLpeLy7GR0+DiqvMdPe3q53OVM2Xp8FyBdUATojPaUE+EA+seWY/7KhVgWZ99o /wmpPV4+qwRXrHGabh2qv5K00Fm8RoU4SKsAWrSAT2QuOglUR02LOfzXw9ItwlKuaYwC gHYg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=PbnR4MKo; dkim=pass header.i=@codeaurora.org header.s=default header.b=n28kgLMw; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b89-v6si8225267plb.262.2018.04.05.06.13.39; Thu, 05 Apr 2018 06:13:53 -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=@codeaurora.org header.s=default header.b=PbnR4MKo; dkim=pass header.i=@codeaurora.org header.s=default header.b=n28kgLMw; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751591AbeDENLL (ORCPT + 99 others); Thu, 5 Apr 2018 09:11:11 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:42104 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751249AbeDENLI (ORCPT ); Thu, 5 Apr 2018 09:11:08 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 39CFE60F92; Thu, 5 Apr 2018 13:11:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1522933868; bh=eja+BVtIwkZy87bmnNfj0UdxRtL2WdbC3RaP+kf/lc0=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=PbnR4MKoE7rWZ4BYIi1JMMCEj7eRec201H+yAFpX0WGpsB0PAqEwrU/mggHEI9NS6 rf+fK9yu8xaWFo/BFnw3ITr8AV8r1y0VIBr1V9NWTC4gmPGEbyMXdKEalehgEOUrJ6 Cfk53iznEcbQC5I0kJITmremY0byrcS83Irbaaos= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from potku.adurom.net (88-114-240-52.elisa-laajakaista.fi [88.114.240.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: kvalo@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id A729160274; Thu, 5 Apr 2018 13:11:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1522933864; bh=eja+BVtIwkZy87bmnNfj0UdxRtL2WdbC3RaP+kf/lc0=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=n28kgLMw7Ysbu291rFbzCzu0W2f8e3df2xf2aVgSrZ2wphWo0VmFFRriPuWxhpPh5 1pN2XGOhE+eE2ZfBE1cwGOT9CyVjxjrEcsW37KQ9n1wQWWgALD2T04FBHS8xfQRClw 1pSyTcVtOthXtcGMhQspWMbZA5gJFXtPu6Rg8Lec= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org A729160274 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=kvalo@codeaurora.org From: Kalle Valo To: Ulf Hansson Cc: Arend van Spriel , 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 Subject: Re: [PATCH net-next v2 2/2] dt: bindings: add new dt entries for brcmfmac 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> Date: Thu, 05 Apr 2018 16:10:58 +0300 In-Reply-To: (Ulf Hansson's message of "Thu, 22 Mar 2018 11:29:53 +0100") Message-ID: <87lge1er31.fsf@kamboji.qca.qualcomm.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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/ -- Kalle Valo