Message ID | 20201119191051.46363-1-cristian.marussi@arm.com (mailing list archive) |
---|---|
Headers | show |
Series | Add support for SCMIv3.0 Voltage Domain Protocol and SCMI-Regulator | expand |
On Thu, 19 Nov 2020 19:10:46 +0000, Cristian Marussi wrote: > this series introduces the support for the new SCMI Voltage Domain Protocol > defined by the upcoming SCMIv3.0 specification, whose BETA release is > available at [1]. > > Afterwards, a new generic SCMI Regulator driver is developed on top of the > new SCMI VD Protocol. > > [...] Applied to sudeep.holla/linux (for-next/scmi-voltage), thanks! I will soon send pull request to Mark Brown so tha he can pick by the regulator driver patches with these as agreed. [4/5] dt-bindings: arm: Add support for SCMI Regulators https://git.kernel.org/sudeep.holla/c/0f80fcec08 [1/5] firmware: arm_scmi: Add voltage domain management protocol support https://git.kernel.org/sudeep.holla/c/2add5cacff [2/5] firmware: arm_scmi: Add support to enumerated SCMI voltage domain device https://git.kernel.org/sudeep.holla/c/ec88381936 -- Regards, Sudeep
On Thu, 19 Nov 2020 19:10:46 +0000, Cristian Marussi wrote: > this series introduces the support for the new SCMI Voltage Domain Protocol > defined by the upcoming SCMIv3.0 specification, whose BETA release is > available at [1]. > > Afterwards, a new generic SCMI Regulator driver is developed on top of the > new SCMI VD Protocol. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/1] regulator: core: add of_match_full_name boolean flag commit: e7095c35abfc5a5d566941a87434c0fd5ffb570f All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark