From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793353916; b=aasLUwuPCrvw6WtkjMx7V5VDdU49NfrIntXhe1F/3fISLh4LrRXX1erPBi0owzZ9cuXI b9nqdv0a6L4xHNlGIoO3TSvJZH+X3y98QGz8nb3yF5u6352SPEfi47KxpMX/UT8oSZQcn r7PUa7feJ9EKL8YAQuqkJ5L6ljQQHHJ8K3HcC0ZjKftCXzvkwJwmeO4j8fcuz6okcWmk9 hHJmdRI5/4k331TFJDxY2sfQ263GkJC6Or5btfnZpz12swiM8muS5W6Duq7CINlR++mPL LCDHJrn5hgqmnZ3raJF+n1IaBZkPNWXHEtzEO5cRh3v2QnauV1ah4FShtzK183rz62Q== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793353916; h=Received:DKIM-Signature:Date:From:To:Cc:Subject:Message-ID: References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To; bh=Z/Vftd2TiLfBJONWG7tKtuadXYdLcG6KGxDi2+5TrPk=; b=EQ3OdwyUXlA65RFd4CJQSC64RvkP5URRiByxGgPQGeIgKdMQkII7wBbpTk0Szg4NGwjz 2ii3CKkcosqgETlo6g1KwmGGRaEh5VjRkUsX7lLWmR4U0VQ7oHvIhpzYh8NqDIQnQCoZj 0hBGudp3QNTlXGjUJUk9xHsYykfi0ptP2BBVMx16bwQTobnPlAzV7ney9mSlHnjVxU3jN STH6FrkWyqNXsi3GiL44iG+meOrUNxpbcLk2Xrr+r8g5mFfO0KhkOUGb6K60YPzM6MMrc fWdRhBimG9KiAZYY74WIFUz2+5bIZVcERhS1QKUYxCZHtGuSbSAaZ6zTmIOWmkOQKHg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=hByeplNB; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4DB58606A32C; Fri, 30 Oct 2026 09:51:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=hByeplNB Received: by smtp.kernel.org (Postfix) with ESMTPSA id 517981F00A16; Fri, 30 Oct 2026 09:51:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1793353915; bh=Z/Vftd2TiLfBJONWG7tKtuadXYdLcG6KGxDi2+5TrPk=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=hByeplNB2F+8/YYQPC2JpRUhzOe3vf3faSzOSkxSDHcYED9UZz5sLO2agt5UT0Rmb cLMwNB5IAV4N0s4b7zia5r32tdbNM2PJRYXk3wzFNnipbGyco3Te/DWXs7xM8a5Llq eeoFdBdqAiXTMc1uHBPJLSCtxVBjivongrzbGTvUICj6nFLmG9x9Dpeo3sljyZOcNO Ds1q16TBuctLaCSTFL04I9pXDnHPWI18yMie7ejJ+HBP/U4AoKs3Y9SHXNJP1pB4bd WwKjV0duBOSqKJTT4Bx7S2RTppemzti24ZYGWoQTwNGr41ekqMpRQFUQWU7hdjnm8O ssxNDGal6BOoQ== Date: Fri, 30 Oct 2026 10:51:51 +0100 From: Maxime Ripard To: Svyatoslav Ryhel Cc: Neil Armstrong , Jessica Zhang , David Airlie , Simona Vetter , Maarten Lankhorst , Thomas Zimmermann , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Thierry Reding , Jonathan Hunter , Mikko Perttunen , dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org Subject: Re: [PATCH v5 01/11] drm: Add MIPI DBI bus support Message-ID: References: <20261029152909.234584-1-clamor95@gmail.com> <20261029152909.234584-2-clamor95@gmail.com> X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha384; protocol="application/pgp-signature"; boundary="6rse7oyeg5jl7wfl" Content-Disposition: inline In-Reply-To: --6rse7oyeg5jl7wfl Content-Type: text/plain; protected-headers=v1; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: Re: [PATCH v5 01/11] drm: Add MIPI DBI bus support MIME-Version: 1.0 On Fri, Oct 30, 2026 at 11:42:12AM +0200, Svyatoslav Ryhel wrote: > =D0=BF=D1=82, 30 =D0=B6=D0=BE=D0=B2=D1=82. 2026=E2=80=AF=D1=80. =D0=BE 11= :29 Maxime Ripard =D0=BF=D0=B8=D1=88=D0=B5: > > > > On Thu, Oct 29, 2026 at 05:28:59PM +0200, Svyatoslav Ryhel wrote: > > > From: Mikko Perttunen > > > > > > The MIPI DBI bus allows modeling DBI hosts and peripherals using the = Linux > > > driver model. DBI hosts are registered by their respective drivers. D= uring > > > registration, DBI peripherals are created from the device tree nodes > > > provided by the host. > > > > > > DBI hosts expose operations that can be used by peripheral drivers to > > > access associated devices. > > > > > > The original code was authored by Mikko Perttunen; I have aligned it = with > > > the existing MIPI DSI implementation. > > > > > > Co-developed-by: Svyatoslav Ryhel > > > Signed-off-by: Svyatoslav Ryhel > > > > The SoB situation isn't right here. The author is allegedly Mikko > > Perttunen, but you don't have their SoB, and yours isn't there either. > > This is up to Mikko to decide what to do. Not only, no. When you're sending a patch you must add yours too. > > Aside from that, which MIPI-DBI type is this supposed to support, and > > how do you intend to support Type C panels we already support through > > SPI? > > >=20 > MIPI-DBI Type A and B, which have NO support right now. Then you need to make it much clearer... everywhere :) Maxime --6rse7oyeg5jl7wfl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iJUEABMJAB0WIQTkHFbLp4ejekA/qfgnX84Zoj2+dgUCauRotwAKCRAnX84Zoj2+ dnWQAX4w8DU5UTbOSr0wJY5a5uRY5k5ksHOA2v27eRbtX+hNTHYRLlbwgNBIxoCt gaz50U4BfjZFhg2AvQTHY02f+SDwsBFWZm/VA3Se1+aCU+LSX+Rvp/OreKHRL4JY sYSGWF+RHw== =47Ew -----END PGP SIGNATURE----- --6rse7oyeg5jl7wfl--