From: Naresh Solanki <naresh.solanki@9elements.com>
To: Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org, Jean Delvare <jdelvare@suse.com>
Cc: broonie@kernel.org,
Patrick Rudolph <patrick.rudolph@9elements.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] hwmon: (pmbus/core): Implement IRQ support
Date: Thu, 24 Nov 2022 14:26:32 +0530 [thread overview]
Message-ID: <df8201b0-414e-4daf-0dae-bd3ce790304c@9elements.com> (raw)
In-Reply-To: <1724dbac-024a-2758-a030-c07352b536fc@roeck-us.net>
Hi Guenter,
On 22-11-2022 10:32 pm, Guenter Roeck wrote:
> On 11/22/22 05:50, Naresh Solanki wrote:
>> From: Patrick Rudolph <patrick.rudolph@9elements.com>
>>
>> Implement IRQ support to monitor PMBUS regulator events.
>>
>> Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
>> Signed-off-by: Naresh Solanki <Naresh.Solanki@9elements.com>
>
> Adding a PMBus interrupt handler should be generic and also handle hwmon
> specific events. It should report any status changes as sysfs attribute
> notifications.
This handler scope is to address regulator faults.
>
> Guenter
>
Regards,
Naresh
next prev parent reply other threads:[~2022-11-24 8:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 13:50 [PATCH 1/3] hwmon: (pmbus/core): Update regulator flag map Naresh Solanki
2022-11-22 13:50 ` [PATCH 2/3] hwmon: (pmbus/core): Add events to " Naresh Solanki
2022-11-22 13:50 ` [PATCH 3/3] hwmon: (pmbus/core): Implement IRQ support Naresh Solanki
2022-11-22 17:02 ` Guenter Roeck
2022-11-24 8:56 ` Naresh Solanki [this message]
2022-11-24 14:07 ` Guenter Roeck
2022-11-24 20:02 ` Naresh Solanki
-- strict thread matches above, loose matches on Subject: below --
2022-11-22 11:32 [PATCH 1/3] hwmon: (pmbus/core): Update regulator flag map Naresh Solanki
2022-11-22 11:32 ` [PATCH 3/3] hwmon: (pmbus/core): Implement IRQ support Naresh Solanki
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=df8201b0-414e-4daf-0dae-bd3ce790304c@9elements.com \
--to=naresh.solanki@9elements.com \
--cc=broonie@kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=patrick.rudolph@9elements.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