From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <davidgow@google.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
kunit-dev@googlegroups.com, Stephen Boyd <sboyd@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v6 3/7] kunit: Add kunit wrappers for (root) device creation
Date: Mon, 27 Mar 2023 14:38:14 +0200 [thread overview]
Message-ID: <ZCGONl0mC8oyBj-0@kroah.com> (raw)
In-Reply-To: <e027fc0c-83e0-be6f-d62b-dac00ce9b761@gmail.com>
On Mon, Mar 27, 2023 at 03:20:06PM +0300, Matti Vaittinen wrote:
> On 3/27/23 15:01, Greg Kroah-Hartman wrote:
> > On Mon, Mar 27, 2023 at 02:34:02PM +0300, Matti Vaittinen wrote:
> > > A few tests need to have a valid struct device. One such example is
> > > tests which want to be testing devm-managed interfaces.
> > >
> > > Add kunit wrapper for root_device_[un]register(), which create a root
> > > device and also add a kunit managed clean-up routine for the device
> > > destruction upon test exit.
> >
> > I really do not like this as a "root device" is a horrible hack and
> > should only be used if you have to hang other devices off of it and you
> > don't have a real device to tie those devices to.
> >
> > Here you are abusing it and attempting to treat it as a real device,
> > which it is not at all, because:
> >
> > > Special note: In some cases the device reference-count does not reach
> > > zero and devm-unwinding is not done if device is not sitting on a bus.
> > > The root_device_[un]register() are dealing with such devices and thus
> > > this interface may not be usable by all in its current form. More
> > > information can be found from:
> > > https://lore.kernel.org/dri-devel/20221117165311.vovrc7usy4efiytl@houat/
> >
> > See, not a real device, doesn't follow normal "struct device" rules and
> > lifetimes, don't try to use it for a test as it will only cause problems
> > and you will be forced to work around that in a test.
>
> Ok. I understood using the root-device has been a work-around in some other
> tests. Thus continuing use it for tests where we don't need the bus until we
> have a proper alternative was suggested by David.
>
> > Do the right thing here, create a fake bus and add devices to it.
> >
> > Heck, I'll even write that code if you want it, what's the requirement,
> > something like:
> > struct device *kunit_device_create(struct kunit *test, const char *name);
> > void kunit_device_destroy(struct device *dev);
>
> Thanks for the offer Greg. This, however, is being already worked on by
> David. I don't want to step on his toes by writing the same thing, nor do I
> think I should be pushing him to rush on his work.
Ok, David, my offer stands, if you want me to write this I will be glad
to do so.
thanks,
greg k-h
next prev parent reply other threads:[~2023-03-27 12:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 11:27 [PATCH v6 0/7] Support ROHM BU27034 ALS sensor Matti Vaittinen
2023-03-27 11:27 ` [PATCH v6 1/7] dt-bindings: iio: light: Support ROHM BU27034 Matti Vaittinen
2023-03-27 11:28 ` [PATCH v6 2/7] iio: light: Add gain-time-scale helpers Matti Vaittinen
2023-03-30 16:48 ` Matti Vaittinen
2023-03-31 7:39 ` Matti Vaittinen
2023-03-27 11:34 ` [PATCH v6 3/7] kunit: Add kunit wrappers for (root) device creation Matti Vaittinen
2023-03-27 12:01 ` Greg Kroah-Hartman
2023-03-27 12:20 ` Matti Vaittinen
2023-03-27 12:38 ` Greg Kroah-Hartman [this message]
2023-03-28 12:45 ` David Gow
2023-03-28 13:22 ` Matti Vaittinen
2023-03-28 13:38 ` David Gow
2023-03-30 16:53 ` Maxime Ripard
2023-03-27 11:34 ` [PATCH v6 4/7] iio: test: test gain-time-scale helpers Matti Vaittinen
2023-03-27 11:34 ` [PATCH v6 5/7] MAINTAINERS: Add IIO " Matti Vaittinen
2023-03-27 11:34 ` [PATCH v6 6/7] iio: light: ROHM BU27034 Ambient Light Sensor Matti Vaittinen
2023-03-28 5:59 ` kernel test robot
2023-03-30 16:59 ` Matti Vaittinen
2023-03-27 11:35 ` [PATCH v6 7/7] MAINTAINERS: Add ROHM BU27034 Matti Vaittinen
2023-03-27 11:39 ` [PATCH v6 0/7] Support ROHM BU27034 ALS sensor Matti Vaittinen
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=ZCGONl0mC8oyBj-0@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=brendan.higgins@linux.dev \
--cc=davidgow@google.com \
--cc=jic23@kernel.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=sboyd@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