[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180402120414.GA8159@lunn.ch>
Date: Mon, 2 Apr 2018 14:04:14 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Lee Jones <lee.jones@...aro.org>, Rob Herring <robh+dt@...nel.org>,
devicetree@...r.kernel.org,
Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>,
Felipe Balbi <felipe.balbi@...ux.intel.com>,
linux-usb@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jassi Brar <jaswinder.singh@...aro.org>,
Masami Hiramatsu <masami.hiramatsu@...aro.org>,
Arnd Bergmann <arnd@...db.de>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [Question] MFD driver that handles clocks/resets and populates
child nodes
> The maintainer of DWC3, Felipe Balbi, requested to
> split the glue layer driver into small parts such as
> reset, regulator, phy, etc.
What exactly did Felipe ask for? Did he ask that the patch be split
up, one patch per reset, regulator, phy etc?
Are all these resources used just by the DWC3? Or is it a true MFD,
multiple functions?
Andrew
Powered by blists - more mailing lists