diff for duplicates of <56FBE345.5030806@opensource.altera.com> diff --git a/a/1.txt b/N1/1.txt index 2b6c3be..4720a81 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,32 +1,47 @@ + On 03/29/2016 05:29 PM, Mark Brown wrote: -> On Tue, Mar 29, 2016 at 04:43:41PM -0500, Thor Thayer wrote: -> ->> Yes, I see your point. In looking at the regulator drivers, I interpret ->> those as being controlled by the driver whereas this chip is passively ->> reporting status. -> -> If the device isn't doing regulation it's not a regulator. -> ->> After reading the referenced document, I agree that hwmon probably isn't ->> appropriate. However, the regulator doesn't seem appropriate either (the ->> only status appears to be tied to battery properties). -> -> We report status for regulators but that's tied to monitoring that's -> built into a device that does regulation. -> -> How about IIO or power supply? -> + +On Tue, Mar 29, 2016 at 04:43:41PM -0500, Thor Thayer wrote: + + +Yes, I see your point. In looking at the regulator drivers, I interpret +those as being controlled by the driver whereas this chip is passively +reporting status. + + +If the device isn't doing regulation it's not a regulator. + + +After reading the referenced document, I agree that hwmon probably isn't +appropriate. However, the regulator doesn't seem appropriate either (the +only status appears to be tied to battery properties). + + +We report status for regulators but that's tied to monitoring that's +built into a device that does regulation. + +How about IIO or power supply? + + Hi Mark, Thanks for the clarification and for pointing out other frameworks to look at. + Yes, I think the iio may be a good place but I'll need to investigate where it should go. I'm not sure it fits into the adc subdirectory. I see similar functionality in the MAX1363 part but it's not actually an ADC - it only has the supervisor compare functionality. + Thank you! + + +-- +To unsubscribe from this list: send the line "unsubscribe linux-hwmon" in +the body of a message to majord...@vger.kernel.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index d78c21e..c136fc7 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,59 +1,56 @@ "ref\01459278791-3646-1-git-send-email-tthayer@opensource.altera.com\0" - "ref\01459278791-3646-8-git-send-email-tthayer@opensource.altera.com\0" - "ref\020160329201648.GA30248@roeck-us.net\0" - "ref\056FAF70D.4010109@opensource.altera.com\0" - "ref\020160329222927.GS2350@sirena.org.uk\0" "From\0Thor Thayer <tthayer@opensource.altera.com>\0" "Subject\0Re: [RFC 7/8] hwmon: Altera Arria10 System Resource Chip - HW Monitor\0" - "Date\0Wed, 30 Mar 2016 09:31:33 -0500\0" - "To\0Mark Brown <broonie@kernel.org>\0" - "Cc\0Guenter Roeck <linux@roeck-us.net>" - lee.jones@linaro.org - linus.walleij@linaro.org - gnurou@gmail.com - jdelvare@suse.com - robh+dt@kernel.org - pawel.moll@arm.com - mark.rutland@arm.com - ijc+devicetree@hellion.org.uk - dinguyen@opensource.altera.com - linux-gpio@vger.kernel.org - linux-hwmon@vger.kernel.org - devicetree@vger.kernel.org - " lgirdwood@gmail.com\0" + "Date\0Wed, 30 Mar 2016 07:27:36 -0700\0" + "To\0linux-hwmon@vger.kernel.org\0" "\00:1\0" "b\0" "\n" "\n" + "\n" "On 03/29/2016 05:29 PM, Mark Brown wrote:\n" - "> On Tue, Mar 29, 2016 at 04:43:41PM -0500, Thor Thayer wrote:\n" - ">\n" - ">> Yes, I see your point. In looking at the regulator drivers, I interpret\n" - ">> those as being controlled by the driver whereas this chip is passively\n" - ">> reporting status.\n" - ">\n" - "> If the device isn't doing regulation it's not a regulator.\n" - ">\n" - ">> After reading the referenced document, I agree that hwmon probably isn't\n" - ">> appropriate. However, the regulator doesn't seem appropriate either (the\n" - ">> only status appears to be tied to battery properties).\n" - ">\n" - "> We report status for regulators but that's tied to monitoring that's\n" - "> built into a device that does regulation.\n" - ">\n" - "> How about IIO or power supply?\n" - ">\n" + "\n" + "On Tue, Mar 29, 2016 at 04:43:41PM -0500, Thor Thayer wrote:\n" + "\n" + "\n" + "Yes, I see your point. In looking at the regulator drivers, I interpret\n" + "those as being controlled by the driver whereas this chip is passively\n" + "reporting status.\n" + "\n" + "\n" + "If the device isn't doing regulation it's not a regulator.\n" + "\n" + "\n" + "After reading the referenced document, I agree that hwmon probably isn't\n" + "appropriate. However, the regulator doesn't seem appropriate either (the\n" + "only status appears to be tied to battery properties).\n" + "\n" + "\n" + "We report status for regulators but that's tied to monitoring that's\n" + "built into a device that does regulation.\n" + "\n" + "How about IIO or power supply?\n" + "\n" + "\n" "\n" "Hi Mark,\n" "\n" "Thanks for the clarification and for pointing out other frameworks to \n" "look at.\n" "\n" + "\n" "Yes, I think the iio may be a good place but I'll need to investigate \n" "where it should go. I'm not sure it fits into the adc subdirectory. I \n" "see similar functionality in the MAX1363 part but it's not actually an \n" "ADC - it only has the supervisor compare functionality.\n" "\n" - Thank you! + "\n" + "Thank you!\n" + "\n" + "\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe linux-hwmon\" in\n" + "the body of a message to majord...@vger.kernel.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -63b4be3ee9dafc4f7ea717469770ebeb0efa0c24b5ab6cd39e99ca5a592b23a8 +36162ff4d6cb8a33f12487d783bb529fd0cabaea1ed26d1e3db8d2f45b40ce60
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.