[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <365445ed-8f1d-4c05-90a4-e7867e67977a@linux.dev>
Date: Wed, 24 Apr 2024 18:51:47 +0800
From: Sui Jingfeng <sui.jingfeng@...ux.dev>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
dri-devel@...ts.freedesktop.org, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org, Daniel Scally <djrscally@...il.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH v2] software node: Implement device_get_match_data fwnode
callback
Hi,
On 2024/4/24 16:39, Dmitry Baryshkov wrote:
> Ok, what is the_bug_ that is being fixed by this patch?
I didn't have a way to use that driver under non DT environment,
this is the bug. Note: I demanding full features.
Both st7735r.c and repaper.c requires additional device property.
- For st7735r.c: device_property_read_u32(dev, "rotation", &rotation);
- For repaper.c: device_property_read_string(dev, "pervasive,thermal-zone", &thermal_zone)
Under non DT environment, those device properties can not be read.
Software node backend provided a way. Otherwise, the net results
of the patch doesn't meet the description in the commit message.
> If you check
> the 'submitting-patches.rst', you'll find this phrase as a description
> of the Fixes: tag.
I have readthe 'submitting-patches.rst', the first sentence tell us that
"A Fixes: tag indicates that the patch fixes an issue in a previous commit."
So what's the problem?
>>>> Hence, before my patch is applied, the two "Make driver OF-independent" patch
>>>> have no effect. Using device_get_match_data() itself is exactly*same* with
>>>> using of_device_get_match_data() as long as the .device_get_match_data hook is
>>>> not implemented.
> As far as I can see, repaper correctly handles the case by falling
> back to the spi_id. So does st7735r.c.
Yeah, this explicitly is the issue.
Falling back to other means is robust design, but it explicitly says
that the freshly addeddevice_get_match_data() don't works at all
under non DT environment. This is the bug, so what's you concern?
According to the commit message, the purpose of the introduction of
thedevice_get_match_data() is to achieve OF independent. But as you said,
it will fall back, then how does the goal "Make driver
OF-independent" can be achieved by the patch itself?
--
Best regards,
Sui
Powered by blists - more mailing lists