From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <hemant.agrawal@nxp.com>
Received: from NAM03-DM3-obe.outbound.protection.outlook.com
(mail-dm3nam03on0066.outbound.protection.outlook.com [104.47.41.66])
by dpdk.org (Postfix) with ESMTP id 50CB22BA2
for <dev@dpdk.org>; Tue, 17 Jan 2017 14:19:23 +0100 (CET)
Received: from BN6PR03CA0005.namprd03.prod.outlook.com (10.168.230.143) by
BN6PR03MB2465.namprd03.prod.outlook.com (10.168.223.19) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id
15.1.845.12; Tue, 17 Jan 2017 13:19:19 +0000
Received: from BL2FFO11FD005.protection.gbl (2a01:111:f400:7c09::124) by
BN6PR03CA0005.outlook.office365.com (2603:10b6:404:23::15) with Microsoft
SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.860.13 via
Frontend Transport; Tue, 17 Jan 2017 13:19:20 +0000
Authentication-Results: spf=fail (sender IP is 192.88.168.50)
smtp.mailfrom=nxp.com; nxp.com; dkim=none (message not signed)
header.d=none;nxp.com; dmarc=fail action=none header.from=nxp.com;nxp.com;
dkim=none (message not signed) header.d=none;
Received-SPF: Fail (protection.outlook.com: domain of nxp.com does not
designate 192.88.168.50 as permitted sender) receiver=protection.outlook.com;
client-ip=192.88.168.50; helo=tx30smr01.am.freescale.net;
Received: from tx30smr01.am.freescale.net (192.88.168.50) by
BL2FFO11FD005.mail.protection.outlook.com (10.173.161.1) with Microsoft SMTP
Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.803.8
via Frontend Transport; Tue, 17 Jan 2017 13:19:19 +0000
Received: from bf-netperf1.idc ([10.232.134.28])
by tx30smr01.am.freescale.net (8.14.3/8.14.0) with ESMTP id v0HDJ8m9021741;
Tue, 17 Jan 2017 06:19:16 -0700
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: <dev@dpdk.org>
CC: <thomas.monjalon@6wind.com>, <bruce.richardson@intel.com>,
<shreyansh.jain@nxp.com>, <john.mcnamara@intel.com>,
<ferruh.yigit@intel.com>, <jerin.jacob@caviumnetworks.com>, Hemant Agrawal
<hemant.agrawal@nxp.com>
Date: Wed, 18 Jan 2017 00:22:23 +0530
Message-ID: <1484679174-4174-3-git-send-email-hemant.agrawal@nxp.com>
X-Mailer: git-send-email 1.9.1
In-Reply-To: <1484679174-4174-1-git-send-email-hemant.agrawal@nxp.com>
References: <1482988612-6638-1-git-send-email-shreyansh.jain@nxp.com>
<1484679174-4174-1-git-send-email-hemant.agrawal@nxp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-EOPAttributedMessage: 0
X-Matching-Connectors: 131291327597089180;
(91ab9b29-cfa4-454e-5278-08d120cd25b8); ()
X-Forefront-Antispam-Report: CIP:192.88.168.50; IPV:NLI; CTRY:US; EFV:NLI;
SFV:NSPM;
SFS:(10009020)(6009001)(336005)(7916002)(39850400002)(39450400003)(39380400002)(39410400002)(39860400002)(39840400002)(39400400002)(2980300002)(1109001)(1110001)(339900001)(189002)(199003)(36756003)(68736007)(31430400001)(50226002)(54906002)(97736004)(92566002)(47776003)(6916009)(2870700001)(8656002)(356003)(85426001)(50466002)(110136003)(305945005)(5660300001)(77096006)(5820100001)(38730400001)(76176999)(4326007)(86362001)(8936002)(33646002)(2906002)(189998001)(6306002)(2950100002)(8676002)(6666003)(81166006)(104016004)(105606002)(50986999)(626004)(106466001)(23676002)(2351001)(81156014)(30001);
DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR03MB2465; H:tx30smr01.am.freescale.net;
FPR:; SPF:Fail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en;
X-Microsoft-Exchange-Diagnostics: 1; BL2FFO11FD005;
1:vdJySZnldVHlDeeO15G77dtJ/aI+BKxUxNoEqXRrp2OsoXmxx3OERjgEippTKv0ZS3Ku7i6tMMf9hisru3KQMuqZgQRxvefree2yZGSi5H49COprmz4uquU5rRM1/72B9x5UapOBwWiCck+byQn7w/1IiW2oysOxoyHltSdxjMBMHo76ohh++MiqP5jTEvQM9QNRaj4ofmKvdjkW/sQjqpKlU1qJ5BGmtFF13KIftscFfhjVmh00D0GChRwlbAgE7pr7iDQJlpCr1NQR9LRsm4y28UMlMAs1mUGYpUD/J7Nn51lQJn1BuWb7Kklmpwtu2qwzXACn04z/ihhWZisXcQbCeenuWUjSp7J4eOE8uDCxtLCEoUkL/T+ZJy/9sxaGVW5/cfGLYQeBC0jZaTC4PI06rcEAfVOdAkJeuqFodK59N2wbS+DNErbdUq0CGvikQ8a3cSiz2+jJSvb5hEPf4Z9C3ghhwMDQHROi7+tDhJDxdR2u5oqWE6A7vByyn8DHHn/RMyxEB5fHXQiJpwzlQsOsTarZbq0ufhxtqpwaJc+VNLKTL0tBojaB0SO+5TMUV4hZJ8at8WYBqWz6wWj6G9bV3RbFTknpbDdgnzImifnv5dRau5breZoQIQ8ROUpX0v6kfF2bQvuO1g35qEFxdoXew+kN9yy6+RduhwuBd8HMugyH/aBWVLzjTuwtfDMB77RyYst+73vMHHx7XL5MaqJ9q7Ync3Jjfav4DAdqH4kbqVVwV2Ux7Idd5cyvhP0F
X-MS-Office365-Filtering-Correlation-Id: 2921a3b4-1c51-4421-86ac-08d43edb71e7
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:BN6PR03MB2465;
X-Microsoft-Exchange-Diagnostics: 1; BN6PR03MB2465;
3:M7wmBc6GxmD0SXbGVQJF8leKnO/2/eyYq0NfADKter/b/hQ4aQFHu8hKS2WHxbtyYz24axOXy7pxm3wOV9EioVCKylkArgY3c5vVIi8t35PVyYBpdncdw0QBXXH7QgGmt9m5c7Dd259AXGnCDWPitBnoxe+vGouk+6+LUFrBeBg0ryn9s386Ai7jb0uxK7jInoKvBYjk9EHvpGTAujT5Eg3ja255c/sTWJbCDNSBniA3fX8PXqP5PtMRswU+1X19HaFRxdTCoSi3ergKAQvhKSBcwt0iZrkRx2hO9y0XJ/YXHd+8/bap+VmyD/Ha4sC+5e9QeJ4OIGPY90Jba6uJw6810K03Ypqce6sWyHMJ+iKjvP8P+No/s868z9u81z74
X-Microsoft-Exchange-Diagnostics: 1; BN6PR03MB2465;
25:6WQmc50CrXsd8o+x3gYvMScvyI7wTiCfWCbyIrt5uPcLHrHs6BxJsCXZltbxo9t3rHBNws88p0ZoO8SzLzyIwJahVxwuyA9OnChE5qs+hB5jUT4Iv2mZvU5JsJj69G3IYBRaY7L+kxB5EMOgCpwgv/A60ur3JJrTLajz7qP45FglXmNbtAq7UPVuZxZICQWy6hDVbWT7XPqVaae8z+iD83R3hqxXqfwkntGS/5OBtOz+ynNYqxaG7SIkOp2cGJEaFHZntG1USInhMhFLq4xxOwxqi4Tsnlj9V0XZXtMDVyYbQxzwgbo4vSYD7XO2yxgU6Imtu1FZuU59AlzS+DCxwDDEIeIiROpp8R9D3IVt1vugolg7gPgjXml8LdHbXTwaP+attW2uhvae/gCfNuNsK86+Q752O/bLtZZZLTYEkDk8Woo9j3aBNUBIJhHDo4l3Cvt9NiOKPDtDee7BatCXDfE4FWaMvjoLzwtpDmwBrrbWuJCOLjodoPGLaEK+pgLczxE9psB+qJHd0gwzBtSmIpqcCOvYje60Ux1uyLzO6gFklN4Kmod6c07/cOjbRA5imXs24KU9cxPEW0JYUJmU5Dp2q0CrsgBa4PnzBsoo3HsdfrH+HxdmO60VUvoNA7rkcHV+yWNyUeeC+B+jfYVIBHAXhjAurMwR5NmLJk3f3tBPsScF5V3mvXkzQARd3vabZ4tY2FCGkgOd3ZutKyDZcXcHR6AOKEBctsIRREMldeEIO1RXFHMYu8qYbjvKXaTloG25Qh0bkPJfiEehdhwb7D6HMEoSXvtsObzzTVaN51Qi53cm4eUEN8W2MTLDLEjBxz3TsLzdCk021esskg1D8gqdwjNIZZiNPybIP6PhQlpbold47O/YTemrPSEBJySKRWV531R2a63AKDgbOjHBIg==
X-Microsoft-Exchange-Diagnostics: 1; BN6PR03MB2465;
31:EOE8vmWv5QsPloQkJK0YDyHy2d5vrpmA8PoWq5muc2sI5Axa0t8k4I7USfRyDBA2VuxdrgfTsPBsyzobtI678LQAJMh+XZ7B+WIoTgp+mRgx6ie78MWzIY7lqlFOGP94dxVXT7vR2OHfNRi7Lf4POY35oHm6aKu2IwUCvFVHR0qrrJWB4Mzi9dcq2WNpVX2lhpkhlkA4piYXZXMEArygGybzDY9qrOvZWDYItz+unSd66O/1mY0ZslWQvbi4MRnIJqtgaXYAmTkM/bHVs2pt8Q==
X-Microsoft-Antispam-PRVS: <BN6PR03MB24658A9855DAE84B6E44227F897C0@BN6PR03MB2465.namprd03.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(166708455590820)(185117386973197)(227817650892897)(275809806118684)(21532816269658)(264314650089876);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0;
RULEID:(6095060)(601004)(2401047)(8121501046)(5005006)(13023025)(13017025)(13015025)(13024025)(13018025)(10201501046)(3002001)(6055026)(6096035)(20161123565025)(20161123563025)(20161123556025)(20161123559025)(20161123561025);
SRVR:BN6PR03MB2465; BCL:0; PCL:0; RULEID:(400006); SRVR:BN6PR03MB2465;
X-Microsoft-Exchange-Diagnostics: 1; BN6PR03MB2465;
4:tR/r5C39TtCYNHLoZGZm7tgDl+Ha1Bii3+hqAjarmbQS3L8EGvefjVsSgx+6EEdZMQ95qMD3y8TRdKMB4/yBF6xljqufyDC3RQZ3qzoLABUDT7CiC6SrL70199CEi02idA+835402zys212iwj5omKePNGp589eqJgXUj2RrU4TMDIaWEV6dLYmNcSDIgMHAccMyR+i33SXmK3Z9yaMOtMvazRL/On61tyUlWFodvBJDJzEQjcuSpAx8GMXa2Wbh7J/SbnOxxn3JNku8MTkKTKsQXjPDQa3fp0MZFR17/SEb+MvShlt3CZrvESK2XmoSEh9TX8We9QSUhefu983v15JaknJcL40qBespAiBKfDqH5fYplMTfbU1P5DZNKO57Ln67vjLaGtRY8pAqM14DFRtYcSGmw3U6d2lBnA0JUFeViXqBHQp9cH6B306dry5kn/ucnQucvK5HHq0+dRV63t1u1RyxikmGy24/OsDRFnEeaiHmoVL+SHG9GHw8+/+FNk8aF+U53CLOJ14tcyyZXAx5GtAq6NFqBACF0eSk5e+vkh76P5NwtZ3ceBmKCMU5m23d4t60b3Fx52TzoHM+xxqqlJERxLM/KNTrAs2R+row86ksM+SNb2OBNIr40gVfwtFGQOzDlBHorbmSkkxx+YdNF4i/5oRsxtj4dvCvhjClZRoc/oLqsXeRLw9Eex/cmcxahjgVscAUho7gnNLcpYL1QCtm25NKQYE3PguvOWGs6FCllBlRh17xXYDCfoMQXBWM2njcMDtPAH4ItsKsO+5eV2CcXwajCrvhBzBvl50qFoIU3RkUnIqf8Oq9IO4K5gvp1pvMx6aV8LyxTDFu4iaGGvMdS8rdIU9zmF7s2JqU5AaQYWZOAeRFSntRCCm16ZKyEip5SEXbNwx4NzwOuHPQ3Jr0XwscKUH4obENPdk=
X-Forefront-PRVS: 01901B3451
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCTjZQUjAzTUIyNDY1OzIzOmtZQmpMYTA0OGtNRUhwZnllQWMyT1M0aGE0?=
=?utf-8?B?MlhaN1VzTGM3bm1oMW9LSTI4OTVUeUlxTFo1OHVMVFJFZlQ3Y2ZXdXVwWmlj?=
=?utf-8?B?d0FYRzJKRjlHTlkwMjdSbmd6WjhlZUVTOWUvRUlGWXl3eHBFK3BnRnFaK1Y1?=
=?utf-8?B?TnpIQnlXOUcvN0NTUWdHa0tWL1duOExDMUJxOGtqN3JPU2VoVG5BWEl5aXBT?=
=?utf-8?B?dkpNMDJkc3VxNHJIcmdabnJLWGVvMmZwNEwzRkpjYnZReGptNFNBTlZ5a0NV?=
=?utf-8?B?YTdXdFQwSUhlTDhyT1JkdWtBTWxXeTdjOU1NVzZGckFLaE0xVGg4L0gzR3Qz?=
=?utf-8?B?cEdCYUwzeEdNK1p6NUJhV3pzSldDWU5ZRnNDQnJnM3IvNExwRU00NUVBRUNZ?=
=?utf-8?B?MHBNTlUwSVMxYnlCbDJsUUxUT0NVR3ZmUzJYaXZqMW14bHhtTXQvazd0d1hl?=
=?utf-8?B?MVNTTmtGeVE5cVVLS1h3MVM0Y3VYVmNCVXJvYURoTXpodUlEU096N3RUMWI4?=
=?utf-8?B?VGRzOXYrOWpyWHIzdk9wR1RQWW1PaU9ucHZEbjg1dGVuQk5aYnFXaUYxT2FQ?=
=?utf-8?B?dXJtbVBIUDJGc2RKV2ZJRS80a20wNGRHYWtwdnl6eitadG1RR0hlbUpyZGhz?=
=?utf-8?B?VForanI2MnlLcU1OL2ljbWcydDI1OUxZQXBIQ01laXFkcWhwNFdXdjhYTE5k?=
=?utf-8?B?YWRqdWZZZGhVRnNpYkkzaFFWVWgzY1hha1FlRzJnQ3hUZGxUTzI2S0EyaHNK?=
=?utf-8?B?dFlaRjd5QUJER2pIODNSeHc2WXVZL3dIb0Y2WWNJSDljSDM3eHV5M1pxSkJ1?=
=?utf-8?B?WnVmVVRLSWU2eGVtUmRhK1F0QldhZ1lNYW8xajBlRWRoRDVPVVZRMHkvZVZw?=
=?utf-8?B?V2t4WlJZaHQzR2xZMENuTnM0UWFycFZwamRtWTMrZlQvQUhPWmFxMXhPTHBS?=
=?utf-8?B?Q2Y0c2lkaExEZjJXS0RVVUZnYkVOS1FUdVBwZkxlbC93aGNXbjJ4d2dlZHkw?=
=?utf-8?B?dkdUSXEzb0dSRmZTbk9meFFkZk8yY3o5SWFlVFE4Yk1hMng5Zko4WlBOOWs3?=
=?utf-8?B?TUVFSTI2OUc1QzlISi9KZ1A2ODRicHIxOHpEYTBhVWEwb2hVbStvZ0JlWkdL?=
=?utf-8?B?Y1pvVElpa2VWTUJzQUt1cTBzVVVkQ0t2TUVGMFp0SDlXWUN1MlBxSTkvcERp?=
=?utf-8?B?MWlTQlU2OEltUlB5UTIxZUN4YnlMQ3BTS21JMVp3dzZqWWl4b21GSzRTVisy?=
=?utf-8?B?ZFBQejJ2SFROTnJ6cS9ZNXV5WSswVUkxcytkS1B1dTZtYWN3WFZ5SmtzZzB0?=
=?utf-8?B?L1doYjYveUNFeWtTWXhhazN0RkE5MjVuVGFhcVEwY0NwNFJTUzZRU0EwTk5k?=
=?utf-8?B?RC8wMGZ4S3Z2b3BXNjBPY2puVVdMYVNwRUsvdUpsR0xscE1mU2k2bU5raGVy?=
=?utf-8?B?Qm5YVTJxeFdNbmdVVTFna2tHVi9YbmFDYllOMHkrUUlsTk9ZTk9ySTBXdSs4?=
=?utf-8?B?b3VOMUwzRjNOMFdjajc5MnFsSW9YSUtMcmtrSHNycVZhSFB3YzlSMXFRd2x6?=
=?utf-8?B?TEljRWZOMEMvN2RUNzVKbEI3em5qc3ZDd29SZkczb20zd2xFaHErTi9DalYz?=
=?utf-8?B?UXhIWklKdFNBMURzMFZtUVpYRDN4LytBdTBKc1VncEprWEFnUFA1UVA5QS9w?=
=?utf-8?B?ZE9FWkJ3aVdaQW9BMkNhVXNZNDJmUUg0NHZsVUJYeHFrU0tGT0Jib2xBMWk4?=
=?utf-8?B?OWpCcHA3Si9wb3MrR2R6ZWFxUkp5b0RUMkFPemJnbTd2VE9kRTZDajE2WDRs?=
=?utf-8?B?K0c4K08zMzRPNzA2WkVsTE5DcnBvTjdUWnZ0UEZqR1E3MWc9PQ==?=
X-Microsoft-Exchange-Diagnostics: 1; BN6PR03MB2465;
6:rZuVImk9UwA3l3SnvbSLS9AsfkjPp1/lMJWKNEDolv99RQVzi/AfiJ8Z30jqBQHCOYL0Vv8rGec4RvKAjVQsxmlohaOBMFm2HBGs5TUWBDhQUhmT7YoDIALX2yfyvNrc8UutmVJOISqB2CN142XEnbKLlbVEnVHXdqVdjekOnOrie2fBKwgu7tT1rdq2SXI5m03css04UZG9yhjxnL4WbwDoT9LxQaPhcXPMloTVk2fxEaGXXoDY6GQdsBe4Kz8K1XjaO7ZqHxiddMd/88GTSpIZrIWwKw8neyxn3zcN63vFKTdmKEirI+FVbqHOialMe2QuYty3lnYzYF2bzWo4tg6AuZKLT1MlWI2bwy+kTQC8TT+k4kreBQu9teS26eFnVxTvDZDPWOdk1jztq+YWU17YpEdg6HDK6kZQCO66z1E84FY1PIIQP6JsJMyfHfrc;
5:B5paz69tkpDpW0KJEKBm3pz3D+OPa4uUvQoCSubOh2JKfuNY+/krKczFi1/bUPL22lsECVm+/Pmaq77zCz/XjPFDszVdmShHtvDOmlV/s5OUI8XlXpuxq6cdsLYbJ75v8e23vxHuV+y/SRfzoyroLrfhZZGToQTjtVqO5LdFXIUtJ/CA49sNOxcADwTLCpLt;
24:D6imlPXYByCpCGw3fjPtcNYUwEmEX0LDhkf3BH7aVlisJt8iyQtJDdG2P2Z4tjT9pJbNoijD4nsDWG7kbq9bp/zDkk8mYhmbDq4PTi4veg4=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; BN6PR03MB2465;
7:t6MYC5cv22TIfEnLu6o1/QRUFNbFZTW+o6wTpMh+qfh8wCOODCe9Rje+63ae3rEB/NfgwSM7OkJa/C1Uvq5yPfsZmJcddfSCKLHlTrjamwp/biLXwIJW8R5E6814fKAhKx2gnXV3H1QaPh/QrLSBj2ZeYofbzWuAXhz2OqbsdDXX3qQijTQYhX1cfpiofzPgKYCLTssv1IapIpqQ462h0wFwv5oNtZZUiP0QrSP8LwDpKJOsKpdaSiS/PAE+6hZc1eC0B23qkKQNvL8FtlF6b3RlcFWa+KEHriAHCGNUkl3zebBFJ+NRiRu7X7DenDHuVulq/gva/geTIiYkyHM2Lkkkc6ItdisvUNkHQzPuqmdCrNosHOd6d8mydYRLLpLQC+7/5N3GvvttmoZ/iWP8maTwCy26c+VAVR4hOF8VGCs1HJbECEALHb2QyfJ53kisWcqL6mfmtMFRDvgcinG/1w==
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 17 Jan 2017 13:19:19.4125 (UTC)
X-MS-Exchange-CrossTenant-Id: 5afe0b00-7697-4969-b663-5eab37d5f47e
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5afe0b00-7697-4969-b663-5eab37d5f47e; Ip=[192.88.168.50];
Helo=[tx30smr01.am.freescale.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR03MB2465
Subject: [dpdk-dev] [PATCHv4 02/33] doc: add dpaa2 nic details
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
<mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
<mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2017 13:19:23 -0000
This patch adds the NXP dpaa2 architecture and pmd details
in the Network interfaces section.
Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
MAINTAINERS | 8 +
doc/guides/nics/dpaa2.rst | 594 +++++++++++++++++++++++++++++++++
doc/guides/nics/features/dpaa2.ini | 8 +
doc/guides/nics/index.rst | 1 +
doc/guides/rel_notes/release_17_02.rst | 11 +
5 files changed, 622 insertions(+)
create mode 100644 doc/guides/nics/dpaa2.rst
create mode 100644 doc/guides/nics/features/dpaa2.ini
diff --git a/MAINTAINERS b/MAINTAINERS
index 9645c9b..7d6a89a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -354,6 +354,14 @@ M: Alejandro Lucero <alejandro.lucero@netronome.com>
F: drivers/net/nfp/
F: doc/guides/nics/nfp.rst
+NXP DPAA2 PMD
+M: Hemant Agrawal <hemant.agrawal@nxp.com>
+F: drivers/bus/fslmc/
+F: drivers/common/dpaa2/
+F: drivers/net/dpaa2/
+F: drivers/pool/dpaa2/
+F: doc/guides/nics/dpaa2.rst
+
QLogic bnx2x
M: Harish Patil <harish.patil@cavium.com>
M: Rasesh Mody <rasesh.mody@cavium.com>
diff --git a/doc/guides/nics/dpaa2.rst b/doc/guides/nics/dpaa2.rst
new file mode 100644
index 0000000..0b30a6f
--- /dev/null
+++ b/doc/guides/nics/dpaa2.rst
@@ -0,0 +1,594 @@
+.. BSD LICENSE
+ Copyright (C) NXP. 2016.
+ All rights reserved.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+
+ * Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+ * Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in
+ the documentation and/or other materials provided with the
+ distribution.
+ * Neither the name of NXP nor the names of its
+ contributors may be used to endorse or promote products derived
+ from this software without specific prior written permission.
+
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+ "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+ LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+ A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+ OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+ SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+ LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+ DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+ OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+DPAA2 Poll Mode Driver
+======================
+
+The DPAA2 NIC PMD (**librte_pmd_dpaa2**) provides poll mode driver
+support for the inbuilt NIC found in the **NXP DPAA2** SoC family.
+
+More information can be found at `NXP Official Website
+<http://www.nxp.com/products/microcontrollers-and-processors/arm-processors/qoriq-arm-processors:QORIQ-ARM>`_.
+
+NXP DPAA2 (Data Path Acceleration Architecture Gen2)
+----------------------------------------------------
+
+This section provides an overview of the NXP DPAA2 architecture
+and how it is integrated into the DPDK.
+
+Contents summary
+
+- DPAA2 overview
+- Overview of DPAA2 objects
+- DPAA2 driver architecture overview
+
+DPAA2 Overview
+~~~~~~~~~~~~~~
+
+Reference: `FSL MC BUS in Linux Kernel <https://www.kernel.org/doc/readme/drivers-staging-fsl-mc-README.txt>`_.
+
+DPAA2 is a hardware architecture designed for high-speed network
+packet processing. DPAA2 consists of sophisticated mechanisms for
+processing Ethernet packets, queue management, buffer management,
+autonomous L2 switching, virtual Ethernet bridging, and accelerator
+(e.g. crypto) sharing.
+
+A DPAA2 hardware component called the Management Complex (or MC) manages the
+DPAA2 hardware resources. The MC provides an object-based abstraction for
+software drivers to use the DPAA2 hardware.
+
+The MC uses DPAA2 hardware resources such as queues, buffer pools, and
+network ports to create functional objects/devices such as network
+interfaces, an L2 switch, or accelerator instances.
+
+The MC provides memory-mapped I/O command interfaces (MC portals)
+which DPAA2 software drivers use to operate on DPAA2 objects:
+
+The diagram below shows an overview of the DPAA2 resource management
+architecture:
+
+.. code-block:: console
+
+ +--------------------------------------+
+ | OS |
+ | DPAA2 drivers |
+ | | |
+ +-----------------------------|--------+
+ |
+ | (create,discover,connect
+ | config,use,destroy)
+ |
+ DPAA2 |
+ +------------------------| mc portal |-+
+ | | |
+ | +- - - - - - - - - - - - -V- - -+ |
+ | | | |
+ | | Management Complex (MC) | |
+ | | | |
+ | +- - - - - - - - - - - - - - - -+ |
+ | |
+ | Hardware Hardware |
+ | Resources Objects |
+ | --------- ------- |
+ | -queues -DPRC |
+ | -buffer pools -DPMCP |
+ | -Eth MACs/ports -DPIO |
+ | -network interface -DPNI |
+ | profiles -DPMAC |
+ | -queue portals -DPBP |
+ | -MC portals ... |
+ | ... |
+ | |
+ +--------------------------------------+
+
+The MC mediates operations such as create, discover,
+connect, configuration, and destroy. Fast-path operations
+on data, such as packet transmit/receive, are not mediated by
+the MC and are done directly using memory mapped regions in
+DPIO objects.
+
+Overview of DPAA2 Objects
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The section provides a brief overview of some key DPAA2 objects.
+A simple scenario is described illustrating the objects involved
+in creating a network interfaces.
+
+DPRC (Datapath Resource Container)
+
+ A DPRC is a container object that holds all the other
+ types of DPAA2 objects. In the example diagram below there
+ are 8 objects of 5 types (DPMCP, DPIO, DPBP, DPNI, and DPMAC)
+ in the container.
+
+.. code-block:: console
+
+ +---------------------------------------------------------+
+ | DPRC |
+ | |
+ | +-------+ +-------+ +-------+ +-------+ +-------+ |
+ | | DPMCP | | DPIO | | DPBP | | DPNI | | DPMAC | |
+ | +-------+ +-------+ +-------+ +---+---+ +---+---+ |
+ | | DPMCP | | DPIO | |
+ | +-------+ +-------+ |
+ | | DPMCP | |
+ | +-------+ |
+ | |
+ +---------------------------------------------------------+
+
+From the point of view of an OS, a DPRC behaves similar to a plug and
+play bus, like PCI. DPRC commands can be used to enumerate the contents
+of the DPRC, discover the hardware objects present (including mappable
+regions and interrupts).
+
+.. code-block:: console
+
+ DPRC.1 (bus)
+ |
+ +--+--------+-------+-------+-------+
+ | | | | |
+ DPMCP.1 DPIO.1 DPBP.1 DPNI.1 DPMAC.1
+ DPMCP.2 DPIO.2
+ DPMCP.3
+
+Hardware objects can be created and destroyed dynamically, providing
+the ability to hot plug/unplug objects in and out of the DPRC.
+
+A DPRC has a mappable MMIO region (an MC portal) that can be used
+to send MC commands. It has an interrupt for status events (like
+hotplug).
+
+All objects in a container share the same hardware "isolation context".
+This means that with respect to an IOMMU the isolation granularity
+is at the DPRC (container) level, not at the individual object
+level.
+
+DPRCs can be defined statically and populated with objects
+via a config file passed to the MC when firmware starts
+it. There is also a Linux user space tool called "restool"
+that can be used to create/destroy containers and objects
+dynamically.
+
+DPAA2 Objects for an Ethernet Network Interface
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+A typical Ethernet NIC is monolithic-- the NIC device contains TX/RX
+queuing mechanisms, configuration mechanisms, buffer management,
+physical ports, and interrupts. DPAA2 uses a more granular approach
+utilizing multiple hardware objects. Each object provides specialized
+functions. Groups of these objects are used by software to provide
+Ethernet network interface functionality. This approach provides
+efficient use of finite hardware resources, flexibility, and
+performance advantages.
+
+The diagram below shows the objects needed for a simple
+network interface configuration on a system with 2 CPUs.
+
+.. code-block:: console
+
+ +---+---+ +---+---+
+ CPU0 CPU1
+ +---+---+ +---+---+
+ | |
+ +---+---+ +---+---+
+ DPIO DPIO
+ +---+---+ +---+---+
+ \ /
+ \ /
+ \ /
+ +---+---+
+ DPNI --- DPBP,DPMCP
+ +---+---+
+ |
+ |
+ +---+---+
+ DPMAC
+ +---+---+
+ |
+ port/PHY
+
+Below the objects are described. For each object a brief description
+is provided along with a summary of the kinds of operations the object
+supports and a summary of key resources of the object (MMIO regions
+and IRQs).
+
+DPMAC (Datapath Ethernet MAC): represents an Ethernet MAC, a
+hardware device that connects to an Ethernet PHY and allows
+physical transmission and reception of Ethernet frames.
+
+- MMIO regions: none
+- IRQs: DPNI link change
+- commands: set link up/down, link config, get stats, IRQ config, enable, reset
+
+DPNI (Datapath Network Interface): contains TX/RX queues,
+network interface configuration, and RX buffer pool configuration
+mechanisms. The TX/RX queues are in memory and are identified by
+queue number.
+
+- MMIO regions: none
+- IRQs: link state
+- commands: port config, offload config, queue config, parse/classify config, IRQ config, enable, reset
+
+DPIO (Datapath I/O): provides interfaces to enqueue and dequeue
+packets and do hardware buffer pool management operations. The DPAA2
+architecture separates the mechanism to access queues (the DPIO object)
+from the queues themselves. The DPIO provides an MMIO interface to
+enqueue/dequeue packets. To enqueue something a descriptor is written
+to the DPIO MMIO region, which includes the target queue number.
+There will typically be one DPIO assigned to each CPU. This allows all
+CPUs to simultaneously perform enqueue/dequeued operations. DPIOs are
+expected to be shared by different DPAA2 drivers.
+
+- MMIO regions: queue operations, buffer management
+- IRQs: data availability, congestion notification, buffer pool depletion
+- commands: IRQ config, enable, reset
+
+DPBP (Datapath Buffer Pool): represents a hardware buffer
+pool.
+
+- MMIO regions: none
+- IRQs: none
+- commands: enable, reset
+
+DPMCP (Datapath MC Portal): provides an MC command portal.
+Used by drivers to send commands to the MC to manage
+objects.
+
+- MMIO regions: MC command portal
+- IRQs: command completion
+- commands: IRQ config, enable, reset
+
+Object Connections
+~~~~~~~~~~~~~~~~~~
+
+Some objects have explicit relationships that must
+be configured:
+
+- DPNI <--> DPMAC
+- DPNI <--> DPNI
+- DPNI <--> L2-switch-port
+
+A DPNI must be connected to something such as a DPMAC,
+another DPNI, or L2 switch port. The DPNI connection
+is made via a DPRC command.
+
+.. code-block:: console
+
+ +-------+ +-------+
+ | DPNI | | DPMAC |
+ +---+---+ +---+---+
+ | |
+ +==========+
+
+- DPNI <--> DPBP
+
+A network interface requires a 'buffer pool' (DPBP object) which provides
+a list of pointers to memory where received Ethernet data is to be copied.
+The Ethernet driver configures the DPBPs associated with the network
+interface.
+
+Interrupts
+~~~~~~~~~~
+
+All interrupts generated by DPAA2 objects are message
+interrupts. At the hardware level message interrupts
+generated by devices will normally have 3 components--
+1) a non-spoofable 'device-id' expressed on the hardware
+bus, 2) an address, 3) a data value.
+
+In the case of DPAA2 devices/objects, all objects in the
+same container/DPRC share the same 'device-id'.
+For ARM-based SoC this is the same as the stream ID.
+
+
+DPAA2 DPDK - Poll Mode Driver Overview
+--------------------------------------
+
+This section provides an overview of the drivers for
+DPAA2-- 1) the bus driver and associated "DPAA2 infrastructure"
+drivers and 2) functional object drivers (such as Ethernet).
+
+As described previously, a DPRC is a container that holds the other
+types of DPAA2 objects. It is functionally similar to a plug-and-play
+bus controller.
+
+Each object in the DPRC is a Linux "device" and is bound to a driver.
+The diagram below shows the dpaa2 drivers involved in a networking
+scenario and the objects bound to each driver. A brief description
+of each driver follows.
+
+.. code-block: console
+
+
+ +------------+
+ | DPDK DPAA2 |
+ | PMD |
+ +------------+ +------------+
+ | Ethernet |.......| Mempool |
+ . . . . . . . . . | (DPNI) | | (DPBP) |
+ . +---+---+----+ +-----+------+
+ . ^ | .
+ . | |<enqueue, .
+ . | | dequeue> .
+ . | | .
+ . +---+---V----+ .
+ . . . . . . . . . . .| DPIO driver| .
+ . . | (DPIO) | .
+ . . +-----+------+ .
+ . . | QBMAN | .
+ . . | Driver | .
+ +----+------+-------+ +-----+----- | .
+ | dpaa2 bus | | .
+ | VFIO fslmc-bus |....................|.....................
+ | | |
+ | /bus/fslmc | |
+ +-------------------+ |
+ |
+ ========================== HARDWARE =====|=======================
+ DPIO
+ |
+ DPNI---DPBP
+ |
+ DPMAC
+ |
+ PHY
+ =========================================|========================
+
+
+A brief description of each driver is provided below.
+
+DPAA2 bus driver
+~~~~~~~~~~~~~~~~
+
+The DPAA2 bus driver is a rte_bus driver which scans the fsl-mc bus.
+Key functions include:
+
+- Reading the container and setting up vfio group
+- Scanning and parsing the various MC objects and adding them to
+ their respective device list.
+
+Additionally, it also provides the object driver for generic MC objects.
+
+DPIO driver
+~~~~~~~~~~~
+
+The DPIO driver is bound to DPIO objects and provides services that allow
+other drivers such as the Ethernet driver to enqueue and dequeue data for
+their respective objects.
+Key services include:
+
+- Data availability notifications
+- Hardware queuing operations (enqueue and dequeue of data)
+- Hardware buffer pool management
+
+To transmit a packet the Ethernet driver puts data on a queue and
+invokes a DPIO API. For receive, the Ethernet driver registers
+a data availability notification callback. To dequeue a packet
+a DPIO API is used.
+
+There is typically one DPIO object per physical CPU for optimum
+performance, allowing different CPUs to simultaneously enqueue
+and dequeue data.
+
+The DPIO driver operates on behalf of all DPAA2 drivers
+active -- Ethernet, crypto, compression, etc.
+
+DPBP based Mempool driver
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The DPBP driver is bound to a DPBP objects and provides sevices to
+create a hardware offloaded packet buffer mempool.
+
+DPAA2 NIC Driver
+~~~~~~~~~~~~~~~~
+The Ethernet driver is bound to a DPNI and implements the kernel
+interfaces needed to connect the DPAA2 network interface to
+the network stack.
+
+Each DPNI corresponds to a DPDK network interface.
+
+Features
+^^^^^^^^
+
+Features of the DPAA2 PMD are:
+
+- Multiple queues for TX and RX
+- Receive Side Scaling (RSS)
+- Packet type information
+- Checksum offload
+- Promiscuous mode
+
+Supported DPAA2 SoCs
+--------------------
+
+- LS2080A/LS2040A
+- LS2084A/LS2044A
+- LS2088A/LS2048A
+- LS1088A/LS1048A
+
+Prerequisites
+-------------
+
+This driver relies on external libraries and kernel drivers for resources
+allocations and initialization. The following dependencies are not part of
+DPDK and must be installed separately:
+
+- **NXP Linux SDK**
+
+ NXP Linux software development kit (SDK) includes support for family
+ of QorIQ® ARM-Architecture-based system on chip (SoC) processors
+ and corresponding boards.
+
+ It includes the Linux board support packages (BSPs) for NXP SoCs,
+ a fully operational tool chain, kernel and board specific modules.
+
+ SDK and related information can be obtained from: `NXP QorIQ SDK <http://www.nxp.com/products/software-and-tools/run-time-software/linux-sdk/linux-sdk-for-qoriq-processors:SDKLINUX>`_.
+
+- **DPDK Helper Scripts**
+
+ DPAA2 based resources can be configured easily with the help of ready scripts
+ as provided in the DPDK helper repository.
+
+ `DPDK Helper Scripts <https://github.com/qoriq-open-source/dpdk-helper>`_.
+
+Currently supported by DPDK:
+
+- NXP SDK **2.0+**.
+- MC Firmware version **10.0.0** and higher.
+- Supported architectures: **arm64 LE**.
+
+- Follow the DPDK :ref:`Getting Started Guide for Linux <linux_gsg>` to setup the basic DPDK environment.
+
+Pre-Installation Configuration
+------------------------------
+
+Config File Options
+~~~~~~~~~~~~~~~~~~~
+
+The following options can be modified in the ``config`` file.
+Please note that enabling debugging options may affect system performance.
+
+- ``CONFIG_RTE_LIBRTE_FSLMC_BUS`` (default ``n``)
+
+ By default it is enabled only for defconfig_arm64-dpaa2-* config.
+ Toggle compilation of the ``librte_pmd_fslmcbus`` driver.
+
+- ``CONFIG_RTE_LIBRTE_DPAA2_PMD`` (default ``n``)
+
+ By default it is enabled only for defconfig_arm64-dpaa2-* config.
+ Toggle compilation of the ``librte_pmd_dpaa2`` driver.
+
+- ``CONFIG_RTE_LIBRTE_DPAA2_COMMON`` (default ``n``)
+
+ By default it is enabled only for defconfig_arm64-dpaa2-* config.
+ Toggle compilation of the ``librte_pmd_dpaa2_qbman``,
+ and ``librte_pmd_dpaa2_dpio`` driver.
+
+- ``CONFIG_RTE_LIBRTE_DPAA2_DEBUG_DRIVER`` (default ``n``)
+
+ Toggle display of generic debugging messages
+
+- ``CONFIG_RTE_LIBRTE_DPAA2_USE_PHYS_IOVA`` (default ``y``)
+
+ Toggle to use physical address vs virtual address for hardware accelerators.
+
+- ``CONFIG_RTE_LIBRTE_DPAA2_DEBUG_INIT`` (default ``n``)
+
+ Toggle display of initialization related messages.
+
+- ``CONFIG_RTE_LIBRTE_DPAA2_DEBUG_RX`` (default ``n``)
+
+ Toggle display of receive fast path run-time message
+
+- ``CONFIG_RTE_LIBRTE_DPAA2_DEBUG_TX`` (default ``n``)
+
+ Toggle display of transmit fast path run-time message
+
+- ``CONFIG_RTE_LIBRTE_DPAA2_DEBUG_TX_FREE`` (default ``n``)
+
+ Toggle display of transmit fast path buffer free run-time message
+
+
+Driver Compilation
+~~~~~~~~~~~~~~~~~~
+
+To compile the DPAA2 PMD for Linux arm64 gcc target, run the
+following ``make`` command:
+
+.. code-block:: console
+
+ cd <DPDK-source-directory>
+ make config T=arm64-dpaa2-linuxapp-gcc install
+
+.. _dpaa2_testpmd_example:
+
+Running testpmd
+~~~~~~~~~~~~~~~
+
+This section demonstrates how to launch ``testpmd`` with DPAA2 device
+managed by ``librte_pmd_dpaa2`` in the Linux operating system.
+
+#. Configure the resource container:
+
+ Configure resources in MC and create the DPRC container:
+
+ .. code-block:: console
+
+ export the DPRC container
+ e.g. export DPRCT=dprc.2
+
+#. Start ``testpmd`` with basic parameters:
+
+ .. code-block:: console
+
+ ./arm64-dpaa2-linuxapp-gcc/testpmd -c 0xff -n 1 \
+ -- -i --portmask=0x3 --nb-cores=1 --no-flush-rx
+
+ Example output:
+
+ .. code-block:: console
+
+ .....
+ EAL: Registered [pci] bus.
+ EAL: Registered [fslmc] bus.
+ EAL: Detected 8 lcore(s)
+ EAL: Probing VFIO support...
+ EAL: VFIO support initialized
+ .....
+ PMD: DPAA2: Processing Container = dprc.2
+ EAL: fslmc: DPRC contains = 51 devices
+ EAL: fslmc: Bus scan completed
+ .....
+ Configuring Port 0 (socket 0)
+ Port 0: 00:00:00:00:00:01
+ Configuring Port 1 (socket 0)
+ Port 1: 00:00:00:00:00:02
+ .....
+ Checking link statuses...
+ Port 0 Link Up - speed 10000 Mbps - full-duplex
+ Port 1 Link Up - speed 10000 Mbps - full-duplex
+ Done
+ testpmd>
+
+Limitations
+-----------
+
+Platform Requirement
+~~~~~~~~~~~~~~~~~~~~
+DPAA2 drivers for DPDK can only work on NXP SoCs as listed in the
+``Supported DPAA2 SoCs``.
+
+Maximum packet length
+~~~~~~~~~~~~~~~~~~~~~
+
+The DPAA2 SoC family support a maximum of a 10240 jumbo frame. The value
+is fixed and cannot be changed. So, even when the ``rxmode.max_rx_pkt_len``
+member of ``struct rte_eth_conf`` is set to a value lower than 10240, frames
+up to 10240 bytes can still reach the host interface.
diff --git a/doc/guides/nics/features/dpaa2.ini b/doc/guides/nics/features/dpaa2.ini
new file mode 100644
index 0000000..b2ad6ec
--- /dev/null
+++ b/doc/guides/nics/features/dpaa2.ini
@@ -0,0 +1,8 @@
+;
+; Supported features of the 'dpaa2' network poll mode driver.
+;
+; Refer to default.ini for the full list of available PMD features.
+;
+[Features]
+ARMv8 = Y
+Usage doc = Y
diff --git a/doc/guides/nics/index.rst b/doc/guides/nics/index.rst
index 92d56a5..fa01662 100644
--- a/doc/guides/nics/index.rst
+++ b/doc/guides/nics/index.rst
@@ -39,6 +39,7 @@ Network Interface Controller Drivers
bnx2x
bnxt
cxgbe
+ dpaa2
e1000em
ena
enic
diff --git a/doc/guides/rel_notes/release_17_02.rst b/doc/guides/rel_notes/release_17_02.rst
index d445d64..f3ab037 100644
--- a/doc/guides/rel_notes/release_17_02.rst
+++ b/doc/guides/rel_notes/release_17_02.rst
@@ -57,6 +57,17 @@ New Features
Six new APIs have been added to the ixgbe PMD for MACsec offload support.
The declarations for the APIs can be found in ``rte_pmd_ixgbe.h``.
+* **Added a new driver for NXP DPAA2 - FSLMC bus.**
+
+ Added the new bus "fslmc" driver for NXP DPAA2 devices. See the
+ "Network Interface Controller Drivers" document for more details on this new
+ driver.
+
+* **Added a new driver for NXP DPAA2 Network PMD.**
+
+ Added the new "dpaa2" net driver for NXP DPAA2 devices. See the
+ "Network Interface Controller Drivers" document for more details on this new
+ driver.
Resolved Issues
---------------
--
1.9.1