From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id C8C7BE00902; Wed, 21 Jan 2015 19:52:16 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from smtp.webfaction.com (mail6.webfaction.com [74.55.86.74]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 64F27E008EC for ; Wed, 21 Jan 2015 19:52:12 -0800 (PST) Received: from [192.168.1.10] (c-73-194-208-34.hsd1.nj.comcast.net [73.194.208.34]) by smtp.webfaction.com (Postfix) with ESMTP id DF22320A35B5; Thu, 22 Jan 2015 03:52:10 +0000 (UTC) Message-ID: <54C073E8.3050305@mindchasers.com> Date: Wed, 21 Jan 2015 22:52:08 -0500 From: Bob Cochran User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: "meta-freescale@yoctoproject.org" , "ting.liu@freescale.com" , Zhenhua Luo Subject: meta-fsl-ppc: DPAA, questioning constants used for T1040 that are borrowed from FMAN V3H.... X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2015 03:52:16 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi, There are some values set for T1040 / FMANV3L that don't match the published specifications for the part. The values I'm questioning are mainly defined in drivers/net/ethernet/freescale/fman/inc/integrations/T4240/dpaa_integration_ext.h (V3H integration layer) I'm wondering whether this is a purposeful overallocation to simplify things or if this is an oversight. The mismatch that troubles me most is the max number of tasks in FMBM_CFG2.TNTSKS is set to 124 rather than 60 (in violation of the T1040 DPAA RM). Also, this value appears to be hard coded in Peripherals/FM/fm.h rather than use the BMI_MAX_NUM_OF_TASKS value in dpaa_integration_ext.h, which is also set wrong for FMAN V3L. Below is a list of dpaa_integration_ext.h constants (#defines) that are being used for the T1040 but don't appear to match the published capabilities: FM_MURAM_SIZE should be 192 KILOBYTE, not 384 KILOBYTE FM_IRAM_SIZE should be 32 KILOBYTE, not 64 KILOBYTE FM_NUM_OF_CTRL should be 1, not 4 FM_VSP_MAX_NUM_OF_ENTRIES should be 32, not 64 FM_MAX_NUM_OF_10G_MACS should be 0, not 1 And there are some others, like the enums for the number of SW portals (24 are allocated but the T1040 only has 10). If these over-allocations are purposeful, then I'll keep my patches local to optimize my target's RAM. Otherwise, I'll submit my patches once I am done rigorously testing my changes. Thanks Bob