Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Gwendal Grignou <gwendal@chromium.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	linux-iio <linux-iio@vger.kernel.org>,
	Stephen Boyd <swboyd@chromium.org>
Subject: Re: [PATCH v10 3/5] iio: proximity: Add SX9324 support
Date: Sun, 9 Jan 2022 16:41:50 +0000	[thread overview]
Message-ID: <20220109164142.618e6fd4@jic23-huawei> (raw)
In-Reply-To: <CAHp75VdPs6BcA2uka3irNr3mNBY9T-Dtw7J0M=Emm7_RPo+1yw@mail.gmail.com>

On Sun, 9 Jan 2022 14:19:44 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:

> On Sun, Jan 2, 2022 at 6:28 PM Gwendal Grignou <gwendal@chromium.org> wrote:
> >
> > Semtech SAR sensor SX9324 is an evolution of the SX9310:
> > It has 4 phases that can be configure to capture and process data
> > from any of 3 CS pins and provide independent detection:
> > proximity, table proximity or body proximity.
> >
> > Gather antenna data:
> >   echo sx9324-dev3 > trigger/current_trigger
> >   echo 1 > scan_elements/in_proximity0_en
> >   echo 1 > buffer/enable
> >   od -v -An --endian=big -t d2 -w2 /dev/iio\:device3
> >   (at 10Hz, the default).
> >
> > Trigger events:
> > Setting:
> >   thresh_falling_period: 2 (events)
> >   thresh_rising_period: 2 (events)
> >   in_proximity0_thresh_either_value: 300
> >   in_proximity0_thresh_either_hysteresis: 72
> >
> > using iio_event_monitor /dev/iio\:deviceX, approaching my hand to the
> > antenna pad, I see:
> > ...
> > Event: time: 1634763907532035297, type: proximity, channel: 0, evtype:
> > thresh, direction: falling
> > Event: time: 1634763910138104640, type: proximity, channel: 0, evtype:
> > thresh, direction: rising
> > ...
> >
> > Datasheet:
> > https://edit.wpgdadawant.com/uploads/news_file/program/2019/30184/tech_files/program_30184_suggest_other_file.pdf  
> 
> Jonathan, I noticed you have applied this to testing, can you please
> make Datasheet a real tag?
> I.o.w. put it to one line and drop the following blank line.
> 
Sure.  Can roll other fixes in as well until rc1 shows up and I rebase the tree.

I tidied up the other patch naming in here to make it more consistent whilst
I was there.

New tree pushed out.
Thanks,

Jonathan



  reply	other threads:[~2022-01-09 16:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-01 20:38 [PATCH v10 0/5] Expand Semtech SAR Sensors support Gwendal Grignou
2022-01-01 20:38 ` [PATCH v10 1/5] iio: sx9310: Add frequency in read_avail Gwendal Grignou
2022-01-01 20:38 ` [PATCH v10 2/5] iio: sx9310: Extract common Semtech sensor logic Gwendal Grignou
2022-01-01 20:38 ` [PATCH v10 3/5] iio: proximity: Add SX9324 support Gwendal Grignou
2022-01-09 12:19   ` Andy Shevchenko
2022-01-09 16:41     ` Jonathan Cameron [this message]
2022-01-09 12:25   ` Andy Shevchenko
2022-01-09 16:39     ` Jonathan Cameron
2022-01-09 16:47       ` Andy Shevchenko
2022-01-16 17:01         ` Jonathan Cameron
2022-01-01 20:38 ` [PATCH v10 4/5] dt-bindings: iio: Add sx9324 binding Gwendal Grignou
2022-01-01 20:38 ` [PATCH v10 5/5] iio: sx9324: Add dt_binding support Gwendal Grignou
2022-01-09 10:52 ` [PATCH v10 0/5] Expand Semtech SAR Sensors support Jonathan Cameron

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=20220109164142.618e6fd4@jic23-huawei \
    --to=jic23@jic23.retrosnub.co.uk \
    --cc=andy.shevchenko@gmail.com \
    --cc=gwendal@chromium.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=swboyd@chromium.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