From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <shreyansh.jain@nxp.com>
Received: from NAM01-BY2-obe.outbound.protection.outlook.com
(mail-by2nam01on0081.outbound.protection.outlook.com [104.47.34.81])
by dpdk.org (Postfix) with ESMTP id 520325592
for <dev@dpdk.org>; Thu, 29 Dec 2016 06:14:30 +0100 (CET)
Received: from BN6PR03CA0045.namprd03.prod.outlook.com (10.175.124.31) by
BN6PR03MB2466.namprd03.prod.outlook.com (10.168.223.20) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id
15.1.817.10; Thu, 29 Dec 2016 05:14:28 +0000
Received: from BY2FFO11OLC003.protection.gbl (2a01:111:f400:7c0c::112) by
BN6PR03CA0045.outlook.office365.com (2603:10b6:404:10c::31) with Microsoft
SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.817.10 via
Frontend Transport; Thu, 29 Dec 2016 05:14:28 +0000
Authentication-Results: spf=fail (sender IP is 192.88.158.2)
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.158.2 as permitted sender) receiver=protection.outlook.com;
client-ip=192.88.158.2; helo=az84smr01.freescale.net;
Received: from az84smr01.freescale.net (192.88.158.2) by
BY2FFO11OLC003.mail.protection.outlook.com (10.1.15.183) with Microsoft SMTP
Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.789.10
via Frontend Transport; Thu, 29 Dec 2016 05:14:25 +0000
Received: from Tophie.ap.freescale.net ([10.232.14.87])
by az84smr01.freescale.net (8.14.3/8.14.0) with ESMTP id uBT5DOHj010218;
Wed, 28 Dec 2016 22:14:22 -0700
From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: <dev@dpdk.org>
CC: <thomas.monjalon@6wind.com>, <bruce.richardson@intel.com>,
<john.mcnamara@intel.com>, <ferruh.yigit@intel.com>,
<jerin.jacob@caviumnetworks.com>, Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Thu, 29 Dec 2016 10:46:22 +0530
Message-ID: <1482988612-6638-4-git-send-email-shreyansh.jain@nxp.com>
X-Mailer: git-send-email 2.7.4
In-Reply-To: <1482988612-6638-1-git-send-email-shreyansh.jain@nxp.com>
References: <1482180853-18823-1-git-send-email-hemant.agrawal@nxp.com>
<1482988612-6638-1-git-send-email-shreyansh.jain@nxp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-EOPAttributedMessage: 0
X-Matching-Connectors: 131274620684133037;
(91ab9b29-cfa4-454e-5278-08d120cd25b8); ()
X-Forefront-Antispam-Report: CIP:192.88.158.2; IPV:NLI; CTRY:US; EFV:NLI;
SFV:NSPM;
SFS:(10009020)(6009001)(7916002)(336005)(39410400002)(39840400002)(39400400002)(39450400003)(39860400002)(39380400002)(39850400002)(2980300002)(1109001)(1110001)(339900001)(189002)(199003)(36756003)(105606002)(106466001)(2906002)(33646002)(4326007)(85426001)(97736004)(189998001)(47776003)(23676002)(50466002)(2351001)(76176999)(50986999)(92566002)(69596002)(104016004)(68736007)(86362001)(110136003)(5660300001)(8936002)(356003)(81166006)(38730400001)(8656002)(8676002)(50226002)(81156014)(5820100001)(626004)(77096006)(6916009)(31430400001)(2950100002)(2870700001)(305945005)(7059030);
DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR03MB2466; H:az84smr01.freescale.net; FPR:;
SPF:Fail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en;
X-Microsoft-Exchange-Diagnostics: 1; BY2FFO11OLC003;
1:2Lt8aYld95wsT9pcrZEgDqEttolAtJtCBp6SYzsh/B/8NcJnAuIzXpml+oDodZ2/6PrKeNLCdYRtKg1JQfBhakpVcEBrdUymV7iVEMHMMhrlnkQZHLl8V0+efZqr+QWHemWOVUZFuetej/QSp2gP04Tnp8C3Dy10ZlgU2RLRu8FxDlPJWywbTLgKp8T0ahYKAS2DhfNeeK0bgAxv1Hrm/YwL6eTG8LZynzbc7JaDLkV2MiJzaXGHeqpljSYXJByiDiDOYzCW+wXZSBcWvM6pJI0kezEIKAg+Y+wfwSthBcO21fVN5eMOEkD6W1tPhGwTDSgd11dh46nnnnYTfoeR1fruGY2EfITMyFH1MU7z5hhWJS99pFF91E24cKLMGCcDSulvmm3YvZGj0o4TWfDdTDbl5uzjKKmq2d0OPnNZsbFfcJWnH/wPaOyGwgxZ3Cm6bffm7ToS/xb+aCRbpB808SFPZZxi2lilqDbTQ5aGxifPVCZPm61VEOOI+twcuIpk+OCd36xthW/dhxRM3z0OKsTjUB4lCizItXJpObHbfjwd1uzrslAhGoU1XSkUiOTg3nyyVlkVU80ZsMEpZW3Yxl93sr7LR0iOhZ/rf3R8kDHghUJDQK7KtCNT9l+LtUR2nN9px4CNkavHxtwsF1Ex2dMOdHs86cS+uaXbgTNSxjEeqsuI71fVpyGpcnaZHMopprT28nR6nYjYGM5oUaAEhLycKmSnJsjEHMyNR5ivH8yC17JAAbNkpEljSezYJ5kTxq67sdDReLMZPIpYcBLRnw==
X-MS-Office365-Filtering-Correlation-Id: 4028d145-d04a-442c-d7c5-08d42fa9904a
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:BN6PR03MB2466;
X-Microsoft-Exchange-Diagnostics: 1; BN6PR03MB2466;
3:j4DktYAvAW6gSJWti3YO7P0gVPhPiJuKhOh6mLE4PRLTrKXq4ZhcSgt9ubMh4z/2EnCmSfimgOFeN5ZvFXSrSXDpCosGxji2RYU+2g4+MV0UCTxhXlTIZowlha2NYsT6+E6zseGjpDJeUVy65PuPlZlXFVnsvJJVEJO8JXID6kgi/TXG2wRXVn1YGz7X1nI2C5KYbw60UcS8yuDNhHE50oshkXUv8WImxvD9CDiZStRFvrmqzK2in8cRy4ilsvThmhc9WAKxUrHJZV069y5mptvgW1fV4O97dDrbezQDyqOuglptfcHGOSz3twQTJ3/I8GGiwgF+YykaGRBa71C2K+dIAmMr1eUKAVlWqPy8n8E=;
25:OCRhZRl2TJWamlvtK57ZAHFtq0QFBcmELbrmw0K62CbN40mu1dpQD1+zg7fC+phHoIB7I0SIi65P2aCW7iObBcsePyYy2mtNXLPg1dqL/ECrMeCAvtGKrqcwwpDgA+ZRFgXjbWAHacXxDLNvDtygOaJTw3fz+GPM5hu7i5oZ43ETVANfQ4PDhX7qsO4qHR4PSt6mPGjcSAvhWp9NOZbWxP/0WIJEl1NlwLw8B5t6uOWQ39G1Wyk7HVNvhz70P2eU873NtkQwBCf/cCIZTrrY78Ux8nHpggOqBj0GccBrmEcLxsJgMJjfdZwnHzB80iQAWxYEYE+PhJRbbcV7QkQthlZkf64MJFKvgUkkMXlPh9nQaIADXENS+LMSVqaXWCct5b1hYN/InOSS9R7ZtwkVBznC5FMYv8FxN5yuWy7gFAkonVJ/3Kl+7p+e8EBJztTHXkIZQlN7we3xO46lKEZfRw==
X-Microsoft-Exchange-Diagnostics: 1; BN6PR03MB2466;
31:rW+VCbyddEvO+H/Iiy6HUCkA3L9+A/46UfOjwBcs+mzFn05iy6Kf1PmVeci/cDYLYYIGiSqSOqUTJ6zvFSByZYyl/EW3GA4vO0wwzNFF74FPjGLfsKCryZcT6r1vXEckV8H0Ccz/IkVab/DRNSynTT8d8CWqwOsJbcTdylCJs6ELyU2qvdSeDKxCHBunh8NAxa8pVco65TCK8T3+ydEFF3OFNjzLqIQlDhh3Wuo2YBJHRm8dwHYzC0+6ObFDCdEFiW8IZvS2Cm3DBO4dAT4Fnw==
X-Microsoft-Antispam-PRVS: <BN6PR03MB2466369224D47F7F19A491F7906B0@BN6PR03MB2466.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)(13024025)(13023025)(13015025)(13017025)(13018025)(8121501046)(5005006)(3002001)(10201501046)(6055026)(6096035)(20161123561025)(20161123559025)(20161123556025)(20161123565025)(20161123563025);
SRVR:BN6PR03MB2466; BCL:0; PCL:0; RULEID:(400006); SRVR:BN6PR03MB2466;
X-Microsoft-Exchange-Diagnostics: 1; BN6PR03MB2466;
4:y5QGYAdguA/mchjl7nvZ317faVwk4jFplnkqcmGelGRFjHlAJ/LJfe1uyXN03OOA+Q8T72l7BzdTw/q3dd66yUHo/elXJw0u9gUaJdfbz28kr4vWGV/CKxr1+bLb46QImztJVEiQ4YLl/S2o+F/qmiDxsURGMNQRuY88hQlYZMaskhMZfv+01lqelqw5Fd4LLLycqww/YlK/EOiMF1yxey6p0wHJ6SEXnlJD5P9JT3bXgKg2K0bJoT7d+hq4uWTyA31nSGZYNbWIJMhQI0rV2I1tK3NYkUaxUNyMOcfy1gFiwSPcq4e2wpjUBZI0IQeBhfPCi+N4vHyAMuN3Q4694dM3up2wVODwY+Z/gK43WmJS3YI4iN64YtiOyT40BiR7HA0SrRGlqz46rCzKRflUPxS6vVZdMPFZjWXmpm9t0zgwVFYz9cFNTPUuu2HFIL2K35Zdbl4fT3sLKMlqjqHHqNB9naeLXPQ2GFSuAPBe3Aan4qTCWhYkpbPBpwJhdRTFYzeTtebdw9dYDz1j5G/LMhL+NT465noXq2PWMhXCyZ/gcT8ELf0ZpZOKKm+sguqWKLT44OLR5FEVBDUXoMPXkuGwDvOykUPbpVdC7UWVLrG62efkPCzFNLDjaWnF5r9CSjkVhUl5hfusBqDjkmWZq8JmoAqlTVM/ABXtEN3xuO82jVe5VEyJNCZYesQ0dFo9E5RbTc/g5qaxhktHI1lANC4EIxYvnzYj+M87/ofWgb7f7nd5zX76plSwxFvPtRGuxQMrWrzjErl5LLyqPAylc6xsGy5iL7TEHwQr7kCS3Rs7STVXE0Mzga1bo2csGwo1CfPWDy4I9JdTfACwopCrx1/FToRh5jMX9eqkMR1k3vos76rBm4SzbQrQIkAnNq+Rt/km5S3FDsw/DSiP12OItHm3yBSkxNggwHSfruleCdI=
X-Forefront-PRVS: 01713B2841
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCTjZQUjAzTUIyNDY2OzIzOklwcm92VFVWUEZmS0QrT2hzZzN4NXpLZVYx?=
=?utf-8?B?OTFXd2RydmhaVFVZRXcwMWIvSGhDUE1OTXN4Y2RwV2tWZWNOdjVRU2pqc2kv?=
=?utf-8?B?UG4rUmdWMWtYUWxaTHR3OGs2SHlvZVhrTE9iTXNEaFpVY09lNHM1eVlCUmc0?=
=?utf-8?B?b3ZKR2EwZ1RaWkJsUjJRZGpNN1hTTk1wRFV3VktjZmEwb3ZydW81dFZ0RFJD?=
=?utf-8?B?RThjOXB0SHpFV016ZWRRUmYwbFY2K3ZuZlc2TUZnQ3FaNXdCeUlhSFlZbkpZ?=
=?utf-8?B?SUFjV3lmWW9URzl2VDYvTmVtWWxFTHRTT3NQY2wvOVM1SjQ3b09Rc1J3TUor?=
=?utf-8?B?WjNucU83VzlUcllSSGEwYU9FN1FqYklCbHBGTkFPOVNEbTdXZUQ4VGRKMkl5?=
=?utf-8?B?OTlQSG1QcjNGczFTbExpUmMrblRuSVhJU3lvUWZyTVF5aUFydVJwS3hqWnZC?=
=?utf-8?B?dGoxUm9nOEJTOU0wNVRoWFRWUy9PUGkwY0hiWlZXKzNNb1plZmtmRkl1NXN0?=
=?utf-8?B?Skd3L2k5ZjFkdnJEZUQwdVRvL2FDdEJLemU1cTAvOGNlM2hiSzE2OXc4ODZp?=
=?utf-8?B?anRndlZpZDQ4RGpOY0ZWbWZQdUtqcjU5ZWIwNVBMbWtiL0Zid05lUWlXY3I2?=
=?utf-8?B?VWg2VmZVNWVXK055aXZ0KzRTNE43K093dGtvUlNnT1hPWGIvc0MwcElMNHlz?=
=?utf-8?B?UUIyYlRqbFh4SXV1WjI3eXptMnVyQ21aQk12c3M5ZFpMSXVxV1hVMWZLeFlR?=
=?utf-8?B?TjdsbEtrSXhDa2dGV1dKZGJQY2xyTUwyTmt1WS84Y0MxZDRXUCtzRmRxNzh4?=
=?utf-8?B?RVE4R1lQa1hyQlJCR0dTeklOS3J4cWx0WlZzUXdvTnprRitGWjRPZTRpUjlu?=
=?utf-8?B?S3VldkpMenF3NTR3MlFNNEdoZ1NwdjVHVDVmZVNSc1RrYWlsOCs4clBmZGFj?=
=?utf-8?B?QXg1Wkc5MkVzWDZWbUdsZFBQbTJmMi9LM09nY0ovZTZnT21KWGoxb29SY21j?=
=?utf-8?B?eWhsamVDZ3B6ZmhzdlJsKytBdzdPeXBsMHBMYzFkc1l4ZGNvUmoxemc4bS8r?=
=?utf-8?B?OUdvZ1EzM1NZTmNEcXhGUkwxS3d4TWYwWWNwRGVDNS9QSkZRYmJxSlJrcWRy?=
=?utf-8?B?KzdmcitaaHNNSk52b1A3dnRwZCtxSGlYQjNDZ1ZjOE1UWkw1UGs0Smwycm9R?=
=?utf-8?B?MnM2L3dQQ2Z0Wlg0ZEc3SGRwMVV0UzJuSEpiV1huRXYvUzBLUk4zZVdYNmFq?=
=?utf-8?B?cU1qSHdWQmJiK0xacklKWTMyUlk2b0pLZDdDbkxNWmtxZnZLWmw3U1c5djcy?=
=?utf-8?B?MmhaWFJnRWZzS0JDOUZuZWR3cmtvTThlTWs3M0VDenhaeDlDT24vS1oxWnN0?=
=?utf-8?B?OEFxTTlqS1BrdFROUk1nVFJUOWw5VGMvVWdGMWNKK200L1hCM2ZweHRkdUVv?=
=?utf-8?B?dTVFdGEvakpGNmJYZDNKVDhYSW5lMmllbkIxaGxsamduV3ZlU0hmQVlTMEth?=
=?utf-8?B?N2pUaVZGZlpZWEJBd1pXMjl1VGQxMjhUVHVlWGZvdTVvaFpxY2F0WWdNaFlU?=
=?utf-8?B?STVRZ1hXWHloNitUY3FUOFVEMm5uRDRhbnpjdzBLRXNVRkJrUVNuZFAyQW4r?=
=?utf-8?B?ZnpNa21aY0M0TXFJdGhaY3A4dWRuREMvcmhXNU9wMndCK3JtdmFYVVkrbG5k?=
=?utf-8?B?SnF6bGlGRS85dGFDNTI0cDB1TGZpS0g4aUNJMTBMdHBEdGxUL1ZSR1F5MzFn?=
=?utf-8?B?RWI5M1BFY3kyUmJkN0ppaWMxUGx0L29Yc0hPdXkwNG5Nd3JMUDl6L2lzOUEw?=
=?utf-8?Q?/02MR9LRij2sC?=
X-Microsoft-Exchange-Diagnostics: 1; BN6PR03MB2466;
6:EQmU3lBuhiwq/NmbNGzQJJrwO0hXRMuWM0MoQya+YcwdWNUKWlk/VO9SA64Jpwl0wCOJBrKVHgzemtAmuqZe8RfE1rwUKc0LsXx/q486Rnt0gNjjOuxC0ipN6pKpN9yGfWYXy6gdVVVaSJprScz0LOqV8oyEVkfJfWD24OY0KvXWH82k8bYwDzC1PEoOn6QNvFRxq8BPK6s9539UtjVLCdNo1djmPfU9pSFfBFLJImFCxmUiaBldUx6GyYoSyLSt+FxcIqdzWtFf4ckqxQkXojV6RXamoGQ3NHbKycrQmPekaWDHF1xYh4Yl5QiI8PSp5hnhxy4C0FgeemPo/fgao33gCFx2V0zGbOVAK+JHY293yLPgRbjjffrwAt+2hOdbFmDk/g9AyTgeYKMVkSfTSJ47LT2s5eG9jsTrj80rvkmuFpIwDjp8IiaPeLx9YzgR;
5:DNKx1KuGREK9ZhhNE8yd0S+Ipnquqe4jIbHmyKsfc/OF9Ue2eyH3jzOq69ZHMPoVUk1Vg+gMhVqKG7XglpUI2qeLsjbdUs+Lvu9C3fb8fjMwd/8SE5MBgkpvLOmcxpivHK3KdxbK8xZTksAokWYcdcKfEQPueHWehUipyUp1KR72uGSvi+ookzGhXzzV316G;
24:u6N2FZtgoYHP7e2Uk8wDOOn7B+qm2/AhvToh8imgabcqCCrVtgPq6GW5tL9+jELQNWzbJrQUVgr7XrREeXl0R0lGURUq1BniOjfLhuRdxzc=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; BN6PR03MB2466;
7:+CfVjrB38WyHJ0NbwnsZWH9cgXBQsu171idpmroI7ibkTAhs4s98ut5KfSWtaRAxk+hsSavJIGFR8BszbenioAk0JZ5g+Mq0OGk98+HKzn6OHKJ/vwLotvNe+4zi3dmfu7SJdjn71GlB29YJpcjQ5eJde6yq4RFPiVPyzPMYdkJ4ASepW4U/iRlgh/G/rzlgOGIEdwZYtjHk+CskyWuLomK9nXkSC89rxma9t7mrXWdK3gXoRxQ1kZqlJOdyelVuoco++0R1W4H4NVWhjTGm+sFvfYdeA+NaHYAx/+PBDH2S1DN2EdOaRu+XNkQ426IiWLprytNM8irYv859CCIk7IkWKRjiG3KPg67IoNge60Qy7i/AiKfOSQP/IPr5awHDZ+usmvZDuTcVauu+eG3tuym2K4tz4dD2SIleIno1mSXYrAV1JFH7o3TRFEQ3xoXOu8tT5WWsgZ0pC23h2YC+FQ==
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 29 Dec 2016 05:14:25.7145 (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.158.2];
Helo=[az84smr01.freescale.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR03MB2466
Subject: [dpdk-dev] [PATCH v3 03/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: Thu, 29 Dec 2016 05:14:31 -0000
From: Hemant Agrawal <hemant.agrawal@nxp.com>
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 ebc97b8..04c4e39 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 180af82..b2e9110 100644
--- a/doc/guides/rel_notes/release_17_02.rst
+++ b/doc/guides/rel_notes/release_17_02.rst
@@ -52,6 +52,17 @@ New Features
See the :ref:`Generic flow API <Generic_flow_API>` documentation for more
information.
+* **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
---------------
--
2.7.4