From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6DAB7C3A5A2 for ; Tue, 10 Sep 2019 07:17:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 448E22171F for ; Tue, 10 Sep 2019 07:17:32 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=geanix.com header.i=@geanix.com header.b="GN1CczuU" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727113AbfIJHR1 (ORCPT ); Tue, 10 Sep 2019 03:17:27 -0400 Received: from first.geanix.com ([116.203.34.67]:60688 "EHLO first.geanix.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726429AbfIJHR1 (ORCPT ); Tue, 10 Sep 2019 03:17:27 -0400 Received: from [192.168.100.95] (unknown [95.138.208.137]) by first.geanix.com (Postfix) with ESMTPSA id DC33063F8C; Tue, 10 Sep 2019 07:16:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=geanix.com; s=first; t=1568099814; bh=aUmlGRD7s/8YP4O7hbJ34i47eXPMIc8IMEp8E2Y/9Rw=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=GN1CczuUe3c7Lb1qMTigsxCLypTCYoaJEMjQUieibQ0K3vhTdK9Nf+SQfy6MJpdtE IA6WDuQSJ6mAXAaC9+bxlwPYJ0tU2Q59OoTVh+ADc9I0z+V8GHHgcykFz3GcRuVqc2 UOayLA6upanOhSrIflCfMdT2vSJYWVlgQDJSBe/syw7QfmR9HXbxMctPb4OmFCphjE +fxZ1zohNr7pspRO+eijsxKnoTvs5CDNphzgfLhN+ptMjGNp61rKjbDfv7inn+dbJn WTmNNsQmKCozy6J0dx/UeZh3+hX6OSvBnd6DsqtDtQL2mCBnjbn9QKN28uXtGY+j9z og9FN3TaeOhTg== Subject: Re: [PATCH v6 5/6] iio: imu: st_lsm6dsx: add motion report function and call from interrupt To: Lorenzo Bianconi Cc: linux-iio@vger.kernel.org, jic23@kernel.org, lorenzo.bianconi83@gmail.com, denis.ciocca@st.com, mario.tesi@st.com, armando.visconti@st.com, martin@geanix.com References: <20190909112846.55280-1-sean@geanix.com> <20190909112846.55280-5-sean@geanix.com> <20190909120546.GE2990@localhost.localdomain> <6e987a54-250c-c146-cff8-99fa33255f9b@geanix.com> <20190910071250.GA2712@localhost.localdomain> From: Sean Nyekjaer Message-ID: <58121fe6-067f-4515-3375-735ca7b41df6@geanix.com> Date: Tue, 10 Sep 2019 09:17:01 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.0 MIME-Version: 1.0 In-Reply-To: <20190910071250.GA2712@localhost.localdomain> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US-large Content-Transfer-Encoding: 7bit Sender: linux-iio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-iio@vger.kernel.org On 10/09/2019 09.12, Lorenzo Bianconi wrote: > probably a silly question..are you tracing the interrupt line with an > oscilloscope or a logical analyser? If you dump interrupt counters in > /proc/interrupts will you see an interrupt storm for the selected irq > pin? > Not a silly question ;-) An Oscilloscope :-) The interrupt counter is stopping. If I switch to IRQ_TYPE_LEVEL_HIGH, (to test if additional readings of the event and FIFO registers would help. It results in interrupt storm and the line continues to stay high. /Sean