From: Kumar Gala <galak@kernel.crashing.org>
To: Emil Medve <Emilian.Medve@freescale.com>
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Igal Liberman <Igal.Liberman@freescale.com>
Subject: Re: [PATCH 1/7] soc/fman: Add the FMan FLIB headers
Date: Fri, 6 Mar 2015 10:32:18 -0600 [thread overview]
Message-ID: <6250951C-902C-49D3-9730-756EE611AF3B@kernel.crashing.org> (raw)
In-Reply-To: <1425534351-1065-2-git-send-email-Emilian.Medve@Freescale.com>
On Mar 4, 2015, at 11:45 PM, Emil Medve <Emilian.Medve@freescale.com> =
wrote:
> From: Igal Liberman <Igal.Liberman@freescale.com>
>=20
> The Freescale Data Path Acceleration Architecture (DPAA) is a set of
> hardware components on specific QorIQ P and T series multicore =
processors.
> This architecture provides the infrastructure to support simplified
> sharing of networking interfaces and accelerators by multiple CPU =
cores,
> and the accelerators themselves.
>=20
> One of the DPAA accelerators is the Frame Manager (FMan), which
> combines the Ethernet network interfaces with packet distribution
> logic to provide intelligent distribution and queuing decisions for
> incoming traffic at line rate.
>=20
> This patch presents the FMan Foundation Libraries (FLIB) headers.
> The FMan FLIB suite adds basic support for the DPAA FMan hardware =
register access.
> The FMan FLIB suite is used in Freescale's SDK Releases.
>=20
> Signed-off-by: Igal Liberman <Igal.Liberman@freescale.com>
> ---
> drivers/soc/fsl/fman/flib/common/general.h | 45 +
> drivers/soc/fsl/fman/flib/fman_common.h | 74 ++
> drivers/soc/fsl/fman/flib/fsl_enet.h | 276 ++++++
> drivers/soc/fsl/fman/flib/fsl_fman.h | 801 =
+++++++++++++++
> drivers/soc/fsl/fman/flib/fsl_fman_dtsec.h | 1017 =
++++++++++++++++++++
> drivers/soc/fsl/fman/flib/fsl_fman_dtsec_mii_acc.h | 104 ++
> drivers/soc/fsl/fman/flib/fsl_fman_kg.h | 506 ++++++++++
> drivers/soc/fsl/fman/flib/fsl_fman_memac.h | 492 ++++++++++
> drivers/soc/fsl/fman/flib/fsl_fman_memac_mii_acc.h | 77 ++
> drivers/soc/fsl/fman/flib/fsl_fman_port.h | 602 ++++++++++++
> drivers/soc/fsl/fman/flib/fsl_fman_prs.h | 106 ++
> drivers/soc/fsl/fman/flib/fsl_fman_rtc.h | 415 ++++++++
> drivers/soc/fsl/fman/flib/fsl_fman_sp.h | 133 +++
> drivers/soc/fsl/fman/flib/fsl_fman_tgec.h | 484 ++++++++++
> 14 files changed, 5132 insertions(+)
> create mode 100644 drivers/soc/fsl/fman/flib/common/general.h
> create mode 100644 drivers/soc/fsl/fman/flib/fman_common.h
> create mode 100644 drivers/soc/fsl/fman/flib/fsl_enet.h
> create mode 100644 drivers/soc/fsl/fman/flib/fsl_fman.h
> create mode 100644 drivers/soc/fsl/fman/flib/fsl_fman_dtsec.h
> create mode 100644 drivers/soc/fsl/fman/flib/fsl_fman_dtsec_mii_acc.h
> create mode 100644 drivers/soc/fsl/fman/flib/fsl_fman_kg.h
> create mode 100644 drivers/soc/fsl/fman/flib/fsl_fman_memac.h
> create mode 100644 drivers/soc/fsl/fman/flib/fsl_fman_memac_mii_acc.h
> create mode 100644 drivers/soc/fsl/fman/flib/fsl_fman_port.h
> create mode 100644 drivers/soc/fsl/fman/flib/fsl_fman_prs.h
> create mode 100644 drivers/soc/fsl/fman/flib/fsl_fman_rtc.h
> create mode 100644 drivers/soc/fsl/fman/flib/fsl_fman_sp.h
> create mode 100644 drivers/soc/fsl/fman/flib/fsl_fman_tgec.h
1. this is way to big of patch to reasonable review
2. can some of these headers be associated with the code patches that =
use them instead
>=20
> diff --git a/drivers/soc/fsl/fman/flib/common/general.h =
b/drivers/soc/fsl/fman/flib/common/general.h
> new file mode 100644
> index 0000000..e5f56af
> --- /dev/null
> +++ b/drivers/soc/fsl/fman/flib/common/general.h
> @@ -0,0 +1,45 @@
> +/*
> + * Copyright 2008-2015 Freescale Semiconductor Inc.
> + *
> + * 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 Freescale Semiconductor nor the
> + * names of its contributors may be used to endorse or promote =
products
> + * derived from this software without specific prior written =
permission.
> + *
> + *
> + * ALTERNATIVELY, this software may be distributed under the terms of =
the
> + * GNU General Public License ("GPL") as published by the Free =
Software
> + * Foundation, either version 2 of that License or (at your option) =
any
> + * later version.
> + *
> + * THIS SOFTWARE IS PROVIDED BY Freescale Semiconductor ``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 Freescale Semiconductor 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.
> + */
> +
> +#ifndef __GENERAL_H
> +#define __GENERAL_H
> +
> +#include <linux/types.h>
> +#include <linux/io.h>
> +
> +#define UNUSED(X) (X =3D X)
Don=92t we already have a kernel mechanism to mark something unused for =
gcc to be quiet?
> +#define KILOBYTE 0x400UL /* 1024 */
Really? I saw one usage, in which you could easily do (5 * 1024).
> +
> +#define iowrite32be(val, addr) out_be32(&(*addr), val)
> +#define ioread32be(addr) in_be32(&(*addr))
> +
> +#endif /* __GENERAL_H */
- k=
next prev parent reply other threads:[~2015-03-06 16:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 5:45 [PATCH 0/7] Freescale DPAA FMan FLIB(s) Emil Medve
2015-03-05 5:45 ` [PATCH 1/7] soc/fman: Add the FMan FLIB headers Emil Medve
2015-03-06 16:32 ` Kumar Gala [this message]
2015-03-05 5:45 ` [PATCH 2/7] soc/fman: Add the FMan FLIB Emil Medve
2015-03-07 0:57 ` Scott Wood
2015-03-05 5:45 ` [PATCH 3/7] soc/fman: Add the FMan port FLIB Emil Medve
2015-03-05 5:45 ` [PATCH 4/7] soc/fman: Add the FMan MAC FLIB Emil Medve
2015-03-05 5:45 ` [PATCH 5/7] soc/fman: Add the FMan parser and KeyGen FLIB(s) Emil Medve
2015-03-05 5:45 ` [PATCH 6/7] soc/fman: Add the FMan RTC FLIB Emil Medve
2015-03-05 5:45 ` [PATCH 7/7] soc/fman: Add the FMan SP FLIB Emil Medve
2015-03-05 12:32 ` [PATCH 0/7] Freescale DPAA FMan FLIB(s) Jamal Hadi Salim
2015-03-05 13:48 ` Emil Medve
2015-03-05 14:35 ` Jamal Hadi Salim
2015-03-05 15:04 ` Emil Medve
2015-03-06 15:09 ` Jamal Hadi Salim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6250951C-902C-49D3-9730-756EE611AF3B@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=Emilian.Medve@freescale.com \
--cc=Igal.Liberman@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).