dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peng Ma <peng.ma@nxp.com>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: Vinod Koul <vkoul@kernel.org>,
	"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	Leo Li <leoyang.li@nxp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>
Subject: RE: [EXT] Re: [V5 1/2] dmaengine: fsl-dpaa2-qdma: Add the DPDMAI(Data Path DMA Interface) support
Date: Tue, 22 Oct 2019 10:19:18 +0000	[thread overview]
Message-ID: <VI1PR04MB443121007853185039A65534ED680@VI1PR04MB4431.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CADYN=9JkQMawVnLoJ8sXAbV8NB_BK0zQA0PomJ583Agj12r8Cg@mail.gmail.com>

Hi Anders && Viod,

I sent v6 patch to fix the build error, please check.
Patchwork link:
https://patchwork.kernel.org/project/linux-dmaengine/list/?series=191397

Best Regards,
Peng
>-----Original Message-----
>From: Anders Roxell <anders.roxell@linaro.org>
>Sent: 2019年10月22日 17:27
>To: Peng Ma <peng.ma@nxp.com>
>Cc: Vinod Koul <vkoul@kernel.org>; dan.j.williams@intel.com; Leo Li
><leoyang.li@nxp.com>; linux-kernel@vger.kernel.org;
>dmaengine@vger.kernel.org
>Subject: Re: [EXT] Re: [V5 1/2] dmaengine: fsl-dpaa2-qdma: Add the
>DPDMAI(Data Path DMA Interface) support
>
>Caution: EXT Email
>
>On Thu, 17 Oct 2019 at 08:16, Peng Ma <peng.ma@nxp.com> wrote:
>>
>> Hi Vinod,
>>
>> Thanks very much for your reply.
>>
>> Best Regards,
>> Peng
>> >-----Original Message-----
>> >From: Vinod Koul <vkoul@kernel.org>
>> >Sent: 2019年10月17日 12:11
>> >To: Peng Ma <peng.ma@nxp.com>
>> >Cc: dan.j.williams@intel.com; Leo Li <leoyang.li@nxp.com>;
>> >linux-kernel@vger.kernel.org; dmaengine@vger.kernel.org
>> >Subject: [EXT] Re: [V5 1/2] dmaengine: fsl-dpaa2-qdma: Add the
>> >DPDMAI(Data Path DMA Interface) support
>> >
>> >Caution: EXT Email
>> >
>> >On 30-09-19, 02:04, Peng Ma wrote:
>> >> The MC(Management Complex) exports the DPDMAI(Data Path DMA
>> >Interface)
>> >> object as an interface to operate the DPAA2(Data Path Acceleration
>> >> Architecture 2) qDMA Engine. The DPDMAI enables sending frame-based
>> >> requests to qDMA and receiving back confirmation response on
>> >> transaction completion, utilizing the DPAA2 QBMan(Queue Manager and
>> >> Buffer Manager
>> >> hardware) infrastructure. DPDMAI object provides up to two
>> >> priorities for processing qDMA requests.
>> >> The following list summarizes the DPDMAI main features and capabilities:
>> >>       1. Supports up to two scheduling priorities for processing
>> >>       service requests.
>> >>       - Each DPDMAI transmit queue is mapped to one of two service
>> >>       priorities, allowing further prioritization in hardware between
>> >>       requests from different DPDMAI objects.
>> >>       2. Supports up to two receive queues for incoming transaction
>> >>       completion confirmations.
>> >>       - Each DPDMAI receive queue is mapped to one of two receive
>> >>       priorities, allowing further prioritization between other
>> >>       interfaces when associating the DPDMAI receive queues to DPIO
>> >>       or DPCON(Data Path Concentrator) objects.
>> >>       3. Supports different scheduling options for processing received
>> >>       packets:
>> >>       - Queues can be configured either in 'parked' mode (default),
>> >>       or attached to a DPIO object, or attached to DPCON object.
>> >>       4. Allows interaction with one or more DPIO objects for
>> >>       dequeueing/enqueueing frame descriptors(FD) and for
>> >>       acquiring/releasing buffers.
>> >>       5. Supports enable, disable, and reset operations.
>> >>
>> >> Add dpdmai to support some platforms with dpaa2 qdma engine.
>> >
>> >Applied both, thanks
>
>I see this error when I'm building.
>
>WARNING: modpost: missing MODULE_LICENSE() in
>drivers/dma/fsl-dpaa2-qdma/dpdmai.o
>see include/linux/module.h for more information
>ERROR: "dpdmai_enable" [drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.ko]
>undefined!
>ERROR: "dpdmai_set_rx_queue"
>[drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.ko] undefined!
>ERROR: "dpdmai_get_tx_queue"
>[drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.ko] undefined!
>ERROR: "dpdmai_get_rx_queue"
>[drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.ko] undefined!
>ERROR: "dpdmai_get_attributes"
>[drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.ko] undefined!
>ERROR: "dpdmai_open" [drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.ko]
>undefined!
>ERROR: "dpdmai_close" [drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.ko]
>undefined!
>ERROR: "dpdmai_disable" [drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.ko]
>undefined!
>ERROR: "dpdmai_reset" [drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.ko]
>undefined!
>make[2]: *** [../scripts/Makefile.modpost:95: __modpost] Error 1
>make[1]: *** [/srv/src/kernel/next/Makefile:1282: modules] Error 2
>make: *** [Makefile:179: sub-make] Error 2
>make: Target 'Image' not remade because of errors.
>make: Target 'modules' not remade because of errors.
>
>any other that see the same ?
>
>Cheers,
>Anders

  reply	other threads:[~2019-10-22 10:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-30  2:04 [V5 1/2] dmaengine: fsl-dpaa2-qdma: Add the DPDMAI(Data Path DMA Interface) support Peng Ma
2019-09-30  2:04 ` [V5 2/2] dmaengine: fsl-dpaa2-qdma: Add NXP dpaa2 qDMA controller driver for Layerscape SoCs Peng Ma
2019-10-17  4:11 ` [V5 1/2] dmaengine: fsl-dpaa2-qdma: Add the DPDMAI(Data Path DMA Interface) support Vinod Koul
2019-10-17  6:15   ` [EXT] " Peng Ma
2019-10-22  9:27     ` Anders Roxell
2019-10-22 10:19       ` Peng Ma [this message]
2019-10-22 11:10         ` Anders Roxell
2019-10-23  2:44           ` Peng Ma
2019-10-22 16:10         ` Vinod Koul
2019-10-23  2:38           ` Peng Ma

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=VI1PR04MB443121007853185039A65534ED680@VI1PR04MB4431.eurprd04.prod.outlook.com \
    --to=peng.ma@nxp.com \
    --cc=anders.roxell@linaro.org \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vkoul@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).