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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111202140304.GT8245@opensource.wolfsonmicro.com>
Date:	Fri, 2 Dec 2011 14:03:04 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Ashish Jangam <Ashish.Jangam@...tcummins.com>
Cc:	"arnd@...db.de" <arnd@...db.de>,
	"sameo@...nedhand.com" <sameo@...nedhand.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Dajun <dajun.chen@...semi.com>,
	"linaro-dev@...ts.linaro.org" <linaro-dev@...ts.linaro.org>
Subject: Re: [PATCH 01/11] MFD: DA9052 MFD core module v8

On Fri, Dec 02, 2011 at 01:57:49PM +0000, Ashish Jangam wrote:
> > On Fri, Nov 18, 2011 at 02:49:54PM +0530, Ashish Jangam wrote:

> > > +	da9052_i2c->bustype = BUS_I2C;

> > bustype should be redundant now, it certianly doesn't seem to be
> > referred to in this patch.

> This is required in the TSI driver.

You can just query the bus_type of the struct device if you really need
this.

> > > + * Interrupt controller support for Dilaog DA9052 PMICs.

> > This looks very much like it could be replaced with regmap-irq.  The
> > code would be slightly less efficient due to the support for sparse
> > interrupt registers but it'd be less code.

> regmap-irq has a opaque struct regmap_irq_chip_data which has a member
> irq_base and this is required for non-primary irqs registration
> and also the clean-up function regmap_del_irq_chip() requires it.
> So as of now I will keep the current irq implementation as it is. 

I'm not sure how this is relevant to my above comment?  The struct is of
course opaque since it is only used by the implementation.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ