linux-kernel - Re: Recommendations for a new MFD device 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150210072039.GC8020@x1>
Date:	Tue, 10 Feb 2015 15:20:39 +0800
From:	Lee Jones <lee.jones@...aro.org>
To:	Sascha Hauer <s.hauer@...gutronix.de>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	eddie.huang@...iatek.com, Mark Brown <broonie@...nel.org>
Subject: Re: Recommendations for a new MFD device driver?

On Fri, 06 Feb 2015, Sascha Hauer wrote:

> Hi All,
> 
> We are adding support for a new pretty typical MFD device, the MediaTek
> MT6397. Initial patches are already posted. It's a PMIC which among other
> things has regulators and a RTC. The same RTC is reused on another PMIC,
> but with another register offset and another interrupt.
> 
> Now the question is where shall we put the register/irq resource
> information?
> 
> 1) Put it into the RTC device driver.
> 2) Put it into the .resource field of struct mfd_cell
> 3) Put it into the device tree using standard reg, interrupt properties and
>    a) Let the RTC driver interpret these
>    b) Let the MFD driver create resources in the .resource field of struct
>       mfd_cell
>    c) Let the MFD core create the resources

I have no problem with 2, if that's the route you'd like to take.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
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/