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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS 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 092DBC64E7A for ; Tue, 1 Dec 2020 12:42:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A232C20757 for ; Tue, 1 Dec 2020 12:42:18 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="EqRY9/Tr" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728721AbgLAMmD (ORCPT ); Tue, 1 Dec 2020 07:42:03 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57556 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727055AbgLAMmC (ORCPT ); Tue, 1 Dec 2020 07:42:02 -0500 Received: from mail-lf1-x142.google.com (mail-lf1-x142.google.com [IPv6:2a00:1450:4864:20::142]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 20620C0613CF for ; Tue, 1 Dec 2020 04:41:21 -0800 (PST) Received: by mail-lf1-x142.google.com with SMTP id v14so3864165lfo.3 for ; Tue, 01 Dec 2020 04:41:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LjDKiVUvuKMaRcRGWQSpUGV0bwVQVIskn2Kbrs7Awbs=; b=EqRY9/TrPSbVxfgh6ruxnu8otDhN3brcU/g32do7o1ip4FbR+r5iJDyBT3FqHV98qp +KTHYwAgiUCdnT2RfgfyE43Hpzf4JGaXWwrftuCp4m5LVGiK9WjlzMUJBy4Y8p1CDkm7 +zlM0Yjy5xDhts1zy6dQmQyBrKZ7eKDGiwqjxQwxqYMKQsnPQQtmAkHQyYJKFfqWiFyZ 9fBQTt/htHP/0GZ1iAS+ZBTTmOaVyENLJCtEhij5QIjjvSdMUBIuiWXbHTeQ4VNFVmkr w9zAluEZUqNvDVKtNi5vOgKB5+nNhY7B/UqK4KfZ0XxJg44irsH8thThAXF2G3dgnL3s JtDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LjDKiVUvuKMaRcRGWQSpUGV0bwVQVIskn2Kbrs7Awbs=; b=HU5rCPr1BFphASm8MIgP99m9cBbc9xTHJir3pAxj1usC2BsjbjSMWLAoHgBlpltl4T 3lz3nIqFvDZ0wDR+MOWbytpKmVCnlz2IqyqPK3/cPs1gBUZwdjnHJ4zmHcfQki14+N+Q 3YVDqhK58vSd349shqLC9ByxO1g1rib2UiH1aTGJTjjv6BiF1wS01jep2ynu0nCLgHlU HhyEFsK+rtYX5ycB6CGVI95vlZ2Y/vOTiq2CSuiX5m9pg7ms1G8byiC18Kiv4nyTyzpW K/RpsCgw17JxkoblqS4PdJXkziWoLC9kHhpcVX+xhErfzYFUK1trHznXEqY6IWHv4gp8 YsRQ== X-Gm-Message-State: AOAM531AxbYyN688pc0tLZ7M0+3ITxUulCPuasfjTjpp7qEAhzWY+Ype gmmUf7isd7TiAhRJZloTQOuUb2k0H0B1ObMD1ALg8A== X-Google-Smtp-Source: ABdhPJwfHfzDHFP7FoqfTIm91ADs8s/coo8BjsBLPxRNeM88hjwGheLU0HhCxHMWUQTaRQTnNwhXpz/yN/5SSGvGOd0= X-Received: by 2002:a19:ca05:: with SMTP id a5mr1153633lfg.571.1606826479594; Tue, 01 Dec 2020 04:41:19 -0800 (PST) MIME-Version: 1.0 References: <20201130125915.1315667-1-linus.walleij@linaro.org> <20201130125915.1315667-2-linus.walleij@linaro.org> <20201130210752.5028588c@archlinux> In-Reply-To: <20201130210752.5028588c@archlinux> From: Linus Walleij Date: Tue, 1 Dec 2020 13:41:08 +0100 Message-ID: Subject: Re: [PATCH 2/2] iio: gyro: mpu3050: Store timestamp in poll function To: Jonathan Cameron Cc: linux-iio , Hartmut Knaack , Lars-Peter Clausen , Peter Meerwald-Stadler Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-iio@vger.kernel.org On Mon, Nov 30, 2020 at 10:07 PM Jonathan Cameron wrote: > I'm a bit confused here. Rightly so! > pollfuncs are per device using the trigger, so writing to the > timestamp of the one from this device, won't have an affect on > any others. > > If it did, we'd still have an issue as there are no ordering > guarantees amongst different consumers of a trigger. Yeah I got it all wrong. I'm trying to find the real bug (likely in the trigger consuming driver) and fix that instead. What do you use when stress testing IIO stuff? I have been using the tools from the kernel so mainly lsiio, iio_generic_buffer and iio_event_monitor so far. iio-sensor-proxy seems really nice, but I just haven't figured out what kind of programs people are in turn using that with.. Yours, Linus Walleij