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=-3.8 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,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 1A10DC433E6 for ; Thu, 11 Mar 2021 08:19:17 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 4C02164F92 for ; Thu, 11 Mar 2021 08:19:16 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4C02164F92 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4Dx20f1wpNz3d6b for ; Thu, 11 Mar 2021 19:19:14 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=FhylOKgC; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=kernel.org (client-ip=198.145.29.99; helo=mail.kernel.org; envelope-from=wsa@kernel.org; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=FhylOKgC; dkim-atps=neutral Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4Dx20C2vPFz3cHH for ; Thu, 11 Mar 2021 19:18:51 +1100 (AEDT) Received: by mail.kernel.org (Postfix) with ESMTPSA id 9896B61554; Thu, 11 Mar 2021 08:18:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1615450728; bh=pcPYx32koDPoQYOnqgHXzh5B1hR+EWUWAY4YkutCz7A=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=FhylOKgCVND8Y9Y2qTErMZIg9mJ00+UGrQGUmieOjOSW5LUWaOGH3h7pggBgVtPM6 qaWJLoyx9SyhQSOm2amdTZTMFZZJ5NCzmS6kOlMQ/QvdEJITkfJpv79fBqd68P9Stb PU12e9hpkKqsSTxjvUi9D71ycfDUZi5XpohwQopGd7U4w+TwGuuzoKeeTXRH/LSQ4M 7sm3ZXipdFxylhKPtQSkpbebDumT0kKCyn5DFRyxtMOjWHZD0ZkGHHUzJDDXljSaGN k1gpUo7jMM0qcYLnnCeRrgSOurn9a1NSfEFeEGQL6UqoXcH3WTEGMehDt96Bljow5D 15PMBuTs/E1gw== Date: Thu, 11 Mar 2021 09:18:42 +0100 From: Wolfram Sang To: Guenter Roeck Subject: Re: Errant readings on LM81 with T2080 SoC Message-ID: <20210311081842.GA1070@ninjato> References: <8e0a88ba-01e9-9bc1-c78b-20f26ce27d12@alliedtelesis.co.nz> <96d660bc-17ab-4e0e-9a94-bce1737a8da1@roeck-us.net> <4a1b1494-df96-2d8c-9323-beb2c2ba706b@alliedtelesis.co.nz> <5709f180-04b5-09b2-e1c4-53eb5c9345d8@roeck-us.net> <1aa0dc23-0706-5902-2f46-0767de0e3ad6@alliedtelesis.co.nz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH" Content-Disposition: inline In-Reply-To: X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "linux-hwmon@vger.kernel.org" , "jdelvare@suse.com" , "linux-kernel@vger.kernel.org" , Chris Packham , "linux-i2c@vger.kernel.org" , "linuxppc-dev@lists.ozlabs.org" Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" --7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Bummer. What is really weird is that you see clock stretching under > CPU load. Normally clock stretching is triggered by the device, not > by the host. One example: Some hosts need an interrupt per byte to know if they should send ACK or NACK. If that interrupt is delayed, they stretch the clock. --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEOZGx6rniZ1Gk92RdFA3kzBSgKbYFAmBJ0l4ACgkQFA3kzBSg Kbbb/w/8DLizM94FZ2EJrsVVPXMLUIQDEIGL3ujBX2GyAsv6HeYmKAJzuE4QhMyE kE+xExT0T62C8UpKJ5ZHpRYzWXLgiJEucIOS2qlLEjn29rhI+u6bTd3LfPe/YpyB qMDuUzwLg4KiOPbiyX856rvJ5KOG/EN2owyWxZPXgKuKqqSUe+ewXIaZzu8l9Z8D qzvSjMhvWdisp976ZCj6ZK1U8j2iHtbijGiOIdmCvtH3TaLid1Tie/BheiwdQMPo 2yDRYK4XkZDwcd8E0qRDN3Ew8Vv71hQH+uSiW5/cGxWSvXO3j16OuQH9TObSI+KI WAdnpcTyudvinJAnw5xBhm3Jmc/dbTDh0KYFHrPJS09qBg62D2zRKlG0IeFA/p3v VWmVk6cklvAemFo0iBejL/O9at2ItOZ+M6n3M4zVsuxGM88roenQQ9S74QxXgBKj roGq1udYl7LJUxDDswBwGyGTsHWcMfjDTVgimEYlvxlPkjJbg7qv0iHnLCl7hi2G MZMl28mpaWEmkQMAsiQygwezbEgTYGmV1xU7lVxeqDq3ypI51bsInMP3yc3LPalz wA8Grj0ZQloVpPWyZHu5sAVIKvEafk3NsDvfNj1rOLh/XBsGQRGv8qRuqqjQfecw YHTA/PJJ3Wn+i31hH9bqVkRVjgyq6iCeEP4STaAu3dCHKQFaXfs= =FkGx -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH--