From: sashiko-bot@kernel.org
To: "ChunAn Wu" <an.wu@canonical.com>, linux-serial@vger.kernel.org
Subject: Re: [PATCH v3 1/3] serdev: handle devices without an ACPI or device tree node
Date: Fri, 23 Oct 2026 05:33:54 +0000 [thread overview]
Message-ID: <sashiko-outbox-182317@kernel.org> (raw)
In-Reply-To: <20261023052717.2577234-2-an.wu@canonical.com>
> Serdev clients instantiated by a driver have no ACPI companion and no
> device tree node. Their modalias read returns -ENODEV, their add uevent
> is suppressed, and they cannot be driver-matched, so creators force a
> bind with device_driver_attach().
>
> Resolve both TODOs in the serdev core by modelling matching on the SPI
> bus: add a creator-set modalias to struct serdev_device and an id_table
> to struct serdev_device_driver. ACPI and OF are still tried first;
> clients without their own modalias keep returning -ENODEV. The device
> name, derived from the controller, is unchanged.
>
> Signed-off-by: ChunAn Wu <an.wu@canonical.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261023052717.2577234-1-an.wu@canonical.com?part=1
next prev parent reply other threads:[~2026-10-23 5:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 5:27 [PATCH v3 0/3] serdev: handle devices without an ACPI or device tree ChunAn Wu
2026-10-23 5:27 ` [PATCH v3 1/3] serdev: handle devices without an ACPI or device tree node ChunAn Wu
2026-10-23 5:33 ` sashiko-bot [this message]
2026-10-23 12:26 ` Markus Probst
2026-10-23 13:02 ` An Wu
2026-10-23 5:27 ` [PATCH v3 2/3] platform/x86: dell-uart-backlight: Bind through normal serdev matching ChunAn Wu
2026-10-23 5:32 ` sashiko-bot
2026-10-23 5:27 ` [PATCH v3 3/3] platform/x86: lenovo-yoga-tab2-pro-1380-fastcharger: " ChunAn Wu
2026-10-23 5:39 ` sashiko-bot
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=sashiko-outbox-182317@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=an.wu@canonical.com \
--cc=linux-serial@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.