From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net v2 1/1] bnx2x: Assign unique DMAE channel number for FW DMAE transactions. Date: Mon, 12 Nov 2018 08:54:55 -0800 (PST) Message-ID: <20181112.085455.1513459403088791878.davem@davemloft.net> References: <20181112022734.22168-1-sudarsana.kalluru@cavium.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, Michal.Kalderon@cavium.com To: sudarsana.kalluru@cavium.com Return-path: Received: from shards.monkeyblade.net ([23.128.96.9]:56718 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728149AbeKMCtA (ORCPT ); Mon, 12 Nov 2018 21:49:00 -0500 In-Reply-To: <20181112022734.22168-1-sudarsana.kalluru@cavium.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Sudarsana Reddy Kalluru Date: Sun, 11 Nov 2018 18:27:34 -0800 > Driver assigns DMAE channel 0 for FW as part of START_RAMROD command. FW > uses this channel for DMAE operations (e.g., TIME_SYNC implementation). > Driver also uses the same channel 0 for DMAE operations for some of the PFs > (e.g., PF0 on Port0). This could lead to concurrent access to the DMAE > channel by FW and driver which is not legal. Hence need to assign unique > DMAE id for FW. > Currently following DMAE channels are used by the clients, > MFW - OCBB/OCSD functionality uses DMAE channel 14/15 > Driver 0-3 and 8-11 (for PF dmae operations) > 4 and 12 (for stats requests) > Assigning unique dmae_id '13' to the FW. > > Changes from previous version: > ------------------------------ > v2: Incorporated the review comments. > > Signed-off-by: Sudarsana Reddy Kalluru > Signed-off-by: Michal Kalderon Applied.