Received: by 2002:a05:6a10:1d13:0:0:0:0 with SMTP id pp19csp521695pxb; Wed, 25 Aug 2021 08:35:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzGa7jFEhyrRZoCj4PC1Hq3WfILREUl5FXZb0dDwPz7pURlDV+ju59dBDMuk9JUgq+U74ho X-Received: by 2002:a6b:f919:: with SMTP id j25mr37303932iog.2.1629905749915; Wed, 25 Aug 2021 08:35:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1629905749; cv=none; d=google.com; s=arc-20160816; b=SZjPk/+r5HS0YAamm2chpaz5DJ7fEJ8lTxFaBhrRWxKx3SoypsO1MF1n+SfZaRi1QW MemGebiEKCXeWbqMuzuDuVM1AUJk55vdY30qtHo38YofEUJrxXLHJxVNwTv6m9Ftvp3C H/G65X+/i2SOlMFg6GT+GfoQLIf88Ihkud+UqdTqqFj6jA7CMPPCEnXGDm70oiIVB3Rs njJsJoWWT2I5l4q7cEc/rkzuigXKRh7ucwCVkQky39z0mUUcqbtbDX/wxBDolkPsVSb3 Th79kdl1wC3Uayj+ZZ/lkIhTMFafw0kz6M6AHuGjyIaXM6Zk4HtlfvU0eHDWgAL/th1G g60Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=rS4rQhWZ9HtaxhVGr+t8trV+J11x9hnBs7ciFUJAIbs=; b=LNC3GZRTE436gaFgMiEEhV2MIduCvgtM0jrxsQzp3sOEIbohAoG4W/VmqR11okocxU cdIDaosxEhAfYc4ilMwHp/3s+rV8Kji4FBrSQXgVX+Jmw2u6OIUXpsDOlU/K9WOF+em5 Tnttl5iBu6M6+KJ558FF7s+Bad78PTBtUog/iEGkZnOytTz4cThnPwt2fYa5J1I+Ifwi JsFUaLTAU2U6ohTlq0+tPwMTqA3i72Ig2hK6/uocZZaLxlCXQyLV23HxLmhYsIosCosu QY3JDp/hPbV0J9bzFtd2ipmSGphr7zmRrAgtoTnndM4u//bRgIj0LZJYF8f1nbD+8q0R NNgg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b9si95699ion.34.2021.08.25.08.35.38; Wed, 25 Aug 2021 08:35:49 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233573AbhHYPHB (ORCPT + 99 others); Wed, 25 Aug 2021 11:07:01 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:51548 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231995AbhHYPHB (ORCPT ); Wed, 25 Aug 2021 11:07:01 -0400 Received: from maud (unknown [IPv6:2600:8800:8c06:1000::c8f3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: alyssa) by bhuna.collabora.co.uk (Postfix) with ESMTPSA id D41DC1F43B19; Wed, 25 Aug 2021 16:06:04 +0100 (BST) Date: Wed, 25 Aug 2021 11:05:49 -0400 From: Alyssa Rosenzweig To: Steven Price Cc: Alyssa Rosenzweig , dri-devel@lists.freedesktop.org, Rob Herring , Tomeu Vizoso , David Airlie , Daniel Vetter , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 4/4] drm/panfrost: Handle non-aligned lock addresses Message-ID: References: <20210824173028.7528-1-alyssa.rosenzweig@collabora.com> <20210824173028.7528-5-alyssa.rosenzweig@collabora.com> <6fe675c4-d22b-22da-ba3c-f6d33419b9ed@arm.com> <8db73065-e8e8-7894-7eac-befd082a25e1@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8db73065-e8e8-7894-7eac-befd082a25e1@arm.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > Horrifying, and not what I wanted to read my last day before 2 weeks of > > leave. Let's drop this patch, hopefully by the time I'm back, your > > friends in GPU can confirm that's a spec bug and not an actual > > hardware/driver one... > > > > Can you apply the other 3 patches in the mean time? Thanks :-) > > > > Yeah, sure. I'll push the first 3 to drm-misc-next-fixes (should land in > v5.15). > > It's interesting that if my (new) reading of the spec is correct then > kbase has been horribly broken in this respect forever. So clearly it > can't be something that crops up very often. It would have been good if > the spec could have included wording such as "naturally aligned" if > that's what was intended. Indeed. Fingers crossed this is a mix-up. Although the text you quoted seems pretty clear unfortunately :| > Enjoy your holiday! Thanks!