On Thu, Feb 20, 2020 at 05:06:05PM +0100, Halil Pasic wrote:

Currently force_dma_unencrypted() is only used by the direct
implementation of the DMA API, and thus resides in dma-direct.h. But
there is nothing dma-direct specific about it: if one was -- for
whatever reason -- to implement custom DMA ops that have to in the
encrypted/protected scenarios dma-direct currently deals with, one would
need exactly this kind of information.

I really don't think it has business being anywhre else, and your completely
bogus second patch just proves the point.