public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cristian Marussi <cristian.marussi@arm.com>
To: Jyoti Bhayana <jbhayana@google.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Rob Herring <robh@kernel.org>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	Sudeep Holla <sudeep.holla@arm.com>,
	Enrico Granata <egranata@google.com>,
	Mikhail Golubev <mikhail.golubev@opensynergy.com>,
	Igor Skalkin <Igor.Skalkin@opensynergy.com>,
	Peter Hilber <Peter.hilber@opensynergy.com>,
	Ankit Arora <ankitarora@google.com>,
	Guru Nagarajan <gurunagarajan@google.com>,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v7 1/1] iio/scmi: Adding support for IIO SCMI Based Sensors
Date: Tue, 16 Mar 2021 13:13:28 +0000	[thread overview]
Message-ID: <20210316131314.GI30179@e120937-lin> (raw)
In-Reply-To: <CA+=V6c341JjXQ+QFpiSES_Lm7PT0qCh2WU0uQWrmrFaPr_2QiA@mail.gmail.com>

Hi

I reposted my series on top of the take3 immutable branch from Jonathan
at:

https://lore.kernel.org/lkml/20210316124903.35011-1-cristian.marussi@arm.com/T/#t

You should have received an email regarding the relevant IIO SCMI patch

v7-0025-iio-scmi-port-driver-to-the-new-scmi_sensor_proto.patch

which includes the port of your v7 IIO SCMI driver to the new API, and moved
also the notification registration to the probe phase to simplify it
further.

On my side I tested with some fake emulated sensors emitting periodic
100ms SENSOR_UPDATE notifs...and verifying that notifications are still
dispatched and received fine. (values are just fakes)

If you can have a look, comment and possibly Ack.

Thanks

Cristian

---

(debian-arm64)root@debarm64:~# /root/iio_generic_buffer -a -c -1 -g -l 100 -N 0
iio device number being used is 0
trigger-less mode selected
Enabling all channels
Enabling: in_accel_x_en
Enabling: in_accel_z_en
Enabling: in_timestamp_en
Enabling: in_accel_y_en
-9465 -9457 -9449 6169807244683640832.000000
-9464 -9456 -9448 6169807244683640832.000000
-9463 -9455 -9447 6169807244683640832.000000
-9462 -9454 -9446 6169807244683640832.000000
-9461 -9453 -9445 6169807244683640832.000000
-9460 -9452 -9444 6169807244683640832.000000
-9459 -9451 -9443 7169807022831960064.000000
-9458 -9450 -9442 7169807022831960064.000000
-9457 -9449 -9441 7169807022831960064.000000
-9456 -9448 -9440 7169807022831960064.000000
-9455 -9447 -9439 7169807022831960064.000000
-9454 -9446 -9438 7169807022831960064.000000
-9453 -9445 -9437 7169807022831960064.000000
-9452 -9444 -9436 7169807022831960064.000000
-9451 -9443 -9435 7169807022831960064.000000
-9450 -9442 -9434 7169807022831960064.000000
-9449 -9441 -9433 8169806800980279296.000000
-9448 -9440 -9432 8169806800980279296.000000
-9447 -9439 -9431 8169806800980279296.000000
-9446 -9438 -9430 8169806800980279296.000000
-9445 -9437 -9429 8169806800980279296.000000
-9444 -9436 -9428 8169806800980279296.000000
-9443 -9435 -9427 8169806800980279296.000000
-9442 -9434 -9426 8169806800980279296.000000
-9441 -9433 -9425 8169806800980279296.000000
-9440 -9432 -9424 8169806800980279296.000000
-9439 -9431 -9423 9169807128884412416.000000
-9438 -9430 -9422 9169807128884412416.000000
-9437 -9429 -9421 9169807128884412416.000000
-9436 -9428 -9420 9169807128884412416.000000
-9435 -9427 -9419 9169807128884412416.000000
^CCaught signal 2
Disabling: in_accel_x_en
Disabling: in_accel_z_en
Disabling: in_timestamp_en
Disabling: in_accel_y_en


On Sun, Mar 14, 2021 at 11:47:25AM -0700, Jyoti Bhayana wrote:
> Hi Jonathan,
> 
> No worries. Thanks for the update. It looks good now.
> 
> Thanks,
> Jyoti
> 
> On Sun, Mar 14, 2021 at 8:40 AM Jonathan Cameron <jic23@kernel.org> wrote:
> >
> > On Sat, 13 Mar 2021 11:55:39 -0800
> > Jyoti Bhayana <jbhayana@google.com> wrote:
> >
> > > Hi Jonathan,
> > >
> > > I still see the old version 6 in ib-iio-scmi-5.12-rc2-take2 as well.
> >
> > OK. I'm completely confused as to what is going with my local tree.
> > I have the right patch in the history but it didn't end up in the final
> > pushed out version.  Fat finger mess-up I guess and too many similarly named
> > branches and the fact I didn't check the final result closely enough.
> >
> > There is now an ib-iio-scmi-5.12-rc2-take3 branch
> >
> > This time it definitely has your patch from the 9th of March with no
> > instances of long long in it.
> >
> > Sorry I messed this one up (again!)
> >
> > Jonathan
> >
> > >
> > > Thanks,
> > > Jyoti
> >

  reply	other threads:[~2021-03-16 13:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 23:12 [PATCH v7 0/1] Adding support for IIO SCMI based sensors Jyoti Bhayana
2021-03-09 23:12 ` [PATCH v7 1/1] iio/scmi: Adding support for IIO SCMI Based Sensors Jyoti Bhayana
2021-03-10 11:15   ` Peter Hilber
2021-03-10 17:19     ` Jyoti Bhayana
2021-03-11  9:55       ` Peter Hilber
2021-03-11 21:08   ` Jonathan Cameron
2021-03-12 12:16     ` Jonathan Cameron
2021-03-12 13:31       ` Cristian Marussi
2021-03-12 17:54         ` Jyoti Bhayana
2021-03-13 17:11           ` Jonathan Cameron
2021-03-13 19:55             ` Jyoti Bhayana
2021-03-14 15:40               ` Jonathan Cameron
2021-03-14 18:47                 ` Jyoti Bhayana
2021-03-16 13:13                   ` Cristian Marussi [this message]
2021-03-16 17:53                     ` Jyoti Bhayana
2021-03-15 13:41                 ` Sudeep Holla

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=20210316131314.GI30179@e120937-lin \
    --to=cristian.marussi@arm.com \
    --cc=Igor.Skalkin@opensynergy.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=Peter.hilber@opensynergy.com \
    --cc=ankitarora@google.com \
    --cc=davem@davemloft.net \
    --cc=egranata@google.com \
    --cc=gurunagarajan@google.com \
    --cc=jbhayana@google.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lukas.bulwahn@gmail.com \
    --cc=mchehab+huawei@kernel.org \
    --cc=mikhail.golubev@opensynergy.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh@kernel.org \
    --cc=sudeep.holla@arm.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