linux-kernel - Re: [PATCH V1 Resend 0/3] dmaengine: Allow controller drivers to set channel ids

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 PHC
Open Source and information security mailing list archives

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

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

Date:	Tue, 20 Dec 2011 01:40:24 -0800
From:	"Williams, Dan J" <dan.j.williams@...el.com>
To:	Viresh Kumar <viresh.kumar@...com>
Cc:	vinod.koul@...el.com, linux-kernel@...r.kernel.org,
	armando.visconti@...com, shiraz.hashim@...com, vipin.kumar@...com,
	rajeev-dlh.kumar@...com, deepak.sikri@...com,
	vipulkumar.samar@...com, amit.virdi@...com, pratyush.anand@...com,
	bhupesh.sharma@...com, viresh.linux@...il.com, bhavna.yadav@...com,
	vincenzo.frascino@...com, mirko.gardi@...com
Subject: Re: [PATCH V1 Resend 0/3] dmaengine: Allow controller drivers to set
 channel ids

On Sun, Dec 18, 2011 at 8:30 PM, Viresh Kumar <viresh.kumar@...com> wrote:
> Hi Dan,
>
> Probably you missed this patchset earlier, so resending it again.
>
> Currently value of chan_id field is updated by dmaengine.c while the dma device
> is registered. In some cases the controller driver may need to assign channel
> numbers by itself. This patchset introduces changes to do it.

Didn't we already go through this discussion once?

Here is the old thread: http://marc.info/?t=131122111000001&r=2&w=2

The chan_id is really only a sysfs detail, and for the same reasons
that scsi_host adapters don't pick their own host number neither
should dma channels.

The driver can set a channel id in its private channel struct right?

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