From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Okba Slatnia <okbaslatnia@gmail.com>, linux-iio@vger.kernel.org
Subject: Re: st_lsm6dsx minor issue
Date: Sun, 18 Aug 2024 09:50:28 +0200 [thread overview]
Message-ID: <ZsGnxBpYxihXxtC5@lore-rh-laptop> (raw)
In-Reply-To: <20240817174630.1c24bb02@jic23-huawei>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
> On Thu, 8 Aug 2024 15:27:33 +0200
> Okba Slatnia <okbaslatnia@gmail.com> wrote:
>
> > Hi all,
Hi Okba,
> >
> > I'm building a yocto firmware based on Linux kernel version 5.15.148
> > and i'm facing a little limitation or problem preventing me from
> > changing the value of the sampling_frequency of the accelerator:
> > /sys/bus/iio/devices/iio:device0/sampling_frequency
> > despite i'm following the
> > /sys/bus/iio/devices/iio:device0/sampling_frequenc_available for the
> > possible values.
> > for the info , i can successfully change the sampling_frequency on
> > another yocto firmware based on Linux kernel version 4.19 and despite
> > keeping the same kernel flags confs i'm still facing this issue , i
> > made sure it's not an access right issue because i can change other
> > files in the same path with same access rights.
Can you please provide more details about the issue? Are you able to change
gyro sample frequency? Is the sensor-hub enabled?
Regards,
Lorenzo
> >
> > Can you please help me and tell me if I missed anything ?
> > Thanks in advance.
> > Best Regards.
> > --
> > Okba
>
> +CC Lorenzo on basis maybe he's seen this before?
>
> Jonathan
>
> >
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-08-18 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 13:27 st_lsm6dsx minor issue Okba Slatnia
2024-08-17 16:46 ` Jonathan Cameron
2024-08-18 7:50 ` Lorenzo Bianconi [this message]
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=ZsGnxBpYxihXxtC5@lore-rh-laptop \
--to=lorenzo@kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=okbaslatnia@gmail.com \
/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