diff for duplicates of <20748722.319671342012092123.JavaMail.weblogic@epml17> diff --git a/a/1.txt b/N1/1.txt index 67dfec5..4a26875 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,20 +1,29 @@ -PiBIaSwNCj4NCj4gSSBhbSB3b3JraW5nIG9uIERUIGJpbmRpbmcgZm9yIFRlZ3JhIERWRlMuDQo+ -DQo+IEZvciBUZWdyYSwgRFZGUyBub2RlIG1haW5seSBjb25zaXN0cyBvZiBmcmVxdWVuY3kgYW5k -IHZvbHRhZ2UgcGFpcnMuIA0KPiBGcmVxdWVuY3kgaW4gdGhlIHBhaXIgbWF5IGNoYW5nZSBmb3Ig -ZGlmZmVyZW50IHByb2Nlc3MuIEUuZy4gZm9yIHByb2Nlc3MgDQo+IDEgQ1BVIGNsb2NrIGZyZXF1 -ZW5jeSBjb3VsZCBiZSA5MDBNSHogYXQgMVYgd2hpbGUgZm9yIHByb2Nlc3MgMiBpdCBjb3VsZCAN -Cj4gYmUgMUdIeiBhdCAxVi4NCj4gVGVncmEgdXNlcyB2ZW5kb3Igc3BlY2lmaWMgaWRzIHRvIGlk -ZW50aWZ5IHRoZSBjb3JyZWN0IGZyZXF1ZW5jeSB0YWJsZS4NCg0KSGVsbG8sDQoNCkl0IHNlZW1z -IHRoYXQgaW4gdGhlIGV4YW1wbGUsIHRoZSB2YWx1ZXMgaW4gInZvbHRhZ2UtYXJyYXkiIGFuZA0K -ImZyZXF1ZW5jaWVzIiBhcmUgc3dpdGNoZWQuDQoNCkFueXdheSwgd2hhdCBhYm91dCBTb0NzIHRo -YXQgcmVhZHMgaW5mb3JtYXRpb24gZnJvbSBJRU0gKG9yIGFueSBvdGhlciBtb2R1bGUpDQogdG8g -bWVhc3VyZSBnYXRlIGRlbGF5cyBvciBzb21lIG90aGVyIHZhbHVlIHRvIHNldCB0aGUgYXBwcmlv -cmF0ZSB2b2x0YWdlIHZhbHVlcw0KIGZvciBldmVyeSBwb3NzaWJsZSBmcmVxdWVuY3k/IEkgcmVt -ZW1iZXIgc29tZSBvZiBFeHlub3MgU29DcyBoYXZlIGJlZW4gZG9pbmcNCiBpdDsgZHluYW1pY2Fs -bHkgbWVhc3VyZSB0aGUgY2hhcmFjdGVyaXN0aWNzIGF0IGJvb3QtdXAgdGltZSBhbmQgYXBwbHkg -dm9sdGFnZXMNCiBhY2NvcmRpbmdseTsgdGhleSBjb3VsZG4ndCBpZGVudGlmeSBpdCBiYXNlZCBv -biB0aGUgY2hpcC1pZCBvciBzaW1wbHkgYnkgcmVhZGluZw0KIGEgc2luZ2xlIHJlZ2lzdGVyLg0K -DQoNCkNoZWVycyENCk15dW5nSm9vLg0KDQo+IA0KPiBGb2xsb3dpbmcgaXMgdGhlIHByb3Bvc2Vk -IGJpbmRpbmcgZm9yIHZvbHRhZ2UgYW5kIGZyZXF1ZW5jeSB0YWJsZXMgdXNlZCANCj4gaW4gRFZG -Uy4gTG9va2luZyBmb3IgY29tbWVudHMvc3VnZ2VzdGlvbnMgdG8gbWFrZSBpdCBnZW5lcmljLg0K -DQo +> Hi, +> +> I am working on DT binding for Tegra DVFS. +> +> For Tegra, DVFS node mainly consists of frequency and voltage pairs. +> Frequency in the pair may change for different process. E.g. for process +> 1 CPU clock frequency could be 900MHz at 1V while for process 2 it could +> be 1GHz at 1V. +> Tegra uses vendor specific ids to identify the correct frequency table. + +Hello, + +It seems that in the example, the values in "voltage-array" and +"frequencies" are switched. + +Anyway, what about SoCs that reads information from IEM (or any other module) + to measure gate delays or some other value to set the appriorate voltage values + for every possible frequency? I remember some of Exynos SoCs have been doing + it; dynamically measure the characteristics at boot-up time and apply voltages + accordingly; they couldn't identify it based on the chip-id or simply by reading + a single register. + + +Cheers! +MyungJoo. + +> +> Following is the proposed binding for voltage and frequency tables used +> in DVFS. Looking for comments/suggestions to make it generic. diff --git a/a/content_digest b/N1/content_digest index b57972a..47bf4a1 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,28 +1,37 @@ - "From\0\355\225\250\353\252\205\354\243\274 <myungjoo.ham@samsung.com>\0" - "Subject\0Re: Device tree binding for DVFS table\0" - "Date\0Wed, 11 Jul 2012 13:08:14 +0000\0" + "From\0myungjoo.ham@samsung.com (\355\225\250\353\252\205\354\243\274)\0" + "Subject\0Device tree binding for DVFS table\0" + "Date\0Wed, 11 Jul 2012 13:08:15 +0000 (GMT)\0" "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" - "PiBIaSwNCj4NCj4gSSBhbSB3b3JraW5nIG9uIERUIGJpbmRpbmcgZm9yIFRlZ3JhIERWRlMuDQo+\n" - "DQo+IEZvciBUZWdyYSwgRFZGUyBub2RlIG1haW5seSBjb25zaXN0cyBvZiBmcmVxdWVuY3kgYW5k\n" - "IHZvbHRhZ2UgcGFpcnMuIA0KPiBGcmVxdWVuY3kgaW4gdGhlIHBhaXIgbWF5IGNoYW5nZSBmb3Ig\n" - "ZGlmZmVyZW50IHByb2Nlc3MuIEUuZy4gZm9yIHByb2Nlc3MgDQo+IDEgQ1BVIGNsb2NrIGZyZXF1\n" - "ZW5jeSBjb3VsZCBiZSA5MDBNSHogYXQgMVYgd2hpbGUgZm9yIHByb2Nlc3MgMiBpdCBjb3VsZCAN\n" - "Cj4gYmUgMUdIeiBhdCAxVi4NCj4gVGVncmEgdXNlcyB2ZW5kb3Igc3BlY2lmaWMgaWRzIHRvIGlk\n" - "ZW50aWZ5IHRoZSBjb3JyZWN0IGZyZXF1ZW5jeSB0YWJsZS4NCg0KSGVsbG8sDQoNCkl0IHNlZW1z\n" - "IHRoYXQgaW4gdGhlIGV4YW1wbGUsIHRoZSB2YWx1ZXMgaW4gInZvbHRhZ2UtYXJyYXkiIGFuZA0K\n" - "ImZyZXF1ZW5jaWVzIiBhcmUgc3dpdGNoZWQuDQoNCkFueXdheSwgd2hhdCBhYm91dCBTb0NzIHRo\n" - "YXQgcmVhZHMgaW5mb3JtYXRpb24gZnJvbSBJRU0gKG9yIGFueSBvdGhlciBtb2R1bGUpDQogdG8g\n" - "bWVhc3VyZSBnYXRlIGRlbGF5cyBvciBzb21lIG90aGVyIHZhbHVlIHRvIHNldCB0aGUgYXBwcmlv\n" - "cmF0ZSB2b2x0YWdlIHZhbHVlcw0KIGZvciBldmVyeSBwb3NzaWJsZSBmcmVxdWVuY3k/IEkgcmVt\n" - "ZW1iZXIgc29tZSBvZiBFeHlub3MgU29DcyBoYXZlIGJlZW4gZG9pbmcNCiBpdDsgZHluYW1pY2Fs\n" - "bHkgbWVhc3VyZSB0aGUgY2hhcmFjdGVyaXN0aWNzIGF0IGJvb3QtdXAgdGltZSBhbmQgYXBwbHkg\n" - "dm9sdGFnZXMNCiBhY2NvcmRpbmdseTsgdGhleSBjb3VsZG4ndCBpZGVudGlmeSBpdCBiYXNlZCBv\n" - "biB0aGUgY2hpcC1pZCBvciBzaW1wbHkgYnkgcmVhZGluZw0KIGEgc2luZ2xlIHJlZ2lzdGVyLg0K\n" - "DQoNCkNoZWVycyENCk15dW5nSm9vLg0KDQo+IA0KPiBGb2xsb3dpbmcgaXMgdGhlIHByb3Bvc2Vk\n" - "IGJpbmRpbmcgZm9yIHZvbHRhZ2UgYW5kIGZyZXF1ZW5jeSB0YWJsZXMgdXNlZCANCj4gaW4gRFZG\n" - "Uy4gTG9va2luZyBmb3IgY29tbWVudHMvc3VnZ2VzdGlvbnMgdG8gbWFrZSBpdCBnZW5lcmljLg0K\n" - DQo + "> Hi,\n" + ">\n" + "> I am working on DT binding for Tegra DVFS.\n" + ">\n" + "> For Tegra, DVFS node mainly consists of frequency and voltage pairs. \n" + "> Frequency in the pair may change for different process. E.g. for process \n" + "> 1 CPU clock frequency could be 900MHz at 1V while for process 2 it could \n" + "> be 1GHz at 1V.\n" + "> Tegra uses vendor specific ids to identify the correct frequency table.\n" + "\n" + "Hello,\n" + "\n" + "It seems that in the example, the values in \"voltage-array\" and\n" + "\"frequencies\" are switched.\n" + "\n" + "Anyway, what about SoCs that reads information from IEM (or any other module)\n" + " to measure gate delays or some other value to set the appriorate voltage values\n" + " for every possible frequency? I remember some of Exynos SoCs have been doing\n" + " it; dynamically measure the characteristics at boot-up time and apply voltages\n" + " accordingly; they couldn't identify it based on the chip-id or simply by reading\n" + " a single register.\n" + "\n" + "\n" + "Cheers!\n" + "MyungJoo.\n" + "\n" + "> \n" + "> Following is the proposed binding for voltage and frequency tables used \n" + > in DVFS. Looking for comments/suggestions to make it generic. -d6f472f6c9335d0dedb31fa5f235cc1e9371dfd867a795d93c3623c050c5a514 +317f7a770115352d3875cd791bd0795a837fe6c13077c4c82896740297d52108
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.