linux-kernel - RE: [PATCH v2 1/3] mfd: add lp8788 mfd driver

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] [day] [month] [year] [list]

Message-ID: <A874F61F95741C4A9BA573A70FE3998F41EEF214@DQHE02.ent.ti.com>
Date:	Fri, 10 Aug 2012 07:23:36 +0000
From:	"Kim, Milo" <Milo.Kim@...com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	"sameo@...ux.intel.com" <sameo@...ux.intel.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v2 1/3] mfd: add lp8788 mfd driver

> > Patch v2.
> > (a) For interrupt handling, use generic irq rather than irq-domain
> 
> This seems like a very substantial step backwards, why make this change?
> Using irqdomain solves a bunch of problems, especially around virq
> allocation, and is where we want all drivers to go longer term.

Yes, you're right.
I moved it to old concept because I have to figure out the irq domain,
especially device tree interface.
I'm still not clear.

For the phased development, my plan is 
1) submitting lp8788 driver with generic irq
2) patch for supporting irq domain later

Best Regards,
Milo




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