All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vasu <vasuhansalia05@gmail.com>
To: andriy.shevchenko@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	djrscally@gmail.com, mika.westerberg@linux.intel.com,
	Vasu Hansalia <vasuhansalia05@gmail.com>
Subject: Re: [PATCH 1/2] pinctrl: intel: platform: Add INTC10B5 ACPI ID for Lunar Lake
Date: Sun,  5 Apr 2026 22:03:06 +0530	[thread overview]
Message-ID: <20260405163420.16654-1-vasuhansalia05@gmail.com> (raw)
In-Reply-To: <adKLLO1oKOy1tjdo@ashevche-desk.local>

From: Vasu Hansalia <vasuhansalia05@gmail.com>

Thank you for the clarification Andy.

Confirmed — the LJCA drivers (gpio-usbio and usb-ljca) are present
and loaded on the system:

  $ lsmod | grep -E "usbio|ljca"
  i2c_usbio    12288  0
  gpio_usbio   12288  2
  usbio        20480  2 gpio_usbio,i2c_usbio

You are correct, Patch 1 is not needed. I will drop it.

For Patch 2, I will follow stable-kernel-rules.rst to request the
backport of INT3472_GPIO_TYPE_HANDSHAKE to the Ubuntu OEM kernels.

Thank you for your patience and guidance throughout this process.

Regards,
Vasu Hansalia

  reply	other threads:[~2026-04-05 16:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-04 19:02 [PATCH 1/2] pinctrl: intel: platform: Add INTC10B5 ACPI ID for Lunar Lake Vasu
2026-04-04 19:02 ` [PATCH 2/2] platform/x86: int3472: Handle GPIO types 0x02 and 0x12 " Vasu
2026-04-04 19:55   ` Andy Shevchenko
2026-04-05  1:34     ` Vasu
2026-04-05  9:01       ` Andy Shevchenko
2026-04-05  9:15         ` Vasu
2026-04-05  9:27         ` Vasu
2026-04-05 16:10           ` Andy Shevchenko
2026-04-04 19:52 ` [PATCH 1/2] pinctrl: intel: platform: Add INTC10B5 ACPI ID " Andy Shevchenko
2026-04-05  1:34   ` Vasu
2026-04-05  8:59     ` Andy Shevchenko
2026-04-05  9:15       ` Vasu
2026-04-05 16:17         ` Andy Shevchenko
2026-04-05 16:33           ` Vasu [this message]
2026-04-05  2:07   ` Vasu

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=20260405163420.16654-1-vasuhansalia05@gmail.com \
    --to=vasuhansalia05@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=djrscally@gmail.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.