All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Linus Walleij <linusw@kernel.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v1 1/1] serial: core: Restore sysfs fwnode information
Date: Mon, 29 Dec 2025 14:38:04 +0200	[thread overview]
Message-ID: <aVJ2LFT-ywYzJ3Jo@smile.fi.intel.com> (raw)
In-Reply-To: <hwykqbo2ktw4slmmb2iodeitd5fqfvzuec5eyvgnttyh3keo3h@cibdr37t4shy>

On Mon, Dec 29, 2025 at 05:18:14AM +0200, Dmitry Baryshkov wrote:
> On Mon, Dec 22, 2025 at 11:55:26AM +0100, Marek Szyprowski wrote:

...

> I can confirm that this patch fixes the breakage on Qualcomm devices.
> Please send it as a proper patch (though I'd say, the flag should only
> be set only if dev->of_node != NULL).
> 
> An alternative is to introduce dev_set_node_from_dev() which mimics both
> dev_set_node() and device_set_of_node_from_dev().

While I am on vacation, I have a brief look at the report and fix and the
discussion. There are several ongoing tasks that may collide with this:

- the desire to split device.h, so we have something like device/fwnode.h with
all related APIs listed there

- taking these, it might be good to have device_set_used_node() as a combination
of the above and also device_is_node_used() to be used in its solely user of pin
control core

- the proper understanding of this flag to begin with and how it may be related
to ACPI-based platforms (or non-DT in general)

- with that done, it might be a room to see if the flag actually should be
somewhere in fwnode structure or elsewhere

- or we can revisit the whole design and see if we can get rid of the flag

+Cc: Linus for searching for his comments, thoughts, etc.

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2025-12-29 12:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20251218152957eucas1p196470bc80be0d8a4037edfe6e53f3d13@eucas1p1.samsung.com>
2025-11-27 16:36 ` [PATCH v1 1/1] serial: core: Restore sysfs fwnode information Andy Shevchenko
2025-11-27 19:07   ` Greg Kroah-Hartman
2025-12-18 13:50   ` Cosmin Tanislav
2025-12-18 15:29   ` Marek Szyprowski
2025-12-18 16:54     ` Mark Brown
2025-12-22 10:55       ` Marek Szyprowski
2025-12-29  3:18         ` Dmitry Baryshkov
2025-12-29 12:38           ` Andy Shevchenko [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=aVJ2LFT-ywYzJ3Jo@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=m.szyprowski@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 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.