Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3712740imj; Tue, 12 Feb 2019 03:27:45 -0800 (PST) X-Google-Smtp-Source: AHgI3IYhUIWqw8ecsYGVL+80+cIKrlqVfHeDpTU3UbisKw59dwOkZNssw6m5JxTUAEU/zMMiFro4 X-Received: by 2002:aa7:810c:: with SMTP id b12mr3525265pfi.44.1549970865437; Tue, 12 Feb 2019 03:27:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549970865; cv=none; d=google.com; s=arc-20160816; b=KWN/LZFJf7F2cnoqbI905CPbLLCELyMtXXd9ukUE660WjUcBCreavpRxiVU+8DumqJ HXnNax2sWQ6xK/cs1A2n18i+aZtYkAgwPW7iwIpiJxTSDQFZwX91V4RwwPAEGwa7Vz0b 44SOEXWo1uOGJ1UjQAxSOV5RbTg6HSyPiZcpm/BYtuY7Iz65rFG0LZpNctGorhahD35q Q6ooKvemnE93B/SanMsvS2V95e76VzvDH7WJVxPVhc8+RVXIonstuPUgZoQUuuP2NK0m aJBAhj95KGDDrtg/RlGxC4eIuWz3AGbv84jB8TjPzs8hFh+3PUzAd/CfP+eqlFxo5dw3 5P2Q== 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:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=eG82BeaLg7G5TqLorqU1noHcVQhlezYxUVlEo9FpuTs=; b=rA6PiblkvzD5W2gcVWTgTCBVaaF2DgHuetgQdtyqRSsPVQPqA/nA11E1HXuq/DWtIz Mkz1dIuJ9IaBfE3PZCJ8Tzwrp1ZSwrorefkxuBbxH4BCac1O/QzrqZ71zux7CAL83ROw SRx52rqraWleIFApZ4vIRsZJYhJ7fqHTMyiuuCDniYb5M6EgLRP7szOy8VE22TQiqAcr hXPpJLV+GQ3+8W7fPoqFOBjzggnq8YQveUJqVYeS3+KszBbR+VLxlN8tl5ME9hfYyoV8 C0rB11STryuV9b9DE/4SXkN2tRkcBrbRH/Lw5j1QBGaC/yw6QRap7wpO4mBhS+9RT1F7 pUkw== 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 z16si11425268pgu.407.2019.02.12.03.27.29; Tue, 12 Feb 2019 03:27:45 -0800 (PST) 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 S1728516AbfBLLNC (ORCPT + 99 others); Tue, 12 Feb 2019 06:13:02 -0500 Received: from gloria.sntech.de ([185.11.138.130]:35480 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727428AbfBLLNC (ORCPT ); Tue, 12 Feb 2019 06:13:02 -0500 Received: from ip5f5a6320.dynamic.kabel-deutschland.de ([95.90.99.32] helo=diego.localnet) by gloria.sntech.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1gtVzl-0001Au-HM; Tue, 12 Feb 2019 12:12:57 +0100 From: Heiko =?ISO-8859-1?Q?St=FCbner?= To: Katsuhiro Suzuki Cc: linux-rockchip@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] arm64: dts: rockchip: add HDMI sound node for rk3328-rock64 Date: Tue, 12 Feb 2019 12:12:57 +0100 Message-ID: <2275914.n7pQDzs7mT@diego> In-Reply-To: References: <20190202043444.9308-1-katsuhiro@katsuster.net> <1970132.3b67tCGWFf@phil> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Am Montag, 4. Februar 2019, 13:59:37 CET schrieb Katsuhiro Suzuki: > On 2019/02/03 18:06, Heiko Stuebner wrote: > > Am Samstag, 2. Februar 2019, 05:34:44 CET schrieb Katsuhiro Suzuki: > >> This patch adds HDMI sound (I2S0) node and remove dma properties > >> from UART2 node for rock64. > >> > >> The DMAC of rk3328 can use 8 channels at same time. Currently, total > >> > >> 7 channels are used as follows: > >> - I2S1 2ch > >> - UART2 2ch > >> - SPDIF 1ch > >> - SPI0 2ch > >> > >> HDMI audio using I2S0 that requires 2ch but DMAC has only 1 channel. > >> > >> UART2 can work without DMA resources, so this patch removes dma > >> allocation for UART2 and reuses it to I2S0. > > > > I don't follow that description. How can i2s0 re-use the uart2 dma > > channels? Looking at the dma table in the TRM, uart2 has channels 6+7 > > while i2s0 uses channels 11+12. They should just run concurrently? > > Sorry for confusing... 6 or 7 is as ID number of slave DMA channel. > TRM calls it 'Req number'. Req number 6+7 and 11+12 can work > concurrently but TRM says DMAC can transfer 8 DMA channels at same > time. So all 16 Req numbers cannot activate at same time. It should > be keep less or equal than 8 numbers. But that "shortcoming" of having more requests than channels is not something specific to the pl330, instead most dma controllers have that "problem", which seems to get solved by the virt-dma mechanism of dmaengine - which pl330 doesn't use so far. (but see pl080 for example) The devicetree only describes the hardware and is never meant as a configuration space for kernel-code shortcomings. Heiko