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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0F2D8C433F5 for ; Wed, 20 Apr 2022 12:54:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1353740AbiDTM5b (ORCPT ); Wed, 20 Apr 2022 08:57:31 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34716 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233931AbiDTM5a (ORCPT ); Wed, 20 Apr 2022 08:57:30 -0400 Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8D44C3CA4A; Wed, 20 Apr 2022 05:54:44 -0700 (PDT) Received: by mail-pl1-x636.google.com with SMTP id j8so1675847pll.11; Wed, 20 Apr 2022 05:54:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=cfKEQXfvPhG1kZ+YpMF2hReHRJMEZQRtVI8gWHNwJsE=; b=SJ9wrEqPvYtvq6u4My/rceS5j/aS5O0TKpsoPpclCoMwLTUcTsXrjY6k58GgXgJDjk tz01T2qFPAHZcwZXJgAwa/uoXApT+ETBGfmmTjkYZ9d86v15pp2JSMJBlS0X/emLIUnL FfaBsG1olGj+ebvEzoG/tMRz6g3iydpNPuDMUWlcJE2yd+4v/SWBiXyLES6jNIDlHD5l 61Z4eLrfFF8CDN43J7Tz5JjM0Q/1AYgpPCyv7abRl+quV72pVPxZxKv/x7sKMu9XzVL5 SWOxNuWj84mkapk9TS6KdbIbwNAjO5B36W7ddQDXFwsqyW2fnMzNSfySVXaXW0AshHBv GGKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=cfKEQXfvPhG1kZ+YpMF2hReHRJMEZQRtVI8gWHNwJsE=; b=CB5waa/HRh+d+PEZOBTarWNAVVd+jutVltwYQ/syYhdP1ahzJWS/Yd8CWc+0tUpxhi apIuHL8TT8wve1bT/bQjlAN2XCg0KdIDZzKJ3b7TtP33fw/Lde5/5brBMtjwrdbT92hk 3n4UMQLzZo4aUGAVHMenPiiuti9HPFYUgeTjtW2Mvl+ees1w1yO0d0iqUEuGv0GWxCcf CU80fc0OiuB2mmHy8c0O+vTJAWPHC7m9eXQAmy2NExidbshT2sarWbEPNQd8FM4RTv06 HaLDcReYldCvm1DoFrUtnQUDpgB9LJ8ghUfoUkAI7da0TIjNSNc/6F1Glv3CYhfdzxqv cC5Q== X-Gm-Message-State: AOAM531KbE7+se02YKxJhGhBusIC+x85chjBTsCWwUEW9r68AfMo2BUu ZTByFwxa1wn/BekMuy9rH/w= X-Google-Smtp-Source: ABdhPJyBl7o+zKhHc4HtlQRcXGENqCIJ11onw+S/lwrewiHQtnsX2ruF+ZGjWz971D6YhQis7geogw== X-Received: by 2002:a17:90b:4f42:b0:1d2:d1fa:4df5 with SMTP id pj2-20020a17090b4f4200b001d2d1fa4df5mr4297398pjb.81.1650459284069; Wed, 20 Apr 2022 05:54:44 -0700 (PDT) Received: from hoboy.vegasvil.org ([2601:640:8200:33:e2d5:5eff:fea5:802f]) by smtp.gmail.com with ESMTPSA id o22-20020a17090a9f9600b001d0d20fd674sm15955961pjp.40.2022.04.20.05.54.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Apr 2022 05:54:42 -0700 (PDT) Date: Wed, 20 Apr 2022 05:54:39 -0700 From: Richard Cochran To: Tan Tee Min Cc: Jakub Kicinski , Tan Tee Min , Giuseppe Cavallaro , Alexandre Torgue , Jose Abreu , "David S . Miller" , Paolo Abeni , Maxime Coquelin , Rayagond Kokatanur , netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, Voon Wei Feng , Wong Vee Khee , Song Yoong Siang , Alexandre Torgue Subject: Re: [PATCH net 1/1] net: stmmac: add fsleep() in HW Rx timestamp checking loop Message-ID: <20220420125439.GA1401@hoboy.vegasvil.org> References: <20220413040115.2351987-1-tee.min.tan@intel.com> <20220413125915.GA667752@hoboy.vegasvil.org> <20220414072934.GA10025@linux.intel.com> <20220414104259.0b928249@kernel.org> <20220419005220.GA17634@linux.intel.com> <20220419132853.GA19386@hoboy.vegasvil.org> <20220420051508.GA18173@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220420051508.GA18173@linux.intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Wed, Apr 20, 2022 at 01:15:08PM +0800, Tan Tee Min wrote: > No. The context descriptor (frame) is possibly still owned by the > DMA controller in this situation. So that is a problem. The solution is to postpone this logic until the driver owns the buffer. Doesn't the HW offer some means of notification, like an interrupt for example? Thanks, Richard