diff for duplicates of <4FFD77FE.8050206@nvidia.com> diff --git a/a/1.txt b/N1/1.txt index 3ad84cc..9e071de 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -11,7 +11,8 @@ Tegra uses vendor specific ids to identify the correct frequency table. Following is the proposed binding for voltage and frequency tables used in DVFS. Looking for comments/suggestions to make it generic. -====DVFS table node=========This node defines the voltage configuration for the DVFS which includes +=======DVFS table node=================== +This node defines the voltage configuration for the DVFS which includes the regulator and voltage array. Required properties: @@ -22,7 +23,8 @@ voltage-table : <voltage array, values in mV>; #address-cells and #size-cells : To identify correct frequency table using process id (or some other vendor specific way). -====Frequency table node======= +========Frequency table node=============== + This node defines frequency configuration for the device DVFS. Required properties: @@ -31,7 +33,7 @@ In device node need a reference to the DVFS table node. dvfs : the phandle for the DVFS table node -frequency-table@n +frequency-table at n reg = <n>; dependent on address-cells and size-cells in DVFS table node. frequencies = <frequency array, values in MHz>; @@ -51,12 +53,12 @@ cpu-dvfs-table : dvfs-table { device { dvfs = <&cpu-dvfs-table>; - frequency-table@102 { + frequency-table at 102 { reg = <0x102>; frequencies = <314 314 314 456 456 456 608 608 608 760 817 817 912 1000>; }; - frequency-table@002 { + frequency-table at 002 { reg = <0x002>; frequencies = <598 598 750 750 893 893 1000>; }; diff --git a/a/content_digest b/N1/content_digest index 8be0d71..d253a87 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,7 +1,6 @@ - "ref\020748722.319671342012092123.JavaMail.weblogic@epml17\0" - "From\0Prashant Gaikwad <pgaikwad@nvidia.com>\0" + "From\0pgaikwad@nvidia.com (Prashant Gaikwad)\0" "Subject\0Device tree binding for DVFS table\0" - "Date\0Wed, 11 Jul 2012 13:08:30 +0000\0" + "Date\0Wed, 11 Jul 2012 18:26:30 +0530\0" "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" @@ -18,7 +17,8 @@ "Following is the proposed binding for voltage and frequency tables used \n" "in DVFS. Looking for comments/suggestions to make it generic.\n" "\n" - "====DVFS table node=========This node defines the voltage configuration for the DVFS which includes \n" + "=======DVFS table node===================\n" + "This node defines the voltage configuration for the DVFS which includes \n" "the regulator and voltage array.\n" "\n" "Required properties:\n" @@ -29,7 +29,8 @@ "#address-cells and #size-cells : To identify correct frequency table \n" "using process id (or some other vendor specific way).\n" "\n" - "====Frequency table node=======\n" + "========Frequency table node===============\n" + "\n" "This node defines frequency configuration for the device DVFS.\n" "\n" "Required properties:\n" @@ -38,7 +39,7 @@ "\n" "dvfs : the phandle for the DVFS table node\n" "\n" - "frequency-table@n\n" + "frequency-table at n\n" " reg = <n>; dependent on address-cells and size-cells in DVFS \n" "table node.\n" " frequencies = <frequency array, values in MHz>;\n" @@ -58,12 +59,12 @@ "\n" "device {\n" " dvfs = <&cpu-dvfs-table>;\n" - " frequency-table@102 {\n" + " frequency-table at 102 {\n" " reg = <0x102>;\n" " frequencies = <314 314 314 456 456 456 608 608 \n" "608 760 817 817 912 1000>;\n" " };\n" - " frequency-table@002 {\n" + " frequency-table at 002 {\n" " reg = <0x002>;\n" " frequencies = <598 598 750 750 893 893 1000>;\n" " };\n" @@ -72,4 +73,4 @@ "Thanks & Regards,\n" Prashant G -452cc2976bc7c1ad5a4e7c9298281d398d67c30670d0a60f4bd1a443ebe2fe83 +44b90bd8ddaf02db829a8c1bfd1c6a5f87d532f62565b2eb1d9a97e544b8c9be
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.