From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Ivan Hu <ivan.hu@canonical.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
jesse.huang@portwell.com.tw,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: portwell-ec: Move watchdog device under correct platform hierarchy
Date: Fri, 13 Jun 2025 15:08:13 +0300 (EEST) [thread overview]
Message-ID: <18d60b6c-80c0-85e8-79f5-a41d8a757a46@linux.intel.com> (raw)
In-Reply-To: <20250613082614.28929-1-ivan.hu@canonical.com>
On Fri, 13 Jun 2025, Ivan Hu wrote:
> Without explicitly setting a parent for the watchdog device, the device is
> registered with a NULL parent. This causes device_add() (called internally
> by devm_watchdog_register_device()) to register the device under
> /sys/devices/virtual, since no parent is provided. The result is:
>
> DEVPATH=/devices/virtual/watchdog/watchdog0
>
> To fix this, assign &pdev->dev as the parent of the watchdog device before
> calling devm_watchdog_register_device(). This ensures the device is
> associated with the Portwell EC platform device and placed correctly in
> sysfs as:
>
> DEVPATH=/devices/platform/portwell-ec/watchdog/watchdog0
>
> This aligns the device hierarchy with expectations and avoids misplacement
> under the virtual class.
>
This is missing the Fixes tag.
> Signed-off-by: Ivan Hu <ivan.hu@canonical.com>
> ---
> drivers/platform/x86/portwell-ec.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/platform/x86/portwell-ec.c b/drivers/platform/x86/portwell-ec.c
> index 8b788822237b..3e019c51913e 100644
> --- a/drivers/platform/x86/portwell-ec.c
> +++ b/drivers/platform/x86/portwell-ec.c
> @@ -236,6 +236,7 @@ static int pwec_probe(struct platform_device *pdev)
> return ret;
> }
>
> + ec_wdt_dev.parent = &pdev->dev;
> ret = devm_watchdog_register_device(&pdev->dev, &ec_wdt_dev);
> if (ret < 0) {
> dev_err(&pdev->dev, "failed to register Portwell EC Watchdog\n");
>
--
i.
prev parent reply other threads:[~2025-06-13 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 8:26 Ivan Hu
2025-06-13 12:08 ` Ilpo Järvinen [this message]
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=18d60b6c-80c0-85e8-79f5-a41d8a757a46@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=ivan.hu@canonical.com \
--cc=jesse.huang@portwell.com.tw \
--cc=linux-kernel@vger.kernel.org \
--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 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®