lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 24 Oct 2012 08:39:01 +0530 From: Vinod Koul <vkoul@...radead.org> To: Dan Williams <djbw@...com> Cc: vinod.koul@...el.com, Matt Porter <mporter@...com>, Chris Ball <cjb@...top.org>, Linux DaVinci Kernel List <davinci-linux-open-source@...ux.davincidsp.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux MMC List <linux-mmc@...r.kernel.org> Subject: Re: [RFC PATCH 1/3] dmaengine: add dma_get_channel_caps() On Tue, 2012-10-23 at 15:54 -0700, Dan Williams wrote: > > +struct dmaengine_chan_caps { > > + enum dmaengine_apis ops; > > + int seg_nr; > > + int seg_len; > > +}; > > This makes sense for the potentially dynamic capability properties > that get set after configuration, but why do we need the operation > types here? They can be retrieved from the parent device. I was thinking that each channel can have different capabilities. You can assign one channel for mempcy operations exclusively and some others for slave usage exclusively. I believe some h/w do have such assignment so would help in doing that. -- Vinod Koul Intel Corp. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists