Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp3340151ybd; Tue, 25 Jun 2019 00:33:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqzB5il/42bqYgCqFNIGPnmGgOmRJHBf/mDIoXLkgOBOC+wDJQ7rxPyuT5G0p5Dfjhn+QDid X-Received: by 2002:a17:90a:2305:: with SMTP id f5mr31647167pje.128.1561448016766; Tue, 25 Jun 2019 00:33:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561448016; cv=none; d=google.com; s=arc-20160816; b=HhWFogasJjRLUA8GtSyeEs+v1mjMbXORN4WD5kAVWh106c6LI333BhtAHhjwEnjudF NFnIhoEIiV8mWzlXup/Jl6CTCR/kiY69SgzXVHzlb0MbXAwcR3lTlPWHYLJ/AyogX7gB lDMpkCXe7yJNWYsDq67HyP4RuXEfuLDvmdyBYZQ0a92liOQ8ixJn20nmxwMZEo3EpCXy YZeaej1pPHUDoiMabLmesDN5rPyGbaiS1mB7d2rb9bPB3vPPwHOGmUfqQPQDwHRntNGh fiQiw8xFR55Th1eVuL7dlMP7rtKWiFnOelFI6kBWlRtvZQsvSZR4sVto5rKfbPMafbIR 7SIQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=hrSe+43UgdM8BSXwHh3b3dmlayy3t0TbE1vJT23vx58=; b=DbHu1aq/FZxlCAs58X2L8crtrlKDciVVD1wnuADOFssj7Ov7yJFRDeby37H0+oazA5 XMzWZK/2xBq8A8LKJLaBM9VNyM79RQnpD0j/Xsy0GMhgCF48qjy8opf0rafoNl+a6aBj FbdsXip9CYk23vUlYWdRkupplKg4IoFxtY6E+N2emQ9g4z5eQtDnIBL4/KpndnM9MhWO N7R2QQSLWZVWfh5kLInu0hyBeJXoBptdOh9NvILgX4SuDvAcJrV4dlPOc32oQDN6nXNs 0t9lSSWOOcj6VgY1JDEZ6XGtnRp9Q5stw3C13FybR+xLzmrpI68G+LGercNf4dAAFyBE Wdrw== ARC-Authentication-Results: i=1; mx.google.com; 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 24si12515299pgo.350.2019.06.25.00.33.21; Tue, 25 Jun 2019 00:33:36 -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; 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 S1728655AbfFYGAg (ORCPT + 99 others); Tue, 25 Jun 2019 02:00:36 -0400 Received: from verein.lst.de ([213.95.11.211]:59667 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726495AbfFYGAg (ORCPT ); Tue, 25 Jun 2019 02:00:36 -0400 Received: by newverein.lst.de (Postfix, from userid 2407) id 1546568B02; Tue, 25 Jun 2019 08:00:00 +0200 (CEST) Date: Tue, 25 Jun 2019 08:00:00 +0200 From: Christoph Hellwig To: Fredrik Noring Cc: Christoph Hellwig , Guenter Roeck , laurentiu.tudor@nxp.com, stern@rowland.harvard.edu, gregkh@linuxfoundation.org, linux-usb@vger.kernel.org, marex@denx.de, leoyang.li@nxp.com, linux-kernel@vger.kernel.org, robin.murphy@arm.com, JuergenUrban@gmx.de Subject: Re: [PATCH v7 3/5] usb: host: ohci-sm501: init genalloc for local memory Message-ID: <20190625060000.GA28986@lst.de> References: <20190611133223.GA30054@roeck-us.net> <20190611172654.GA2602@sx9> <20190611190343.GA18459@roeck-us.net> <20190613134033.GA2489@sx9> <20190613153414.GA909@sx9> <3f2164cd-7655-b7cc-ec57-d8751886728c@roeck-us.net> <20190614142816.GA2574@sx9> <20190624063515.GA3296@lst.de> <20190624125916.GA2516@sx9> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190624125916.GA2516@sx9> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 24, 2019 at 02:59:16PM +0200, Fredrik Noring wrote: > Hi Christoph, > > > Can you send me the patch formally so that I can queue it up for the > > dma-mapping tree? > > That patch would be detrimental to local memory devices, as previously > discussed, so I would like to suggest a much better approach, as shown below, > where allocations are aligned as required but not necessarily much more than > that. This looks sensible to me. Can you submit it with a proper patch description and split into a separate patch for genalloc vs the user of the new interface?