diff for duplicates of <20160127072430.GD3368@x1> diff --git a/a/1.txt b/N1/1.txt index 64f539b..28d8ce0 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,6 +1,6 @@ On Tue, 26 Jan 2016, Laxman Dewangan wrote: -> +>=20 > On Tuesday 26 January 2016 08:28 PM, Lee Jones wrote: > >On Mon, 25 Jan 2016, Laxman Dewangan wrote: > > @@ -9,7 +9,7 @@ On Tue, 26 Jan 2016, Laxman Dewangan wrote: > >I wouldn't describe any of them. It's normally pretty obvious which > >properties are boolean by the lack of required cell description. > > -> +>=20 > Rob suggested to use the type also for Boolean and tristate. I think > it is good to have for all places that what type of values are > valid. @@ -22,8 +22,10 @@ document. But if you insist, please ensure you are consistent, so > >>>>+The property for fps child nodes as: > >>>>+Required properties: > >>>>+ -reg: FPS number like 0, 1, 2 for FPS0, FPS1 and FPS2 respectively. -> >>>I'm surprised Rob Acked this. We don't usually do device numbers in DT. -> >>What is best way to make the child node for FPS and differentiate FPS0,1, 2? +> >>>I'm surprised Rob Acked this. We don't usually do device numbers in D= +T. +> >>What is best way to make the child node for FPS and differentiate FPS0,= +1, 2? > >>What is your suggestion here? > >There are lots of ways you can solve this and so many examples of > >others doing so. I suggest you have a look at some DTS files and @@ -31,24 +33,24 @@ document. But if you insist, please ensure you are consistent, so > >strings. > Here, I think I can go similar to regulators where child node name > identifies the regulators. -> +>=20 > fps-config { > fps0 { -> maxim,fps-time-period-us = <1280>; -> maxim,fps-enable-input = <FPS_EN_SRC_EN0>; +> maxim,fps-time-period-us =3D <1280>; +> maxim,fps-enable-input =3D <FPS_EN_SRC_EN0>; > }; -> +>=20 > fps1 { -> maxim,fps-time-period-us = <2560>; -> maxim,fps-enable-input = <FPS_EN_SRC_EN1>; +> maxim,fps-time-period-us =3D <2560>; +> maxim,fps-enable-input =3D <FPS_EN_SRC_EN1>; > }; -> +>=20 > fps2 { -> maxim,fps-time-period-us = <640>; -> maxim,fps-enable-input = <FPS_EN_SRC_SW>; +> maxim,fps-time-period-us =3D <640>; +> maxim,fps-enable-input =3D <FPS_EN_SRC_SW>; > }; > }; -> +>=20 > So node name gives the FPS name. That is also an acceptable means to solve the issue. @@ -56,24 +58,34 @@ That is also an acceptable means to solve the issue. As I said, there are many ways to skin a cat. > >>>+Pinmux and GPIO: -> >>>+=============== +> >>>+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >>>I think this whole section needs moving to ../pinctrl and needs to be > >>>reviewed by Linus W. > >>Is this mean I need to create DT binding doc for the each subsystem > >>differently? -> >>Actually during AS3722, I had different understanding to have single file. +> >>Actually during AS3722, I had different understanding to have single fi= +le. > >Yes, that way you have each of the the subsystem experts review your > >documentation. You can then link to them from this document. > OK, I will add different dt binding doc in respective driver and > squash that with respected submodule drivers. -> +>=20 --- +--=20 Lee Jones Linaro STMicroelectronics Landing Team Lead -Linaro.org │ Open source software for ARM SoCs +Linaro.org =E2=94=82 Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog --- -To unsubscribe from this list: send the line "unsubscribe linux-gpio" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html + +--=20 +--=20 +You received this message because you are subscribed to "rtc-linux". +Membership options at http://groups.google.com/group/rtc-linux . +Please read http://groups.google.com/group/rtc-linux/web/checklist +before submitting a driver. +---=20 +You received this message because you are subscribed to the Google Groups "= +rtc-linux" group. +To unsubscribe from this group and stop receiving emails from it, send an e= +mail to rtc-linux+unsubscribe@googlegroups.com. +For more options, visit https://groups.google.com/d/optout. diff --git a/a/content_digest b/N1/content_digest index 7811795..182bdc7 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,7 +5,7 @@ "ref\020160126145854.GC3368@x1\0" "ref\056A79DB4.6090000@nvidia.com\0" "From\0Lee Jones <lee.jones@linaro.org>\0" - "Subject\0Re: [PATCH V4 1/5] DT: mfd: add device-tree binding doc fro PMIC max77620/max20024\0" + "Subject\0[rtc-linux] Re: [PATCH V4 1/5] DT: mfd: add device-tree binding doc fro PMIC max77620/max20024\0" "Date\0Wed, 27 Jan 2016 07:24:30 +0000\0" "To\0Laxman Dewangan <ldewangan@nvidia.com>\0" "Cc\0robh+dt@kernel.org" @@ -31,7 +31,7 @@ "b\0" "On Tue, 26 Jan 2016, Laxman Dewangan wrote:\n" "\n" - "> \n" + ">=20\n" "> On Tuesday 26 January 2016 08:28 PM, Lee Jones wrote:\n" "> >On Mon, 25 Jan 2016, Laxman Dewangan wrote:\n" "> >\n" @@ -40,7 +40,7 @@ "> >I wouldn't describe any of them. It's normally pretty obvious which\n" "> >properties are boolean by the lack of required cell description.\n" "> >\n" - "> \n" + ">=20\n" "> Rob suggested to use the type also for Boolean and tristate. I think\n" "> it is good to have for all places that what type of values are\n" "> valid.\n" @@ -53,8 +53,10 @@ "> >>>>+The property for fps child nodes as:\n" "> >>>>+Required properties:\n" "> >>>>+\t-reg: FPS number like 0, 1, 2 for FPS0, FPS1 and FPS2 respectively.\n" - "> >>>I'm surprised Rob Acked this. We don't usually do device numbers in DT.\n" - "> >>What is best way to make the child node for FPS and differentiate FPS0,1, 2?\n" + "> >>>I'm surprised Rob Acked this. We don't usually do device numbers in D=\n" + "T.\n" + "> >>What is best way to make the child node for FPS and differentiate FPS0,=\n" + "1, 2?\n" "> >>What is your suggestion here?\n" "> >There are lots of ways you can solve this and so many examples of\n" "> >others doing so. I suggest you have a look at some DTS files and\n" @@ -62,24 +64,24 @@ "> >strings.\n" "> Here, I think I can go similar to regulators where child node name\n" "> identifies the regulators.\n" - "> \n" + ">=20\n" "> fps-config {\n" "> fps0 {\n" - "> maxim,fps-time-period-us = <1280>;\n" - "> maxim,fps-enable-input = <FPS_EN_SRC_EN0>;\n" + "> maxim,fps-time-period-us =3D <1280>;\n" + "> maxim,fps-enable-input =3D <FPS_EN_SRC_EN0>;\n" "> };\n" - "> \n" + ">=20\n" "> fps1 {\n" - "> maxim,fps-time-period-us = <2560>;\n" - "> maxim,fps-enable-input = <FPS_EN_SRC_EN1>;\n" + "> maxim,fps-time-period-us =3D <2560>;\n" + "> maxim,fps-enable-input =3D <FPS_EN_SRC_EN1>;\n" "> };\n" - "> \n" + ">=20\n" "> fps2 {\n" - "> maxim,fps-time-period-us = <640>;\n" - "> maxim,fps-enable-input = <FPS_EN_SRC_SW>;\n" + "> maxim,fps-time-period-us =3D <640>;\n" + "> maxim,fps-enable-input =3D <FPS_EN_SRC_SW>;\n" "> };\n" "> };\n" - "> \n" + ">=20\n" "> So node name gives the FPS name.\n" "\n" "That is also an acceptable means to solve the issue.\n" @@ -87,26 +89,36 @@ "As I said, there are many ways to skin a cat.\n" "\n" "> >>>+Pinmux and GPIO:\n" - "> >>>+===============\n" + "> >>>+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D\n" "> >>>I think this whole section needs moving to ../pinctrl and needs to be\n" "> >>>reviewed by Linus W.\n" "> >>Is this mean I need to create DT binding doc for the each subsystem\n" "> >>differently?\n" - "> >>Actually during AS3722, I had different understanding to have single file.\n" + "> >>Actually during AS3722, I had different understanding to have single fi=\n" + "le.\n" "> >Yes, that way you have each of the the subsystem experts review your\n" "> >documentation. You can then link to them from this document.\n" "> OK, I will add different dt binding doc in respective driver and\n" "> squash that with respected submodule drivers.\n" - "> \n" + ">=20\n" "\n" - "-- \n" + "--=20\n" "Lee Jones\n" "Linaro STMicroelectronics Landing Team Lead\n" - "Linaro.org \342\224\202 Open source software for ARM SoCs\n" + "Linaro.org =E2=94=82 Open source software for ARM SoCs\n" "Follow Linaro: Facebook | Twitter | Blog\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-gpio\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + "\n" + "--=20\n" + "--=20\n" + "You received this message because you are subscribed to \"rtc-linux\".\n" + "Membership options at http://groups.google.com/group/rtc-linux .\n" + "Please read http://groups.google.com/group/rtc-linux/web/checklist\n" + "before submitting a driver.\n" + "---=20\n" + "You received this message because you are subscribed to the Google Groups \"=\n" + "rtc-linux\" group.\n" + "To unsubscribe from this group and stop receiving emails from it, send an e=\n" + "mail to rtc-linux+unsubscribe@googlegroups.com.\n" + For more options, visit https://groups.google.com/d/optout. -a40d7ccaa47e58bb38b78393529fef231b253f8eb0334fb0289c4f718635dbcd +3499e0b86b05c25d8763323ca0f8f2d0e0b90168d9b2135ad056b93884a6fba3
diff --git a/a/1.txt b/N2/1.txt index 64f539b..c84f761 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -73,7 +73,3 @@ Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog --- -To unsubscribe from this list: send the line "unsubscribe linux-gpio" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N2/content_digest index 7811795..dc5109a 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -103,10 +103,6 @@ "Lee Jones\n" "Linaro STMicroelectronics Landing Team Lead\n" "Linaro.org \342\224\202 Open source software for ARM SoCs\n" - "Follow Linaro: Facebook | Twitter | Blog\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-gpio\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + Follow Linaro: Facebook | Twitter | Blog -a40d7ccaa47e58bb38b78393529fef231b253f8eb0334fb0289c4f718635dbcd +8eb0731104b4a39d6c51f34c8d5ed2f8fc4393d5719fc7f420f4e7b830abba06
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.