From: Chintan Patel <chintanlike@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, tzimmermann@suse.de,
andy@kernel.org, deller@gmx.de, gregkh@linuxfoundation.org
Subject: Re: [PATCH v2 2/4] staging: fbtft: Make FB_DEVICE dependency optional
Date: Sat, 27 Dec 2025 19:36:03 -0800 [thread overview]
Message-ID: <ec86f093-8fe8-4fc8-b330-dc7ee8a01de9@gmail.com> (raw)
In-Reply-To: <CAHp75VeLF8nd-JiPFnxJ2H43ZS=oYgW4=BTZjR_GuUuj03gyRg@mail.gmail.com>
Hi Andy,
On 12/27/25 06:19, Andy Shevchenko wrote:
> On Fri, Dec 19, 2025 at 7:43 AM Chintan Patel <chintanlike@gmail.com> wrote:
>>
>> fbtft provides sysfs interfaces for debugging and gamma configuration,
>> but these are not required for the core driver.
>>
>> Drop the hard dependency on CONFIG_FB_DEVICE and make sysfs support
>> optional by using dev_of_fbinfo() at runtime. When FB_DEVICE is disabled,
>> sysfs operations are skipped while the code remains buildable and
>> type-checked.
>
>> v2:
>> - Replace CONFIG_FB_DEVICE ifdefs with runtime checks
>> - Use dev_of_fbinfo() to guard sysfs creation and removal
>
> The place for the change log is either a cover letter, or...
>
>> Suggested-by: Thomas Zimmermann <tzimmermann@suse.de>
>> Suggested-by: Helge Deller <deller@gmx.de>
>> Signed-off-by: Chintan Patel <chintanlike@gmail.com>
>> ---
>
> ...a comment block here. It's not so important to be in the Git
> history since we have a lore.kernel.org archive.
Thank you for suggestion! Will move to coverletter.
>> drivers/staging/fbtft/Kconfig | 5 ++++-
>> drivers/staging/fbtft/fbtft-sysfs.c | 18 ++++++++++++++----
>
> ...
>
>> void fbtft_sysfs_init(struct fbtft_par *par)
>> {
>> - device_create_file(par->info->dev, &debug_device_attr);
>> + struct device *dev = dev_of_fbinfo(par->info);
>> +
>> + if (!dev)
>> + return;
>
>
> The better way is to decouple the definition and the assignment in the
> cases when it's followed by a conditional (validation check). In this
> case any new code added in between doesn't affect readability and
> maintenance efforts.
>
> struct device *dev;
>
> dev = dev_of_fbinfo(par->info);
> if (!dev)
> return;
>
>> + device_create_file(dev, &debug_device_attr);
>> if (par->gamma.curves && par->fbtftops.set_gamma)
>> - device_create_file(par->info->dev, &gamma_device_attrs[0]);
>> + device_create_file(dev, &gamma_device_attrs[0]);
>> }
>
> Ditto for the rest.
Will do v3 and re-send. Thanks for reviews!
next prev parent reply other threads:[~2025-12-28 3:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 5:43 [PATCH v2 0/4] fbdev: Make CONFIG_FB_DEVICE optional for drivers Chintan Patel
2025-12-19 5:43 ` [PATCH v2 1/4] fb: Add dev_of_fbinfo() helper for optional sysfs support Chintan Patel
2025-12-27 14:23 ` Andy Shevchenko
2025-12-19 5:43 ` [PATCH v2 2/4] staging: fbtft: Make FB_DEVICE dependency optional Chintan Patel
2025-12-27 14:15 ` Andy Shevchenko
2025-12-27 14:19 ` Andy Shevchenko
2025-12-28 3:36 ` Chintan Patel [this message]
2025-12-19 5:43 ` [PATCH v2 3/4] fbdev: omapfb: " Chintan Patel
2025-12-19 5:43 ` [PATCH v2 4/4] fbdev: sh_mobile_lcdc: " Chintan Patel
2025-12-27 14:21 ` Andy Shevchenko
2025-12-27 14:24 ` [PATCH v2 0/4] fbdev: Make CONFIG_FB_DEVICE optional for drivers Andy Shevchenko
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=ec86f093-8fe8-4fc8-b330-dc7ee8a01de9@gmail.com \
--to=chintanlike@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).