Hi, On Wed, Jun 17, 2020 at 9:26 AM Ravi Kumar Bokka (Temp) <rbo...@codeaurora.org> wrote: > > > > On 6/17/2020 8:48 PM, Srinivas Kandagatla wrote: > > > > > > On 17/06/2020 15:51, Douglas Anderson wrote: > >> From: Ravi Kumar Bokka <rbo...@codeaurora.org> > >> > >> This switches the bindings over from txt to yaml. > >> > >> Signed-off-by: Ravi Kumar Bokka <rbo...@codeaurora.org> > >> Signed-off-by: Douglas Anderson <diand...@chromium.org> > >> --- > >> > >> Changes in v3: > >> - Split conversion to yaml into separate patch new in v3. > >> - Use 'const' for compatible instead of a 1-entry enum. > >> - Changed filename to match compatible string. > >> - Add #address-cells and #size-cells to list of properties. > >> - Fixed up example. > >> > >> .../bindings/nvmem/qcom,qfprom.yaml | 45 +++++++++++++++++++ > >> .../devicetree/bindings/nvmem/qfprom.txt | 35 --------------- > >> 2 files changed, 45 insertions(+), 35 deletions(-) > >> create mode 100644 > >> Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml > >> delete mode 100644 Documentation/devicetree/bindings/nvmem/qfprom.txt > >> > >> diff --git a/Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml > >> b/Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml > >> new file mode 100644 > >> index 000000000000..5efa5e7c4d81 > >> --- /dev/null > >> +++ b/Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml > >> @@ -0,0 +1,45 @@ > >> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > >> +%YAML 1.2 > >> +--- > >> +$id: http://devicetree.org/schemas/nvmem/qcom,qfprom.yaml# > >> +$schema: http://devicetree.org/meta-schemas/core.yaml# > >> + > >> +title: Qualcomm Technologies Inc, QFPROM Efuse bindings > >> + > >> +maintainers: > >> + - Ravi Kumar Bokka <rbo...@codeaurora.org> > >> + > > > > Am not sure this was intentional, but the old maintainer name is totally > > lost in this patch! > > > > Please fix this! > > > > Hi Srinivas, > The existed qfprom dt-bindings in .txt format. > I will make it as it is to merge whole content in .yaml format once > confirm all the parameters with this new driver changes.
Ah, right. It makes more sense to set you as the maintainer since you were listed as the maintainer for the Linux driver and also the author of the old bindings. I'll change it to you then. Unless I hear otherwise, I'll plan to send out a v4 tomorrow with feedback I've gotten today. -Doug
