Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp2842148imm; Fri, 19 Oct 2018 00:09:19 -0700 (PDT) X-Google-Smtp-Source: ACcGV60WJBfcCNyGorEpwFaChHhoY4QsHy3T6Uk1d3JHc2X7IvCWkmbfujPjDA63oUH5fiLY3S0N X-Received: by 2002:a17:902:4222:: with SMTP id g31-v6mr33606324pld.281.1539932959542; Fri, 19 Oct 2018 00:09:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539932959; cv=none; d=google.com; s=arc-20160816; b=kYWhXlmlMm+t2Iq1Zpvr9tGO3S40nbjis6z0JGmV6wYiF59Z9eOjJo82nl+N2+aPS/ gHf7YCnyBatmZj3DvgON9VQba73FmDYbNo7qEj4voDIhdruJCrU9hARr20k+HH1h+1xJ 5KjUZXnA5LznZkx8M18nldMpnf7QmptYhNgUwzY5YOOSjQyHMlPg6lWjSn7KYIe+EZX9 DijVkUXfeLfT1Xm0ep1qMUw1qG2DzTBHUxsvblrlhCFWNxbqwFhsYK1hEYcxFCrHkCDE zTi1zsjjuGkzatfSvShEjvebPnoZrQ23MAmS6NPmjKcFtVdXHuU1xrdw8i7iopuK2NHG lFMg== 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:dkim-signature; bh=JDErUPvQjrQUI0PUQIGFZwln7G1kY7+iNR47A1Xqui4=; b=YI3NGLcgULQKPE1y9+/ulB1YB7+RTDYIoqk6vLczECv9ZcgFxR5aiuo7f1akruKuV+ k1cv2SDlO4TAR/ZRVTe12YSTJx75DLb2YLEgEN8KiSg7QDE4Oinucio6mNQA9IBnWnRC f9sSGyxXOD3BHyr1w707MX7SFkBpBB+g1mOSgLemCZrt4gJ4uEjTTt2dta0171qc+bj6 0WKsBUrzzWOIYN2SuYJg6i8X6krxgZdP/S3F6THA/fJpe4dBZK+JEYDvxQwU7gTma0fz Soj+WXTay1xKHvoISWgpJFoHlX3zFPXM927YQA6UlZxOd8vSig7W4vLP0uwjT01efFEp Ew+w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=DsIgMhKi; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b1-v6si23492726pfc.156.2018.10.19.00.09.04; Fri, 19 Oct 2018 00:09:19 -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=@gmail.com header.s=20161025 header.b=DsIgMhKi; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727173AbeJSPNI (ORCPT + 99 others); Fri, 19 Oct 2018 11:13:08 -0400 Received: from mail-pf1-f194.google.com ([209.85.210.194]:46302 "EHLO mail-pf1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726758AbeJSPNI (ORCPT ); Fri, 19 Oct 2018 11:13:08 -0400 Received: by mail-pf1-f194.google.com with SMTP id r64-v6so16055403pfb.13; Fri, 19 Oct 2018 00:08:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=JDErUPvQjrQUI0PUQIGFZwln7G1kY7+iNR47A1Xqui4=; b=DsIgMhKiEf/HFAxN8EwaXeDTfGNg2JToTZibaK2PKvYi7IVqRva5sqy3nRltY2uuLN yKPoCIQnl1mvXVJDKWgs9+pu/brH3UXXzmvWrdFmshmT/a+HVqRrxJjuOmvdzoFh0ESV mFM0AAhXWIR21NCI0+OvJfheThaTanK3VmcSnx9FP8zXT/cCl4hveSTwb0RjxSCkHpjm V2Au1FhQa5S7Tg9oMxZoPvMz3YuccNfUyg8Vp+W76RjWi2HTmHTsanlnuuJNz22z6DGv K2nxQM4rQjVBaXScn5wtJToyJBPy2M1VYLOHS/fuuHwO3R5QMcmTNpcmwGqnQKvH6nDp bFFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=JDErUPvQjrQUI0PUQIGFZwln7G1kY7+iNR47A1Xqui4=; b=JUIsZpoHb/rqasFF7J2qgwo+zP2oYHlfYmyREvJjJVVNTcNgJD1UtwHzqouIxRZ/jM C9Ro5WwfocTTiGvLytC1hDFBJ6B2LEuFZ8QeMt3fmtlE1aLCTxOYyYcxtd40TnJiOzuu G1FYd0t6S3M2AZdUTarNQbZaK7V7XPae2YVN+/2CKnE0mXVmgSEWFpxQ9yLfNEnmxMM9 2WBv0Lnjpg1NZQjPLRgzdKNbwZJaaLEa+AiobIPxhnPkXHEjvA0c0t7VyjIhj3uzf8Wq Yyfie43LlCzSBSDtMWHyqLrbikPCnuoGRfF9swfntVYj1iRmF6rdMsEL8ILWde3juopB wUBg== X-Gm-Message-State: ABuFfogI/WK8Ls6Ko5aOBPHnHhrvSJkFPoeKSNbDG3Dkp80Oe5WN3YUr QqRUDtLpGV83NGaOD5aU9VY= X-Received: by 2002:a62:d206:: with SMTP id c6-v6mr8447911pfg.8.1539932901182; Fri, 19 Oct 2018 00:08:21 -0700 (PDT) Received: from Pilot130 (211-20-114-70.HINET-IP.hinet.net. [211.20.114.70]) by smtp.gmail.com with ESMTPSA id 130-v6sm22296529pfz.174.2018.10.19.00.08.16 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Fri, 19 Oct 2018 00:08:20 -0700 (PDT) Date: Fri, 19 Oct 2018 12:41:56 +0530 From: "sudheer.v" To: Benjamin Herrenschmidt Cc: Vinod , Rob Herring , Mark Rutland , Greg Kroah-Hartman , Joel Stanley , Andrew Jeffery , Russell King , Dan Williams , Jiri Slaby , Thomas Gleixner , Marc Zyngier , Christian Borntraeger , Michael Moese , Hendrik Brueckner , Kate Stewart , Philippe Ombredanne , dmaengine@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-aspeed@lists.ozlabs.org, Sudheer V , ShivahShankar Shakarnarayan rao Subject: Re: [[PATCH] 8/9] DMA-UART-Driver-for-AST2500 Message-ID: <20181019071154.GE13642@Pilot130> References: <1539749466-3912-1-git-send-email-open.sudheer@gmail.com> <1539749466-3912-9-git-send-email-open.sudheer@gmail.com> <20181017060531.GU2400@vkoul-mobl> <351eecd5b1b21893e94f76b34c058c6257b7f837.camel@kernel.crashing.org> <20181018095507.GC2400@vkoul-mobl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 19, 2018 at 10:32:24AM +1100, Benjamin Herrenschmidt wrote: > On Thu, 2018-10-18 at 15:25 +0530, Vinod wrote: > > > > > It's not a dmaengine driver. It's a serial UART driver that happens to > > > use a dedicated DMA engine. > > > > Then I see no reason for it to use dmaengine APIs. The framework allows > > people to share a controller for many clients, but if you have dedicated > > one then you may use it directly > > Well... the engine is shared by a few UARTs, they have dedicated rings > but there's a common set of regs for interrupt handling etc. > > That said, I still think it could be contained within a UART driver, > there's little benefit in adding the framework overhead, esp since > these are really weak cores, any overhead will be felt. > > Ben. > > > > It's unclear whether it should be split into two drivers, or just have > > > the serial driver directly use the dma engine since that engine is > > > dedicated in HW to only work on those UARTs and nothing else... > > > > > > Cheers, > > > Ben. Initially we wanted to have a single driver, however we had an informal discussion with one of the maintainer and based on the feedback, followed the Linux DMA and UART architecture. If this seperate DMA-engine driver adds more overhead than benifit, we will merge them into a single UART driver and resubmitt the patches. Vinod, can this dma-controller driver sit under dma subsystem?. or better to move it under UART framework. Thank you. -- Sudheer