From: Leon Romanovsky <leon@kernel.org>
To: M Chetan Kumar <m.chetan.kumar@intel.com>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
johannes@sipsolutions.net, krishna.c.sudi@intel.com,
linuxwwan@intel.com
Subject: Re: [PATCH V2 01/16] net: iosm: entry point
Date: Wed, 21 Apr 2021 08:44:55 +0300 [thread overview]
Message-ID: <YH+71wFykp/fWcCe@unreal> (raw)
In-Reply-To: <20210420161310.16189-2-m.chetan.kumar@intel.com>
On Tue, Apr 20, 2021 at 09:42:55PM +0530, M Chetan Kumar wrote:
> 1) Register IOSM driver with kernel to manage Intel WWAN PCIe
> device(PCI_VENDOR_ID_INTEL, INTEL_CP_DEVICE_7560_ID).
> 2) Exposes the EP PCIe device capability to Host PCIe core.
> 3) Initializes PCIe EP configuration and defines PCIe driver probe, remove
> and power management OPS.
> 4) Allocate and map(dma) skb memory for data communication from device to
> kernel and vice versa.
>
> Signed-off-by: M Chetan Kumar <m.chetan.kumar@intel.com>
> ---
> v2:
> * Implement module_init() & exit() callbacks for rtnl_link.
> * Documentation correction for function signature.
> * Fix coverity warnings.
> ---
> drivers/net/wwan/iosm/iosm_ipc_pcie.c | 588 ++++++++++++++++++++++++++
> drivers/net/wwan/iosm/iosm_ipc_pcie.h | 211 +++++++++
> 2 files changed, 799 insertions(+)
> create mode 100644 drivers/net/wwan/iosm/iosm_ipc_pcie.c
> create mode 100644 drivers/net/wwan/iosm/iosm_ipc_pcie.h
>
> diff --git a/drivers/net/wwan/iosm/iosm_ipc_pcie.c b/drivers/net/wwan/iosm/iosm_ipc_pcie.c
> new file mode 100644
> index 000000000000..8a3a8cd68a6a
> --- /dev/null
> +++ b/drivers/net/wwan/iosm/iosm_ipc_pcie.c
> @@ -0,0 +1,588 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Copyright (C) 2020-21 Intel Corporation.
> + */
> +
> +#include <linux/acpi.h>
> +#include <linux/bitfield.h>
> +#include <linux/module.h>
> +#include <net/rtnetlink.h>
> +
> +#include "iosm_ipc_imem.h"
> +#include "iosm_ipc_pcie.h"
> +#include "iosm_ipc_protocol.h"
> +
> +#define DRV_AUTHOR "Intel Corporation <linuxwwan@intel.com>"
Driver author can't be a company. It needs to be a person.
Thanks
next prev parent reply other threads:[~2021-04-21 5:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 16:12 [PATCH V2 00/16] net: iosm: PCIe Driver for Intel M.2 Modem M Chetan Kumar
2021-04-20 16:12 ` [PATCH V2 01/16] net: iosm: entry point M Chetan Kumar
2021-04-21 5:44 ` Leon Romanovsky [this message]
2021-04-21 6:51 ` Johannes Berg
2021-04-21 8:03 ` Leon Romanovsky
2021-04-20 16:12 ` [PATCH V2 02/16] net: iosm: irq handling M Chetan Kumar
2021-04-20 23:48 ` David Miller
2021-04-20 16:12 ` [PATCH V2 03/16] net: iosm: mmio scratchpad M Chetan Kumar
2021-04-20 16:12 ` [PATCH V2 04/16] net: iosm: shared memory IPC interface M Chetan Kumar
2021-04-20 16:12 ` [PATCH V2 05/16] net: iosm: shared memory I/O operations M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 06/16] net: iosm: channel configuration M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 07/16] net: iosm: mbim control device M Chetan Kumar
2021-05-06 9:25 ` Loic Poulain
2021-05-06 10:44 ` Kumar, M Chetan
2021-05-06 14:09 ` Dan Williams
2021-04-20 16:13 ` [PATCH V2 08/16] net: iosm: bottom half M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 09/16] net: iosm: multiplex IP sessions M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 10/16] net: iosm: encode or decode datagram M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 11/16] net: iosm: power management M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 12/16] net: iosm: shared memory protocol M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 13/16] net: iosm: protocol operations M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 14/16] net: iosm: uevent support M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 15/16] net: iosm: net driver M Chetan Kumar
2021-04-20 16:13 ` [PATCH V2 16/16] net: iosm: infrastructure M Chetan Kumar
2021-04-20 18:08 ` Randy Dunlap
2021-05-06 8:54 ` [PATCH V2 00/16] net: iosm: PCIe Driver for Intel M.2 Modem Aleksander Morgado
2021-05-06 10:51 ` Kumar, M Chetan
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=YH+71wFykp/fWcCe@unreal \
--to=leon@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=krishna.c.sudi@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwwan@intel.com \
--cc=m.chetan.kumar@intel.com \
--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).