From: Chanwoo Choi <chanwoo@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Chanwoo Choi <chanwoo@kernel.org>,
MyungJoo Ham <myungjoo.ham@samsung.com>
Subject: [GIT PULL] extcon next for 6.17
Date: Sat, 26 Jul 2025 09:34:47 +0900 [thread overview]
Message-ID: <15ca3763-45a5-40af-93a8-449a9f1f33a9@kernel.org> (raw)
Dear Greg,
This is extcon-next pull request. I add detailed description of
this pull request on below. Please pull extcon with following updates.
Best Regards,
Chanwoo Choi
The following changes since commit 86731a2a651e58953fc949573895f2fa6d456841:
Linux 6.16-rc3 (2025-06-22 13:30:08 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git tags/extcon-next-for-6.17
for you to fetch changes up to 5f09caafc652bcee7a5247e40dd34d1de1ad7d7f:
extcon: fsa9480: Avoid buffer overflow in fsa9480_handle_change() (2025-07-19 12:39:13 +0900)
----------------------------------------------------------------
Update extcon next for v6.17
Detailed description for this pull request:
- Fix wakeup source leaks on device unbind for extcon drivers
- Add new Maxim MAX14526 MUIC extcon driver and dt-binding document
: The MAX14526 is designed to simplify interface requirements on portable
devices by multiplexing common inputs (USB, UART, Microphone, Stereo Audio
and Composite Video) on a single micro/mini USB connector. The USB input
supports Hi-Speed USB and the audio/video inputs feature
: This provides the following supported external connector detection
- EXTCON_USB
- EXTCON_USB_HOST
- EXTCON_CHG_USB_FAST
- EXTCON_DISP_MHL
- Fix buffer overflow detected by linuxtesting.org SVACE on extcon-fsa9480.c
----------------------------------------------------------------
Krzysztof Kozlowski (5):
extcon: adc-jack: Fix wakeup source leaks on device unbind
extcon: axp288: Fix wakeup source leaks on device unbind
extcon: fsa9480: Fix wakeup source leaks on device unbind
extcon: qcom-spmi-misc: Fix wakeup source leaks on device unbind
extcon: adc-jack: Cleanup wakeup source only if it was enabled
Randy Dunlap (2):
extcon: max14526: avoid defined but not used warning
extcon: max14526: depends on I2C to prevent build warning/errors
Svyatoslav Ryhel (2):
dt-bindings: extcon: Document Maxim MAX14526 MUIC
extcon: Add basic support for Maxim MAX14526 MUIC
Vladimir Moskovkin (1):
extcon: fsa9480: Avoid buffer overflow in fsa9480_handle_change()
.../devicetree/bindings/extcon/maxim,max14526.yaml | 80 ++++++
drivers/extcon/Kconfig | 13 +
drivers/extcon/Makefile | 1 +
drivers/extcon/extcon-adc-jack.c | 2 +
drivers/extcon/extcon-axp288.c | 2 +-
drivers/extcon/extcon-fsa9480.c | 6 +-
drivers/extcon/extcon-max14526.c | 302 +++++++++++++++++++++
drivers/extcon/extcon-qcom-spmi-misc.c | 2 +-
8 files changed, 404 insertions(+), 4 deletions(-)
create mode 100644 Documentation/devicetree/bindings/extcon/maxim,max14526.yaml
create mode 100644 drivers/extcon/extcon-max14526.c
next reply other threads:[~2025-07-26 0:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-26 0:34 Chanwoo Choi [this message]
2025-07-26 6:53 ` [GIT PULL] extcon next for 6.17 Greg Kroah-Hartman
2025-08-01 13:31 ` Chanwoo Choi
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=15ca3763-45a5-40af-93a8-449a9f1f33a9@kernel.org \
--to=chanwoo@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.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