mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "João Paulo Gonçalves" <jpaulo.silvagoncalves@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	 Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	 Watson Chow <watson.chow@avnet.com>
Cc: linux-kernel@vger.kernel.org,
	"João Paulo Gonçalves" <jpaulo.silvagoncalves@gmail.com>,
	stable@vger.kernel.org
Subject: [PATCH 0/2] regulator: max20086: Fixes chip id and enable gpio
Date: Sun, 20 Apr 2025 15:28:00 -0300	[thread overview]
Message-ID: <20250420-fix-max20086-v1-0-8cc9ee0d5a08@gmail.com> (raw)

Hello,

I'm working on integrating a system with a MAX20086 and noticed these
small issues in the driver: the chip ID for MAX20086 is 0x30 and not
0x40. Also, in my use case, the enable pin is always enabled by
hardware, so the enable GPIO isn't needed. Without these changes, the
driver fails to probe.

Signed-off-by: João Paulo Gonçalves <jpaulo.silvagoncalves@gmail.com>
---
João Paulo Gonçalves (2):
      regulator: max20086: Fix MAX200086 chip id
      regulator: max20086: Change enable gpio to optional

 drivers/regulator/max20086-regulator.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
---
base-commit: 6fea5fabd3323cd27b2ab5143263f37ff29550cb
change-id: 20250420-fix-max20086-430a63f7a9eb

Best regards,
-- 
João Paulo Gonçalves <jpaulo.silvagoncalves@gmail.com>


             reply	other threads:[~2025-04-20 18:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-20 18:28 João Paulo Gonçalves [this message]
2025-04-20 18:28 ` [PATCH 1/2] regulator: max20086: Fix MAX200086 chip id João Paulo Gonçalves
2025-04-20 18:28 ` [PATCH 2/2] regulator: max20086: Change enable gpio to optional João Paulo Gonçalves
2025-04-23 13:49 ` [PATCH 0/2] regulator: max20086: Fixes chip id and enable gpio Mark Brown

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=20250420-fix-max20086-v1-0-8cc9ee0d5a08@gmail.com \
    --to=jpaulo.silvagoncalves@gmail.com \
    --cc=broonie@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=watson.chow@avnet.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
all inboxes | Powered by JetHome®