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]
Date:	Wed, 21 May 2014 07:37:18 +0800
From:	"Zhu, Lejun" <lejun.zhu@...ux.intel.com>
To:	Lee Jones <lee.jones@...aro.org>
CC:	sameo@...ux.intel.com, linux-kernel@...r.kernel.org,
	bin.yang@...el.com
Subject: Re: [PATCH 0/4] mfd: Intel SoC Power Management IC



On 5/20/2014 10:55 PM, Lee Jones wrote:
> On Wed, 14 May 2014, Zhu, Lejun wrote:
> 
>> Devices based on Intel SoC products such as Baytrail have a Power
>> Management IC. In the PMIC there are subsystems for voltage regulation,
>> A/D conversion, GPIO and PWMs. The PMIC in Baytrail-T platform is called
>> Crystal Cove.
>>
>> This series contains common code for these PMICs, and device specific
>> support for Crystal Cove.
>>
>> Lejun Zhu (4):
>>   mfd: intel_soc_pmic: Core driver
>>   mfd: intel_soc_pmic: I2C interface
>>   mfd: intel_soc_pmic: Crystal Cove support
>>   mfd: intel_soc_pmic: Build files
> 
> I'm missing the build files patch.  Can you ensure I was on the
> distribution list please?  Also, what's the reason for splitting the
> files out instead of having one single driver?
> 

I'll resend patch 4/4.

The reason for splitting the files is because there are other models of
such SoC PMIC being worked on. These PMICs will have enough similarity
that we feel it's better to keep separate common code
(intel_soc_pmic_core, intel_soc_pmic_i2c) and model specific code
(intel_soc_pmic_crc and future intel_soc_pmic_xxx).

Best Regards
Lejun

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