From: Vasiliy Doylov <nekodevelopper@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
Vasiliy Doylov via B4 Relay
<devnull+nekodevelopper.gmail.com@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/5] iio: accel: mc3230: add OF match table
Date: Sun, 12 Jan 2025 19:38:51 +0300 [thread overview]
Message-ID: <5210adc6-eb1b-4797-a2f1-0368cc44c392@gmail.com> (raw)
In-Reply-To: <20250112162917.6f0cfa9f@jic23-huawei>
On 1/12/25 7:29 PM, Jonathan Cameron wrote:
> Are you sure that didn't previously work? I thought there were
> fallbacks that would make it use the driver name if nothing else matched.
It works if I modprobe module, but module doesn't loading automatically
on boot like other modules.
With OF match it loads automatically during boot, without i need to call
modprobe explicitly
next prev parent reply other threads:[~2025-01-12 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 12:25 [PATCH v3 0/5] iio: accel: mc3230: add mount matrix, of match and mc3510c support Vasiliy Doylov via B4 Relay
2025-01-12 12:25 ` [PATCH v3 1/5] dt-bindings: iio: accel: mc3230: document mc3510c Vasiliy Doylov via B4 Relay
2025-01-13 8:49 ` Krzysztof Kozlowski
2025-01-12 12:25 ` [PATCH v3 2/5] iio: accel: mc3230: add mount matrix support Vasiliy Doylov via B4 Relay
2025-01-12 16:28 ` Jonathan Cameron
2025-01-12 12:25 ` [PATCH v3 3/5] iio: accel: mc3230: add OF match table Vasiliy Doylov via B4 Relay
2025-01-12 16:29 ` Jonathan Cameron
2025-01-12 16:38 ` Vasiliy Doylov [this message]
2025-01-12 12:25 ` [PATCH v3 4/5] iio: accel: mc3230: add multiple devices support Vasiliy Doylov via B4 Relay
2025-01-12 16:32 ` Jonathan Cameron
2025-01-13 8:51 ` Krzysztof Kozlowski
2025-01-12 12:25 ` [PATCH v3 5/5] iio: accel: mc3230: add mc3510c support Vasiliy Doylov via B4 Relay
2025-01-12 16:34 ` Jonathan Cameron
2025-01-13 8:51 ` Krzysztof Kozlowski
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=5210adc6-eb1b-4797-a2f1-0368cc44c392@gmail.com \
--to=nekodevelopper@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+nekodevelopper.gmail.com@kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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