linux-hwmon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Guenter Roeck <linux@roeck-us.net>,
	Neha Malcom Francis <n-francis@ti.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, jdelvare@suse.com,
	linux-hwmon@vger.kernel.org, nm@ti.com, vigneshr@ti.com,
	u-kumar1@ti.com, kristo@kernel.org
Subject: Re: [PATCH RESEND v3 1/3] dt-bindings: hwmon: esm: Add ESM support for TI K3 devices
Date: Tue, 25 Apr 2023 11:07:06 +0200	[thread overview]
Message-ID: <8ae78a2c-bbf7-24ce-b47f-3d0b7a258ba0@linaro.org> (raw)
In-Reply-To: <0ddd5777-cfd0-4b35-a724-681ef9e86d2b@roeck-us.net>

On 24/04/2023 16:44, Guenter Roeck wrote:
> On Mon, Apr 24, 2023 at 04:20:09PM +0530, Neha Malcom Francis wrote:
>> Document the binding for TI K3 ESM (Error Signaling Module) block.
>>
>> Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
> 
> I think I am missing what this has to do with hardware
> monitoring. I see a driver submission into drivers/misc,
> but that doesn't explain the suggested location of the
> devicetree bindings, and I kind of resist the idea that hwmon
> should be the dumping ground for bindings which don't have
> a home.

Hi Guenter,

This was my suggestion in the previous version, that this device could
look like something related to fault handling or hardware monitoring.
Whether it fits hwmon, I am no sure, just proposed it. Definitely I do
not think of hwmon as dumping ground, but I am rather trying to find
proper place for esm, instead of dumping it in misc (which is a dumping
ground :) ).

https://lore.kernel.org/all/eb6bfe2e-1e44-bfb5-01b9-bbf53eba6501@linaro.org/

Best regards,
Krzysztof


  reply	other threads:[~2023-04-25  9:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 10:50 [PATCH RESEND v3 0/3] Add support for ESM Neha Malcom Francis
2023-04-24 10:50 ` [PATCH RESEND v3 1/3] dt-bindings: hwmon: esm: Add ESM support for TI K3 devices Neha Malcom Francis
2023-04-24 14:38   ` Krzysztof Kozlowski
2023-04-24 14:44   ` Guenter Roeck
2023-04-25  9:07     ` Krzysztof Kozlowski [this message]
2023-04-24 10:50 ` [PATCH RESEND v3 2/3] arm64: dts: ti: k3-j721e: Add ESM support Neha Malcom Francis
2023-04-24 10:50 ` [PATCH RESEND v3 3/3] arm64: dts: ti: k3-j7200: " Neha Malcom Francis
2023-04-24 14:37 ` [PATCH RESEND v3 0/3] Add support for ESM Krzysztof Kozlowski
2023-04-24 14:57 ` Guenter Roeck
2023-04-25  8:49   ` Neha Malcom Francis
2023-04-25 14:34     ` Guenter Roeck
2023-05-01 10:05       ` Krzysztof Kozlowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8ae78a2c-bbf7-24ce-b47f-3d0b7a258ba0@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=n-francis@ti.com \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).