From nobody Fri Nov 29 00:54:10 2024 Received: from out-184.mta1.migadu.com (out-184.mta1.migadu.com [95.215.58.184]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 90C3B166315 for ; Thu, 26 Sep 2024 18:09:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.184 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1727374176; cv=none; b=LYmIGKi55TinTpbQX4yheyBbLXqe1tj82sLVUfwdARULj2YVTRhnJnT3fLGoUpXoPJP85lk9aB7mRo+PjV9//V68m4dYND86PWob49FoP1NhgPhioTs6kFb1C38/q5JLoOc5B5SJ+TNlQEz0tRU9TdOEXJuO0DgGwdu6Dx/ClfU= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1727374176; c=relaxed/simple; bh=vnoXmPj03gY3HeZFlU/P/fiukyHxubnqAyx25jYQ6PE=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=HJf3QiGxg5oWx0jMAAGxCr6sg50xVyraCRf+U2Vus1Fo5mQJipycdKOp/C2K8WJEeWNcYhLnCyEjdn762VHKH1yMNzSv6oSTKpmTYyEI6hqcZuvInI5hHYgny+CYTfXlFd1yg+VP5SlWYgjaDPdUqdIZTprJUCaOTy1jb+VXeA0= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=O9o+YpqO; arc=none smtp.client-ip=95.215.58.184 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="O9o+YpqO" X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1727374171; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Mtm2tEn6+0ysbxRZCa9NK2SpqJBjdy9coOdju9E6VL4=; b=O9o+YpqOYzWoFfC6sMVyedxU6uVvTrnsEW0gevy1l9MYltp8/wE72b2jaFnMsd0tetmp57 fopC0KEdgGMYBecsYa0+adB+rtcmWvGOTWspz+4SPDJY88/tGVx+BpG3Ny7VcvmYccg2IJ FSYo6F9xT8hRXieg0gWZGl4H3DwXk0o= From: Sean Anderson To: Arnd Bergmann , Olof Johansson , linux-arm-kernel@lists.infradead.org Cc: Krzysztof Kozlowski , Rob Herring , linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Conor Dooley , Magnus Damm , Geert Uytterhoeven , Sean Anderson Subject: [PATCH 2/2] arm64: dts: renesas: ulcb: Add SD/OE pin properties Date: Thu, 26 Sep 2024 14:09:03 -0400 Message-Id: <20240926180903.479895-3-sean.anderson@linux.dev> In-Reply-To: <20240926180903.479895-1-sean.anderson@linux.dev> References: <20240926180903.479895-1-sean.anderson@linux.dev> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Migadu-Flow: FLOW_OUT Content-Type: text/plain; charset="utf-8" Add SD/OE pin properties to the devicetree so that Linux can configure the pin without relying on the OTP. This configuration is based on inspection of the schematic (which shows the SD/OE pin permanently tied high). Signed-off-by: Sean Anderson Reviewed-by: Geert Uytterhoeven Tested-by: Geert Uytterhoeven --- arch/arm64/boot/dts/renesas/ulcb.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/boot/dts/renesas/ulcb.dtsi b/arch/arm64/boot/dts/re= nesas/ulcb.dtsi index a2f66f916048..2a2cd788ffec 100644 --- a/arch/arm64/boot/dts/renesas/ulcb.dtsi +++ b/arch/arm64/boot/dts/renesas/ulcb.dtsi @@ -234,6 +234,8 @@ versaclock5: clock-generator@6a { #clock-cells =3D <1>; clocks =3D <&x23_clk>; clock-names =3D "xin"; + idt,shutdown =3D <0>; + idt,output-enable-active =3D <1>; }; }; =20 --=20 2.35.1.1320.gc452695387.dirty