Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751770AbdHJFrL (ORCPT ); Thu, 10 Aug 2017 01:47:11 -0400 Received: from shards.monkeyblade.net ([184.105.139.130]:51922 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750868AbdHJFrK (ORCPT ); Thu, 10 Aug 2017 01:47:10 -0400 Date: Wed, 09 Aug 2017 22:47:08 -0700 (PDT) Message-Id: <20170809.224708.2158045350450030076.davem@davemloft.net> To: john@phrozen.org Cc: sean.wang@mediatek.com, netdev@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org, muciri@openmesh.com, shashidhar.lakkavalli@openmesh.com Subject: Re: [PATCH 0/2] net-next: mediatek: bring up QDMA RX ring 0 From: David Miller In-Reply-To: <20170809100932.10539-1-john@phrozen.org> References: <20170809100932.10539-1-john@phrozen.org> X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Wed, 09 Aug 2017 22:47:09 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 361 Lines: 9 From: John Crispin Date: Wed, 9 Aug 2017 12:09:30 +0200 > The MT7623 has several DMA rings. Inside the SW path, the core will use > the PDMA when receiving traffic. While bringing up the HW path we noticed > that the PPE requires the QDMA RX to also be brought up as it uses this > ring internally for its flow scheduling. Series applied.