From: Robin van der Gracht <robin@protonic.nl>
To: barebox@lists.infradead.org
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
Robin van der Gracht <robin@protonic.nl>,
david@protonic.nl
Subject: [PATCH 0/9] ARM: boards: protonic-imx6: Updates
Date: Thu, 16 Jun 2022 15:11:05 +0200 [thread overview]
Message-ID: <20220616131114.214628-1-robin@protonic.nl> (raw)
Our USB FIT boot is now broken and we can no longer aquire the RFID I2C
eeprom chips we're using to store board serial and MAC address.
With this patchstack I'm proposing fusing the serial in the ocotp GP1
register as an alternative to the RFID eeprom and making the usb boot
sequence a boot entry to avoid the race condition we now have.
The patchstack also includes some minor fixes/changes I found during
implementation of the above.
- Robin
Robin van der Gracht (9):
ARM: boards: protonic-imx6: prtvt7 hardkey inputs are active low
ARM: boards: protonic-imx6: Update comment to match a recent code
update
ARM: boards: protonic-imx6: Free allocated autoboot_timeout string
ARM: boards: protonic-imx6: Always free allocated alias string
ARM: boards: protonic-imx6: Remove unsused argument from
prt_imx6_usb_mount
ARM: boards: protonic-imx6: Register prt-usb boot entry
ARM: boards: protonic-imx6: Remove usb_delay from the priv struct
ARM: boards: protonic-imx6: Read serial and mac from fuses if
available
ARM: boards: protonic-imx6: Register serial_number parameter with
ocotp
arch/arm/boards/protonic-imx6/board.c | 215 +++++++++++++++++++-------
1 file changed, 159 insertions(+), 56 deletions(-)
--
2.34.1
next reply other threads:[~2022-06-16 13:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 13:11 Robin van der Gracht [this message]
2022-06-16 13:11 ` [PATCH 1/9] ARM: boards: protonic-imx6: prtvt7 hardkey inputs are active low Robin van der Gracht
2022-06-16 16:28 ` Oleksij Rempel
2022-06-16 16:38 ` Oleksij Rempel
2022-06-17 6:57 ` Sascha Hauer
2022-06-17 8:44 ` Marco Felsch
2022-06-20 7:51 ` Ahmad Fatoum
2022-06-20 8:16 ` Robin van der Gracht
2022-06-20 15:42 ` Robin van der Gracht
2022-06-20 6:48 ` Robin van der Gracht
2022-06-20 7:23 ` Oleksij Rempel
2022-06-16 13:11 ` [PATCH 2/9] ARM: boards: protonic-imx6: Update comment to match a recent code update Robin van der Gracht
2022-06-17 7:00 ` Sascha Hauer
2022-06-20 6:40 ` Robin van der Gracht
2022-06-16 13:11 ` [PATCH 3/9] ARM: boards: protonic-imx6: Free allocated autoboot_timeout string Robin van der Gracht
2022-06-16 13:11 ` [PATCH 4/9] ARM: boards: protonic-imx6: Always free allocated alias string Robin van der Gracht
2022-06-16 13:11 ` [PATCH 5/9] ARM: boards: protonic-imx6: Remove unsused argument from prt_imx6_usb_mount Robin van der Gracht
2022-06-16 13:11 ` [PATCH 6/9] ARM: boards: protonic-imx6: Register prt-usb boot entry Robin van der Gracht
2022-06-16 13:11 ` [PATCH 7/9] ARM: boards: protonic-imx6: Remove usb_delay from the priv struct Robin van der Gracht
2022-06-16 13:11 ` [PATCH 8/9] ARM: boards: protonic-imx6: Read serial and mac from fuses if available Robin van der Gracht
2022-06-16 13:11 ` [PATCH 9/9] ARM: boards: protonic-imx6: Register serial_number parameter with ocotp Robin van der Gracht
2022-06-17 7:10 ` (subset) [PATCH 0/9] ARM: boards: protonic-imx6: Updates Sascha Hauer
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=20220616131114.214628-1-robin@protonic.nl \
--to=robin@protonic.nl \
--cc=barebox@lists.infradead.org \
--cc=david@protonic.nl \
--cc=o.rempel@pengutronix.de \
--subject='Re: [PATCH 0/9] ARM: boards: protonic-imx6: Updates' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox