diff for duplicates of <4E375998.1020901@freescale.com> diff --git a/a/1.txt b/N1/1.txt index 9d000e7..8ec35d2 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -2,26 +2,25 @@ Mark Brown wrote: > I'd expect that things like the _lowest, _highest and _average > attributes which a number of drivers have are what you're looking for. -Yes, but then all I'm doing is presenting numbers that don't change to an=20 +Yes, but then all I'm doing is presenting numbers that don't change to an interface, simply on the basis that the numbers represent sensor values. -If I'm running a sensor application, I'm doing it to get real-time=20 -monitoring of the sensors in my system. The DCM on our boards is not=20 -capable of real-time results. So you're not actually "monitoring" the=20 -hardware. The data from the DCM is available only *after* you stop=20 +If I'm running a sensor application, I'm doing it to get real-time +monitoring of the sensors in my system. The DCM on our boards is not +capable of real-time results. So you're not actually "monitoring" the +hardware. The data from the DCM is available only *after* you stop running the background process. > At the very least it seems obvious how you might extend the interface if > some features you need are missing. The subsystem has fairly extensive > documentation in Documentation/hwmon. -I just don't see how it fits. Yes, I could do it, but then I'd end up=20 -with something that doesn't make any sense. I would have to use a custom=20 -interface to start monitoring and then another interface to stop it. Then= -=20 -I would query the results use the hwmon interface, but the results would=20 +I just don't see how it fits. Yes, I could do it, but then I'd end up +with something that doesn't make any sense. I would have to use a custom +interface to start monitoring and then another interface to stop it. Then +I would query the results use the hwmon interface, but the results would be static. That just seems silly. ---=20 +-- Timur Tabi -Linux kernel developer at Freescale= +Linux kernel developer at Freescale diff --git a/a/content_digest b/N1/content_digest index c5b01b2..47a3a64 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -6,37 +6,37 @@ "Subject\0Re: [PATCH] drivers/misc: introduce Freescale Data Collection Manager driver\0" "Date\0Tue, 2 Aug 2011 01:57:45 +0000\0" "To\0Mark Brown <broonie@opensource.wolfsonmicro.com>\0" - "Cc\0linuxppc-dev@ozlabs.org <linuxppc-dev@ozlabs.org>" - linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> - " arnd@arndb.de <arnd@arndb.de>\0" + "Cc\0arnd@arndb.de <arnd@arndb.de>" + grant.likely@secretlab.ca <grant.likely@secretlab.ca> + linuxppc-dev@ozlabs.org <linuxppc-dev@ozlabs.org> + " linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>\0" "\00:1\0" "b\0" "Mark Brown wrote:\n" "> I'd expect that things like the _lowest, _highest and _average\n" "> attributes which a number of drivers have are what you're looking for.\n" "\n" - "Yes, but then all I'm doing is presenting numbers that don't change to an=20\n" + "Yes, but then all I'm doing is presenting numbers that don't change to an \n" "interface, simply on the basis that the numbers represent sensor values.\n" "\n" - "If I'm running a sensor application, I'm doing it to get real-time=20\n" - "monitoring of the sensors in my system. The DCM on our boards is not=20\n" - "capable of real-time results. So you're not actually \"monitoring\" the=20\n" - "hardware. The data from the DCM is available only *after* you stop=20\n" + "If I'm running a sensor application, I'm doing it to get real-time \n" + "monitoring of the sensors in my system. The DCM on our boards is not \n" + "capable of real-time results. So you're not actually \"monitoring\" the \n" + "hardware. The data from the DCM is available only *after* you stop \n" "running the background process.\n" "\n" "> At the very least it seems obvious how you might extend the interface if\n" "> some features you need are missing. The subsystem has fairly extensive\n" "> documentation in Documentation/hwmon.\n" "\n" - "I just don't see how it fits. Yes, I could do it, but then I'd end up=20\n" - "with something that doesn't make any sense. I would have to use a custom=20\n" - "interface to start monitoring and then another interface to stop it. Then=\n" - "=20\n" - "I would query the results use the hwmon interface, but the results would=20\n" + "I just don't see how it fits. Yes, I could do it, but then I'd end up \n" + "with something that doesn't make any sense. I would have to use a custom \n" + "interface to start monitoring and then another interface to stop it. Then \n" + "I would query the results use the hwmon interface, but the results would \n" "be static. That just seems silly.\n" "\n" - "--=20\n" + "-- \n" "Timur Tabi\n" - Linux kernel developer at Freescale= + Linux kernel developer at Freescale -f71a7e1416b9787be41308ae401a3da7b8b5d48ae83ec1ead5f35729a3fffbfb +265a0291d5972ebc2ca0891032d33d1cffd62cae1f176af19650cd9e194546dd
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.