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:   Thu, 28 Feb 2019 09:04:50 +0200
From:   Matti Vaittinen <matti.vaittinen@...rohmeurope.com>
To:     mazziesaccount@...il.com
Cc:     Guenter Roeck <linux@...ck-us.net>,
        heikki.haikola@...rohmeurope.com, mikko.mutanen@...rohmeurope.com,
        lee.jones@...aro.org, robh+dt@...nel.org, mark.rutland@....com,
        broonie@...nel.org, gregkh@...uxfoundation.org, rafael@...nel.org,
        mturquette@...libre.com, sboyd@...nel.org,
        linus.walleij@...aro.org, bgolaszewski@...libre.com,
        sre@...nel.org, lgirdwood@...il.com, a.zummo@...ertech.it,
        alexandre.belloni@...tlin.com, wim@...ux-watchdog.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-clk@...r.kernel.org, linux-gpio@...r.kernel.org,
        linux-pm@...r.kernel.org, linux-rtc@...r.kernel.org,
        linux-watchdog@...r.kernel.org, bogdan-petru.chircu-mare@....com
Subject: Re: [PATCH v10 0/9] support ROHM BD70528 PMIC

Hello Lee and Mark,

On Thu, Feb 14, 2019 at 03:02:37PM +0200, Matti Vaittinen wrote:
> Patch series introducing support for ROHM BD70528 PMIC
> 
> ROHM BD70528 is a programmable Power Management IC for battery
> powered 'ultra low power' systems like the pre-announced NXP
> i.MX7 ULP. This patch series introduces support for the PMIC. Please
> note that this driver only supports HW setup where PMIC is connected
> to I2C on A7 core. The other scenario is to use M4 as a power manager
> and connect pmic to M4. On such setups the A7 can only access pmic
> via M4 core using RPMSG virtio. Such setup depends on RPMSG
> implementation on M4 core and is currently not supported by this
> patch series.
> 

I was wondering if there is anything that could be done to allow the MFD
part of this series to end up in upstream without having to wait the
regmap-irq changes
(https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git/commit/?h=topic/irq)
 to be merged from Linus' tree to MFD tree? If I see it correctly, the
regmap-irq (main-irq-reg support) changes are not targeted to linux 5.1.
To me it looks like getting them to MFD via Linus' tree will take a while.

The MFD part depends on the regmap-irq changes and I think that most
other subsystems want to have the MFD changes in before taking rest of
the driver in their trees. So it will be a while untill all the changes
are in. It would really be nice to have the drive in-tree sooner - hence
I ask if theres a way. (I don't want to push, just ask if it is possible :])

Best Regards
	Matti Vaittinen

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ