Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1432494

RE: [PATCH 2/4] dmaengine: vdma: Add support for mulit-channel dma mode

Path csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From Appana Durga Kedareswara Rao <appana.durga.rao@xilinx.com>
Newsgroups linux.kernel
Subject RE: [PATCH 2/4] dmaengine: vdma: Add support for mulit-channel dma mode
Date Tue, 28 Jun 2016 08:00:02 +0200
Message-ID <rOUdY-2IX-3@gated-at.bofh.it> (permalink)
References <rIqLD-2IM-3@gated-at.bofh.it> <rIqLE-2IM-33@gated-at.bofh.it> <rMw65-7Hw-1@gated-at.bofh.it> <rMwIO-8bK-33@gated-at.bofh.it> <rMwIO-8bK-31@gated-at.bofh.it> <rMKsq-iq-171@gated-at.bofh.it> <rOSOS-1TL-3@gated-at.bofh.it>
X-Original-To Vinod Koul <vinod.koul@intel.com>
Authentication-Results spf=pass (sender IP is 149.199.60.100) smtp.mailfrom=xilinx.com; vger.kernel.org; dkim=none (message not signed) header.d=none;vger.kernel.org; dmarc=bestguesspass action=none header.from=xilinx.com;
Received-Spf Pass (protection.outlook.com: domain of xilinx.com designates 149.199.60.100 as permitted sender) receiver=protection.outlook.com; client-ip=149.199.60.100; helo=xsj-pvapsmtpgw02;
Thread-Topic [PATCH 2/4] dmaengine: vdma: Add support for mulit-channel dma mode
Thread-Index AQHRwvhG7GsWp3fGQ0KDXydjsS2JzJ/znn0AgACEjJD//4ZBgIAAhK+wgAmy1YCAAJw5EA==
Accept-Language en-US
Content-Language en-US
X-Originating-IP [172.23.95.64]
Content-Type text/plain; charset="us-ascii"
Content-Transfer-Encoding 8BIT
MIME-Version 1.0
X-Rcis-Action ALLOW
X-Tm-As-Product-Ver IMSS-7.1.0.1224-8.0.0.1202-22416.006
X-Tm-As-User-Approved-Sender Yes;Yes
X-Ms-Office365-Filtering-Ht Tenant
X-Forefront-Antispam-Report CIP:149.199.60.100;IPV:NLI;CTRY:US;EFV:NLI;SFV:NSPM;SFS:(10009020)(6009001)(7916002)(2980300002)(438002)(189002)(51914003)(199003)(86362001)(92566002)(54356999)(76176999)(4326007)(586003)(6116002)(102836003)(7696003)(7736002)(3846002)(11100500001)(5250100002)(63266004)(93886004)(23726003)(2920100001)(2900100001)(2950100001)(5003600100003)(50986999)(87936001)(189998001)(50466002)(6806005)(97756001)(33656002)(81156014)(81166006)(110136002)(7846002)(106466001)(8746002)(47776003)(305945005)(356003)(8676002)(46406003)(55846006)(8936002)(106116001)(2906002)(107986001)(5001870100001);DIR:OUT;SFP:1101;SCL:1;SRVR:SN1NAM02HT169;H:xsj-pvapsmtpgw02;FPR:;SPF:Pass;PTR:xapps1.xilinx.com,unknown-60-100.xilinx.com;MX:1;A:1;CAT:NONE;LANG:en;CAT:NONE;
X-Ms-Office365-Filtering-Correlation-ID a4056f95-98f4-4b4b-8e8d-08d39f18ec01
X-Microsoft-Antispam UriScan:;BCL:0;PCL:0;RULEID:(8251501002);SRVR:SN1NAM02HT169;
X-Microsoft-Antispam-Prvs <8c5a313969344f03ac4899b9b55df0b5@SN1NAM02HT169.eop-nam02.prod.protection.outlook.com>
X-Exchange-Antispam-Report-Test UriScan:;
X-Exchange-Antispam-Report-Cfa-Test BCL:0;PCL:0;RULEID:(601004)(2401047)(13018025)(8121501046)(13023025)(13024025)(13017025)(5005006)(13015025)(10201501046)(3002001)(6055026);SRVR:SN1NAM02HT169;BCL:0;PCL:0;RULEID:;SRVR:SN1NAM02HT169;
X-Forefront-Prvs 0987ACA2E2
X-Originatororg xilinx.com
X-Ms-Exchange-Crosstenant-Originalarrivaltime 28 Jun 2016 05:56:12.5374 (UTC)
X-Ms-Exchange-Crosstenant-ID 657af505-d5df-48d0-8300-c31994686c5c
X-Ms-Exchange-Crosstenant-Originalattributedtenantconnectingip TenantId=657af505-d5df-48d0-8300-c31994686c5c;Ip=[149.199.60.100];Helo=[xsj-pvapsmtpgw02]
X-Ms-Exchange-Crosstenant-Fromentityheader HybridOnPrem
X-Ms-Exchange-Transport-Crosstenantheadersstamped SN1NAM02HT169
Sender robomod@news.nic.it
List-ID <linux-kernel.vger.kernel.org>
X-Mailing-List linux-kernel@vger.kernel.org
Approved robomod@news.nic.it
Lines 72
Organization linux.* mail to news gateway
X-Original-Cc "robh+dt@kernel.org" <robh+dt@kernel.org>, "pawel.moll@arm.com" <pawel.moll@arm.com>, "mark.rutland@arm.com" <mark.rutland@arm.com>, "ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>, "galak@codeaurora.org" <galak@codeaurora.org>, Michal Simek <michals@xilinx.com>, Soren Brinkmann <sorenb@xilinx.com>, "dan.j.williams@intel.com" <dan.j.williams@intel.com>, "moritz.fischer@ettus.com" <moritz.fischer@ettus.com>, "laurent.pinchart@ideasonboard.com" <laurent.pinchart@ideasonboard.com>, "luis@debethencourt.com" <luis@debethencourt.com>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>
X-Original-Date Tue, 28 Jun 2016 05:55:58 +0000
X-Original-Message-ID <C246CAC1457055469EF09E3A7AC4E11A4A5B9B9E@XAP-PVEXMBX01.xlnx.xilinx.com>
X-Original-References <1465549954-30220-1-git-send-email-appanad@xilinx.com> <1465549954-30220-3-git-send-email-appanad@xilinx.com> <20160621155502.GB16910@localhost> <C246CAC1457055469EF09E3A7AC4E11A4A5B8248@XAP-PVEXMBX01.xlnx.xilinx.com> <20160621163340.GE16910@localhost> <C246CAC1457055469EF09E3A7AC4E11A4A5B84A9@XAP-PVEXMBX01.xlnx.xilinx.com> <20160628043459.GR22564@localhost>
X-Original-Sender linux-kernel-owner@vger.kernel.org
Xref csiph.com linux.kernel:1432494

Show key headers only | View raw


Hi Vinod,

	Thanks for the review...

> > > > > >  /**
> > > > > > + * struct xilinx_mcdma_config - DMA Multi channel
> > > > > > +configuration structure
> > > > > > + * @tdest: Channel to operate on
> > > > > > + * @tid:   Channel configuration
> > > > > > + * @tuser: Tuser configuration
> > > > > > + * @ax_user: ax_user value
> > > > > > + * @ax_cache: ax_cache value
> > > > > > + */
> > > > > > +struct xilinx_mcdma_config {
> > > > > > +	u8 tdest;
> > > > > > +	u8 tid;
> > > > > > +	u8 tuser;
> > > > > > +	u8 ax_user;
> > > > > > +	u8 ax_cache;
> > > > >
> > > > > can you describe these in details, what do these do, what are
> > > > > the values to be programmed?
> > > >
> > > > As said above In Multi-Channel Mode each Stream interface can be
> > > > Configured up to 16 channels each channel is differentiated based
> > > > on the tdest
> > > and tid values.
> > >
> > > Then why are you not registering 16 channels for this? That should
> > > give you channel to operate on!
> >
> > The number of channels are configurable.
> > We are registering number of Channels that h/w configured for.
> >
> > Will fix in the next version. Will remove this config.
> > And based on the channel type will configure the h/w.
> 
> Looking at this you should redesign!
> 
> The vchan was designed to operate on 'virtual' channels. The hardware channels
> can be independent of that.
> 
> Your IP seems to be a good fit for that approach. Do not link the two and
> separate them. User can have a virtual channel. In your driver, you can manage
> hardware channels...

Fixed it in the v2 and posted the v2 series.
Please go thought it...

> 
> >
> > >
> > > >
> > > > tdest:
> > > > TDEST provides routing information for the data stream.
> > >
> > > pls elobrate
> >
> > Need to configure this with the channel number that We would like to
> > transfer data.
> 
> This should be internal to driver...

Fixed it in the v2 and posted the v2 series.
Please go thought it...

Regards,
Kedar.

> 
> --
> ~Vinod

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH 2/4] dmaengine: vdma: Add support for mulit-channel dma  mode Vinod Koul <vinod.koul@intel.com> - 2016-06-28 06:30 +0200
  RE: [PATCH 2/4] dmaengine: vdma: Add support for mulit-channel dma  mode Appana Durga Kedareswara Rao <appana.durga.rao@xilinx.com> - 2016-06-28 08:00 +0200
    RE: [PATCH 2/4] dmaengine: vdma: Add support for mulit-channel dma  mode Appana Durga Kedareswara Rao <appana.durga.rao@xilinx.com> - 2016-06-28 09:30 +0200

csiph-web