Received: by 2002:ac0:a591:0:0:0:0:0 with SMTP id m17-v6csp443410imm; Sat, 7 Jul 2018 00:28:56 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfSwdSj1hHml+CXzb1Wgfmnnwogcs+AQaRpGAwYh/WuEJjPuh4U2t2XxYcCt8NyKjvr/YCB X-Received: by 2002:a17:902:8e87:: with SMTP id bg7-v6mr12923548plb.129.1530948536500; Sat, 07 Jul 2018 00:28:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530948536; cv=none; d=google.com; s=arc-20160816; b=LgX89fVD2Mpv51DOvkye4fv2osjBL8a37GaPjfWHmt63Oi/o/KlHKnXhTfBNCy65Np ilHHZ1OtcQx+lklsh+NRoAsSbTQ5+7hkDT/ctUqL2RMOKoxlP3M26mT6cHxGyCxAPVu8 Mb7DrHhNVKwdTMQoTEH7f7R90bkB3SfT/mQkJRS3M21Y+ZZXYmpLY8LRXN3HWNEAqn8a 2uixUPHKr7cdBO/Z6BLJC9hQjKzlKUO9g4AleVrp6B9Bc+gFqRuiOFFjJ0fI/FH/8Cwn EVdVHrXHXTwgRkF+KzK8YdP1whkmup0YsY2IyowUTZ0YV1ra15Y4L63QqrsOcFxi0+Qo /iRA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=yUa2bUGn8FCR61aQFejfeap9aUU1xxuiYxbyut0ysv4=; b=mhKQW1RsrRTSVgdcUlqY3PZ4xqWHyBTyDYoIxTTqc4fgvafGAd8IziZyJBzOsV7Kq8 IsQ3d401eHsPJSA0M5waHwlHvayHeVgNPMoOFiPmC9CtilaAkrE3Guc1h/czftlITDen 8wIZd5voptlXUQCgQ00NFhSVxgFsUBoHCFQTVcnIqIC4w/CL/13P9I+mBxSwNURBWrqG 6Oq2bMqXt5UDZs4fIzgGR81d8WPA11hKMd1/UWOAeJTXKIgl1bTc+bI4MkhapNEu/5Sw rtLyWAJGfSoTCX/Vcx3tRv2aHwGvR25QVaQwXs2ros+i//HSkBtck7Gkmc2teGHzsDf6 J04Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=buo2Ixu1; 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 z4-v6si8931444pgp.580.2018.07.07.00.28.39; Sat, 07 Jul 2018 00:28:56 -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=buo2Ixu1; 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 S1752895AbeGGH2A (ORCPT + 99 others); Sat, 7 Jul 2018 03:28:00 -0400 Received: from mail-pf0-f194.google.com ([209.85.192.194]:34931 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751863AbeGGH15 (ORCPT ); Sat, 7 Jul 2018 03:27:57 -0400 Received: by mail-pf0-f194.google.com with SMTP id q7-v6so9025865pff.2; Sat, 07 Jul 2018 00:27:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yUa2bUGn8FCR61aQFejfeap9aUU1xxuiYxbyut0ysv4=; b=buo2Ixu11W3g46CV6Kluz4hQGIeCwxowCW1IgmylIX8mLo+491zSJecQdzc5L8nztO 1pS1tqjsJh8GkkwnEX2yEtw+Zq7cKYFHw10Lbu6EG2s0Ao7PD2q+R0RW1D97hR+6bSM/ /k73YXkn7qUX90tHs5lAgER8qzcezQg5/dFqlaED2qF1tTTR3itQW2/239TzmfCbJyx8 fVbtN0FO070cdW6Jf2H9nMF3lNj53MERdem1i4LALCS4TMC1laYXYeiaT4avy5S56bFC 9ARx8jT4Z12+w1n3THsDaWSF1p2G3vXL9QIIwQshA+ZHsjbOqLhO5FVcFGAwrHC77wvx olnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yUa2bUGn8FCR61aQFejfeap9aUU1xxuiYxbyut0ysv4=; b=mL88xD+b0EcRjHZcYTwRAupl6HneHwZuSCXJ/vl/BbxiMJGSNOepJH0pgERR96xPkZ +hEwVV4vgSRR/jv8Zz/6/PXu80jKsN5Eqz4EbKf2Lu8ZG/ntDFwYBzPE2yJI/xkr05cK zfc2BtlvqiKE37dKwpg+zhbfAEJHhifMQHwhud4dmKlw8ZouRqN31VEoIuJ6Zk23bRFY EDqO/EhD/9VaqPT4Vv6AskOftCuY5LuTBItfRh2T78aE9JWVRqNfXgfWxs5PqL2mLHuf g8p4VjDu9nJmytLhOADqBo4o8FWTXFywXg5l5IdmyZ5E1gy5v0/VmwoYLMnooDhJobV/ pLIQ== X-Gm-Message-State: APt69E0BiMVlGhFUjcgiq+XAFm7gdAhuzlj2wWktmzMFx4wIheGKIPzX ANci/y/Ab9JA7LIHvGIiMSUkV/6ID1qBilVA4Uw= X-Received: by 2002:a65:6699:: with SMTP id b25-v6mr7297578pgw.426.1530948476764; Sat, 07 Jul 2018 00:27:56 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a17:90a:2604:0:0:0:0 with HTTP; Sat, 7 Jul 2018 00:27:56 -0700 (PDT) In-Reply-To: <1530827112.6642.2@smtp.crapouillou.net> References: <20180703123214.23090-1-paul@crapouillou.net> <20180703123214.23090-3-paul@crapouillou.net> <1530827112.6642.2@smtp.crapouillou.net> From: PrasannaKumar Muralidharan Date: Sat, 7 Jul 2018 12:57:56 +0530 Message-ID: Subject: Re: [PATCH 02/14] dmaengine: dma-jz4780: Separate chan/ctrl registers To: Paul Cercueil Cc: Vinod Koul , Rob Herring , Mark Rutland , Ralf Baechle , Paul Burton , James Hogan , Zubair Lutfullah Kakakhel , Mathieu Malaterre , Daniel Silsby , dmaengine@vger.kernel.org, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , open list , Linux-MIPS Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6 July 2018 at 03:15, Paul Cercueil wrote: > > >> Paul, >> >> On 3 July 2018 at 18:02, Paul Cercueil wrote: >>> >>> The register area of the JZ4780 DMA core can be split into different >>> sections for different purposes: >>> >>> * one set of registers is used to perform actions at the DMA core level, >>> that will generally affect all channels; >>> >>> * one set of registers per DMA channel, to perform actions at the DMA >>> channel level, that will only affect the channel in question. >>> >>> The problem rises when trying to support new versions of the JZ47xx >>> Ingenic SoC. For instance, the JZ4770 has two DMA cores, each one >>> with six DMA channels, and the register sets are interleaved: >>> >>> >>> By using one memory resource for the channel-specific registers and >>> one memory resource for the core-specific registers, we can support >>> the JZ4770, by initializing the driver once per DMA core with different >>> addresses. >> >> >> As per my understanding device tree should be modified only when >> hardware changes. This looks the other way around. It must be possible >> to achieve what you are trying to do in this patch without changing >> the device tree. > > > I would agree that devicetree has an ABI that we shouldn't break if > possible. > > However DTS support for all the Ingenic SoCs/boards is far from being > complete, and more importantly, all Ingenic-based boards compile the DTS > file within the kernel; so breaking the ABI is not (yet) a problem, and > we should push the big changes right now while it's still possible. Completely agree with you in this. Let's wait and see what DT maintainer's view.