linux-kernel - Re: [PATCH] DMAENGINE: generic slave channel control v3

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTikiV7+qvy8rG0nFqFoYxYqmwBswZK76abqj5DVb@mail.gmail.com>
Date:	Wed, 28 Jul 2010 00:28:03 -0700
From:	Dan Williams <dan.j.williams@...el.com>
To:	Linus Walleij <linus.walleij@...ricsson.com>
Cc:	linux-kernel@...r.kernel.org, Vinod Koul <vinod.koul@...el.com>,
	Alan Cox <alan@...ux.intel.com>
Subject: Re: [PATCH] DMAENGINE: generic slave channel control v3

On Fri, Jul 23, 2010 at 10:27 AM, Linus Walleij
<linus.walleij@...ricsson.com> wrote:
> This adds an interface to the DMAengine to make it possible to
> reconfigure a slave channel at runtime. We add a few foreseen
> config parameters to the passed struct, with a void * pointer
> for custom per-device or per-platform runtime slave data.
>
> Signed-off-by: Linus Walleij <linus.walleij@...ricsson.com>

Ok, let's go with this version, but one question before I apply it:

What are the rules for when a new dma_slave_config can be set?
Looking at the driver implementations it seems there is nothing
preventing a concurrent call to device_control to occur at "wrong
time"?  Is there a synchronization context I'm missing?

--
Dan
--
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/