linux-kernel - Re: [PATCH] dw_dmac: adjust slave_id accordingly to request line base

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: <CAOh2x=nTJ1iz9aoR8VrkE5A+iaLMMbvFeebGPsO8KWRpDLw7=A@mail.gmail.com>
Date:	Tue, 29 Jan 2013 20:57:24 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc:	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	Vinod Koul <vinod.koul@...el.com>,
	linux-kernel@...r.kernel.org, spear-devel <spear-devel@...t.st.com>
Subject: Re: [PATCH] dw_dmac: adjust slave_id accordingly to request line base

On Tue, Jan 29, 2013 at 10:52 AM, Mika Westerberg
<mika.westerberg@...ux.intel.com> wrote:
> We had a discusssion about this with Andy as well. The thing is that there
> is no way in current resource to pass DMA request line numbers supported by
> the controller to the driver in a generic way. We on the other hand have to
> deal this somehow as we have a shared DMA controller on Lynxpoint where the
> offset will start from 16 (but it might be something else as well).
>
> Is there something which limits the usage of IORESOUCE_DMA to be only
> usable for ISA DMA channels?

Andy,

Why do we need this request_line_base? Why not program the actual value
directly into the slave structure (base + offset)?

In case it is required, add it in platform data field or can add DT
binding for it.

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