From: Marcel Ziswiler <marcel@ziswiler.com>
To: u-boot@lists.denx.de
Cc: Fabio Estevam <festevam@gmail.com>,
Jesse Taube <mr.bossman075@gmail.com>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Stefano Babic <sbabic@denx.de>, Wolfgang Denk <wd@denx.de>
Subject: [PATCH v2 1/8] vf610: synchronise device tree with linux
Date: Fri, 26 Aug 2022 20:31:34 +0200 [thread overview]
Message-ID: <20220826183141.789236-2-marcel@ziswiler.com> (raw)
In-Reply-To: <20220826183141.789236-1-marcel@ziswiler.com>
From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Synchronise device tree with linux v6.0-rc1 plus the recent DDR pinmux
addition still being in-flight.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
---
(no changes since v1)
arch/arm/dts/vf610-pinfunc.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/dts/vf610-pinfunc.h b/arch/arm/dts/vf610-pinfunc.h
index 740276431aa..b7b7322a2d1 100644
--- a/arch/arm/dts/vf610-pinfunc.h
+++ b/arch/arm/dts/vf610-pinfunc.h
@@ -802,7 +802,6 @@
#define VF610_PAD_PTE28__EWM_OUT 0x214 0x000 ALT7 0x0
#define VF610_PAD_PTA7__GPIO_134 0x218 0x000 ALT0 0x0
#define VF610_PAD_PTA7__VIU_PIX_CLK 0x218 0x3AC ALT1 0x1
-
#define VF610_PAD_DDR_RESETB 0x21c 0x000 ALT0 0x0
#define VF610_PAD_DDR_A15__DDR_A_15 0x220 0x000 ALT0 0x0
#define VF610_PAD_DDR_A14__DDR_A_14 0x224 0x000 ALT0 0x0
@@ -853,4 +852,5 @@
#define VF610_PAD_DDR_ODT0__DDR_ODT_1 0x2d8 0x000 ALT0 0x0
#define VF610_PAD_DDR_DDRBYTE1__DDR_DDRBYTE1 0x2dc 0x000 ALT0 0x0
#define VF610_PAD_DDR_DDRBYTE2__DDR_DDRBYTE2 0x2e0 0x000 ALT0 0x0
+
#endif
--
2.35.1
next prev parent reply other threads:[~2022-08-26 18:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 18:31 [PATCH v2 0/8] arm: dts: imx: sync device trees with upstream linux kernel part 1 Marcel Ziswiler
2022-08-26 18:31 ` Marcel Ziswiler [this message]
2022-08-26 18:31 ` [PATCH v2 2/8] imxrt1020: fix lpuart issue in common u-boot device tree Marcel Ziswiler
2022-08-26 18:31 ` [PATCH v2 3/8] imxrt1050: synchronise device tree with linux Marcel Ziswiler
2022-08-28 6:50 ` Jesse Taube
2022-10-22 12:57 ` Marcel Ziswiler
2022-10-24 1:39 ` Jesse Taube
2022-08-26 18:31 ` [PATCH v2 4/8] imx8ulp: " Marcel Ziswiler
2022-08-26 18:31 ` [PATCH v2 5/8] imx8mq: " Marcel Ziswiler
2022-08-26 18:31 ` [PATCH v2 6/8] imx8mp: " Marcel Ziswiler
2022-08-26 18:31 ` [PATCH v2 7/8] imx8mn: " Marcel Ziswiler
2022-08-26 18:31 ` [PATCH v2 8/8] imx8mm: " Marcel Ziswiler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220826183141.789236-2-marcel@ziswiler.com \
--to=marcel@ziswiler.com \
--cc=festevam@gmail.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=marcel.ziswiler@toradex.com \
--cc=mr.bossman075@gmail.com \
--cc=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
--cc=wd@denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).