Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 4 May 2023 10:58:04 +0300
From:   Matti Vaittinen <mazziesaccount@gmail.com>
To:     Matti Vaittinen <mazziesaccount@gmail.com>,
        Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc:     Matti Vaittinen <mazziesaccount@gmail.com>,
        Jonathan Cameron <jic23@kernel.org>,
        Lars-Peter Clausen <lars@metafoo.de>,
        linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH 2/3] iio: bu27008: Probe asynchronously
Message-ID: <7cbc13bb62a0f6919366317991c5f451a0f8aa4e.1683185765.git.mazziesaccount@gmail.com>
References: <cover.1683185765.git.mazziesaccount@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="hrwMi0N3ruh9uJZf"
Content-Disposition: inline
In-Reply-To: <cover.1683185765.git.mazziesaccount@gmail.com>
Precedence: bulk


--hrwMi0N3ruh9uJZf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Devices which may take a while to initialize during probe and which have
no strong reason to probe synchronously can request asynchronous probing
as default probe strategy. This can speed-up start times on some
platforms.

The BU27008 gets probe delayed for at least two reasons. It enables the
supply regulator, (which is likely to have ramp-up delay if it was
disabled) and additionally it delays while the sensor itself is
initializing.

Changing to asynchronous probing may cause problems. Some of which are
discussed in:
https://lore.kernel.org/all/06db017f-e985-4434-8d1d-02ca2100cca0@sirena.org=
=2Euk/

Enabling async probing for the ROHM BU27008 should be fairly safe to try
though as there is no in-tree users for it yet. If the async probing
appears to be an issue we can switch easily back to synchronous (or
better yet, fix the actual problem).

Enable asynchronous probing for BU27008.

Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>

---

I am unsure if this change is 100% safe - but I don't immediately see
the harm. Please let me know if some of you have more experience on
problems when using asynchronous probing with IIO devices.
---
 drivers/iio/light/rohm-bu27008.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/iio/light/rohm-bu27008.c b/drivers/iio/light/rohm-bu27=
008.c
index c04d845062ba..628d17036bb4 100644
--- a/drivers/iio/light/rohm-bu27008.c
+++ b/drivers/iio/light/rohm-bu27008.c
@@ -982,6 +982,7 @@ static struct i2c_driver bu27008_i2c_driver =3D {
 	.driver =3D {
 		.name =3D "bu27008",
 		.of_match_table =3D bu27008_of_match,
+		.probe_type =3D PROBE_PREFER_ASYNCHRONOUS,
 	},
 	.probe_new =3D bu27008_probe,
 };
--=20
2.40.0


--=20
Matti Vaittinen, Linux device drivers
ROHM Semiconductors, Finland SWDC
Kiviharjunlenkki 1E
90220 OULU
FINLAND

~~~ "I don't think so," said Rene Descartes. Just then he vanished ~~~
Simon says - in Latin please.
~~~ "non cogito me" dixit Rene Descarte, deinde evanescavit ~~~
Thanks to Simon Glass for the translation =3D]=20

--hrwMi0N3ruh9uJZf
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEIx+f8wZb28fLKEhTeFA3/03aocUFAmRTZYwACgkQeFA3/03a
ocV01Qf+MNP2ygbXo7I6Vngpe67zSBo3sOt3eOoXjBlae8VvOSGk2y52KNbh64s7
mGrGB0q33y6MQ196jb10ODHBAFKkdtYPtC5gR/OTJtqHyNRfrffcjwndkJk8Ugl3
D5HrkAs/Z9OPvqMwbUT9Ffrazxi56B+dtsHiks9d1gbxmGpRHOKLSJ1m5u8PmBku
62LacMozxQTryj9QTvLeofFQslR+3KBIoXq4TlwY5UX8GunL5eg8FIWAHqIOBZyA
1BTBOQpN6puSYr1cyQsPJ3adPCaBvBVnzxK2TxSdX0HAO5spGbNVBpG1qq4U5uNr
J6pkID5yQ3nqKL5ldyrGkHATdJIMhA==
=8YZz
-----END PGP SIGNATURE-----

--hrwMi0N3ruh9uJZf--