Message ID | 1608790134-27425-1-git-send-email-henryc.chen@mediatek.com |
---|---|
Headers | show |
Series | Add driver for dvfsrc, support for active state of scpsys | expand |
On Thu, 24 Dec 2020 14:08:42 +0800, Henry Chen wrote: > Document the binding for enabling dvfsrc on MediaTek SoC. > > Signed-off-by: Henry Chen <henryc.chen@mediatek.com> > --- > .../devicetree/bindings/soc/mediatek/dvfsrc.yaml | 68 ++++++++++++++++++++++ > 1 file changed, 68 insertions(+) > create mode 100644 Documentation/devicetree/bindings/soc/mediatek/dvfsrc.yaml > My bot found errors running 'make dt_binding_check' on your patch: yamllint warnings/errors: dtschema/dtc warnings/errors: Documentation/devicetree/bindings/soc/mediatek/dvfsrc.example.dts:19:18: fatal error: dt-bindings/soc/mtk,dvfsrc.h: No such file or directory 19 | #include <dt-bindings/soc/mtk,dvfsrc.h> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. make[1]: *** [scripts/Makefile.lib:342: Documentation/devicetree/bindings/soc/mediatek/dvfsrc.example.dt.yaml] Error 1 make: *** [Makefile:1370: dt_binding_check] Error 2 See https://patchwork.ozlabs.org/patch/1420382 This check can fail if there are any dependencies. The base for a patch series is generally the most recent rc1. If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date: pip3 install dtschema --upgrade Please check and re-submit.
On Thu, 2020-12-24 at 10:01 -0700, Rob Herring wrote: > On Thu, 24 Dec 2020 14:08:42 +0800, Henry Chen wrote: > > Document the binding for enabling dvfsrc on MediaTek SoC. > > > > Signed-off-by: Henry Chen <henryc.chen@mediatek.com> > > --- > > .../devicetree/bindings/soc/mediatek/dvfsrc.yaml | 68 ++++++++++++++++++++++ > > 1 file changed, 68 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/soc/mediatek/dvfsrc.yaml > > > > My bot found errors running 'make dt_binding_check' on your patch: > > yamllint warnings/errors: > > dtschema/dtc warnings/errors: > Documentation/devicetree/bindings/soc/mediatek/dvfsrc.example.dts:19:18: fatal error: dt-bindings/soc/mtk,dvfsrc.h: No such file or directory > 19 | #include <dt-bindings/soc/mtk,dvfsrc.h> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > compilation terminated. > make[1]: *** [scripts/Makefile.lib:342: Documentation/devicetree/bindings/soc/mediatek/dvfsrc.example.dt.yaml] Error 1 > make: *** [Makefile:1370: dt_binding_check] Error 2 > > See https://patchwork.ozlabs.org/patch/1420382 > > This check can fail if there are any dependencies. The base for a patch > series is generally the most recent rc1. > > If you already ran 'make dt_binding_check' and didn't see the above > error(s), then make sure 'yamllint' is installed and dt-schema is up to > date: > > pip3 install dtschema --upgrade > > Please check and re-submit. > Hi Rob, Sorry for the check error, I will re-check and submit again. Thanks, Henry
On 12/24/20 08:08, Henry Chen wrote: > From: "henryc.chen" <henryc.chen@mediatek.com> > > Add interconnect provider dt-bindings for MT6873. > > Signed-off-by: Henry Chen <henryc.chen@mediatek.com> checkpatch complains: From:/Signed-off-by: email name mismatch: 'From: "henryc.chen" <henryc.chen@mediatek.com>' != 'Signed-off-by: Henry Chen <henryc.chen@mediatek.com>' Thanks, Georgi > --- > include/dt-bindings/interconnect/mtk,mt6873-emi.h | 41 +++++++++++++++++++++++ > 1 file changed, 41 insertions(+) > create mode 100644 include/dt-bindings/interconnect/mtk,mt6873-emi.h > > diff --git a/include/dt-bindings/interconnect/mtk,mt6873-emi.h b/include/dt-bindings/interconnect/mtk,mt6873-emi.h > new file mode 100644 > index 0000000..7a0bbfb > --- /dev/null > +++ b/include/dt-bindings/interconnect/mtk,mt6873-emi.h > @@ -0,0 +1,41 @@ > +/* SPDX-License-Identifier: GPL-2.0 > + * > + * Copyright (c) 2020 MediaTek Inc. > + */ > + > +#ifndef __DT_BINDINGS_INTERCONNECT_MTK_MT6873_EMI_H > +#define __DT_BINDINGS_INTERCONNECT_MTK_MT6873_EMI_H > + > +#define MT6873_SLAVE_DDR_EMI 0 > +#define MT6873_MASTER_MCUSYS 1 > +#define MT6873_MASTER_GPUSYS 2 > +#define MT6873_MASTER_MMSYS 3 > +#define MT6873_MASTER_MM_VPU 4 > +#define MT6873_MASTER_MM_DISP 5 > +#define MT6873_MASTER_MM_VDEC 6 > +#define MT6873_MASTER_MM_VENC 7 > +#define MT6873_MASTER_MM_CAM 8 > +#define MT6873_MASTER_MM_IMG 9 > +#define MT6873_MASTER_MM_MDP 10 > +#define MT6873_MASTER_VPUSYS 11 > +#define MT6873_MASTER_VPU_0 12 > +#define MT6873_MASTER_VPU_1 13 > +#define MT6873_MASTER_MDLASYS 14 > +#define MT6873_MASTER_MDLA_0 15 > +#define MT6873_MASTER_UFS 16 > +#define MT6873_MASTER_PCIE 17 > +#define MT6873_MASTER_USB 18 > +#define MT6873_MASTER_DBGIF 19 > +#define MT6873_SLAVE_HRT_DDR_EMI 20 > +#define MT6873_MASTER_HRT_MMSYS 21 > +#define MT6873_MASTER_HRT_MM_DISP 22 > +#define MT6873_MASTER_HRT_MM_VDEC 23 > +#define MT6873_MASTER_HRT_MM_VENC 24 > +#define MT6873_MASTER_HRT_MM_CAM 25 > +#define MT6873_MASTER_HRT_MM_IMG 26 > +#define MT6873_MASTER_HRT_MM_MDP 27 > +#define MT6873_MASTER_HRT_DBGIF 28 > +#define MT6873_MASTER_WIFI 29 > +#define MT6873_MASTER_BT 30 > +#define MT6873_MASTER_NETSYS 31 > +#endif >
On Thu, 24 Dec 2020 14:08:41 +0800, Henry Chen wrote: > This series is based on v5.10-rc1. > > The patchsets add support for MediaTek hardware module named DVFSRC > (dynamic voltage and frequency scaling resource collector). The DVFSRC is > a HW module which is used to collect all the requests from both software > and hardware and turn into the decision of minimum operating voltage and > minimum DRAM frequency to fulfill those requests. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [11/13] regulator: Regulator driver for the Mediatek DVFSRC commit: a0db6b0aa670ba040f959a000ef24dd4238e016b 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