linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: nuno.sa@analog.com, linux-hwmon@vger.kernel.org,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-doc@vger.kernel.org
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jean Delvare <jdelvare@suse.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v4 2/3] hwmon: ltc4283: Add support for the LTC4283 Swap Controller
Date: Sat, 6 Dec 2025 10:40:19 -0800	[thread overview]
Message-ID: <144d50f7-398c-4b10-bd21-a6d0c6c7b4c8@roeck-us.net> (raw)
In-Reply-To: <20251204-ltc4283-support-v4-2-db0197fd7984@analog.com>

On 12/4/25 08:15, Nuno Sá via B4 Relay wrote:
> From: Nuno Sá <nuno.sa@analog.com>
> 
> Support the LTC4283 How Swap Controller. The device features programmable
> current limit with foldback and independently adjustable inrush current to
> optimize the MOSFET safe operating area (SOA). The SOA timer limits MOSFET
> temperature rise for reliable protection against overstresses.
> 
> An I2C interface and onboard ADC allow monitoring of board current,
> voltage, power, energy, and fault status.
> 
> Signed-off-by: Nuno Sá <nuno.sa@analog.com>

I finally found the time to write module test code for the driver.

Some early feedback:

- The driver must work with non-devicetree systems and without device
   property support. Select defaults where necessary.
- Attributes marked as readable in the is_visible function must be readable.
   It is not acceptable to return -EOPNOTSUPP. That applies to all
   reset_history attributes and maybe to others.
- regmap is configured for 8 bit accesses, but some registers are 16 bit wide.
   The energy register is 48 bit wide, I am not sure if it is safe to use
   regmap_bulk_read() to bypass that. At the very least it seems risky.
   Is there some regmap documentation that guarantees that a bulk operation
   is always executed as a real bulk operation, not as sequence of 8-bit
   operations ? How does this even work to start with on a system with SMBus
   controller ?

Thanks,
Guenter


  reply	other threads:[~2025-12-06 18:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 16:15 [PATCH v4 0/3] hwmon: Add support for the LTC4283 Hot Swap Controller Nuno Sá via B4 Relay
2025-12-04 16:15 ` [PATCH v4 1/3] dt-bindings: hwmon: Document the LTC4283 " Nuno Sá via B4 Relay
2025-12-04 16:15 ` [PATCH v4 2/3] hwmon: ltc4283: Add support for " Nuno Sá via B4 Relay
2025-12-06 18:40   ` Guenter Roeck [this message]
2025-12-12 16:34     ` Nuno Sá
2025-12-12 16:46       ` Guenter Roeck
2025-12-12 16:55         ` Nuno Sá
2025-12-12 17:21           ` Guenter Roeck
2025-12-12 17:31           ` Guenter Roeck
2025-12-11 17:56   ` Guenter Roeck
2025-12-12 16:50     ` Nuno Sá
2025-12-12 17:07       ` Guenter Roeck
2025-12-04 16:15 ` [PATCH v4 3/3] gpio: gpio-ltc4283: " Nuno Sá via B4 Relay
2025-12-10 23:46   ` Linus Walleij

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=144d50f7-398c-4b10-bd21-a6d0c6c7b4c8@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=brgl@bgdev.pl \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=nuno.sa@analog.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).