linux-kernel - RE: [PATCH] regulator: Add S5M8767 regulator 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: <009901cc9172$e2a2ef90$a7e8ceb0$@com>
Date:	Sun, 23 Oct 2011 19:59:50 +0900
From:	Sangbeom Kim <sbkim73@...sung.com>
To:	'Mark Brown' <broonie@...nsource.wolfsonmicro.com>
Cc:	'Liam Girdwood' <lrg@...com>, linux-kernel@...r.kernel.org
Subject: RE: [PATCH] regulator: Add S5M8767 regulator driver

On Sun, Oct 23, 2011 at 06:30 PM , Mark Brown wrote:
 
> I guess you need an implementation for enable_suspend() (otherwise you
> can't do disable->enable)
Ok, I will add it in the next version.

> 
> > +	{
> > +		.name	= "AP 32KHz",
> > +		.id	= S5M8767_32KHZAP_EN,
> > +		.ops	= &s5m8767_others_ops,
> > +		.type	= REGULATOR_VOLTAGE,
> > +		.owner	= THIS_MODULE,
> > +	}, {
> > +		.name	= "CP 32KHz",
> > +		.id	= S5M8767_32KHZAP_EN,
> > +		.ops	= &s5m8767_others_ops,
> > +		.type	= REGULATOR_VOLTAGE,
> > +		.owner	= THIS_MODULE,
> > +	},
> 
> Do these actually share anything with the other regulators?  If not then
> I guess it's better to do with the struct clk framework.

OK, I will consider clk framework

 
> > +				dev_warn(&pdev->dev, "Duplicated gpio
> > request"
> > +						" for SET3\n");
> 
> Please keep the strings on one line (it makes grepping for errors
> easier).

Thanks,
Sangbeom.

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