From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: Pete Batard <pete@akeo.ie>,
Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Andrei Warkentin (awarkentin@vmware.com)"
<awarkentin@vmware.com>,
Jeff Booher-Kaeding <Jeff.Booher-Kaeding@arm.com>
Cc: Leif Lindholm <leif@nuviainc.com>
Subject: Re: [edk2-devel] [PATCH v1 1/1] Platform/RaspberryPi/ConfigDxe: Fix JTAG Pinout for Pi3/4
Date: Mon, 5 Oct 2020 16:30:03 +0200 [thread overview]
Message-ID: <4a00f26e-f7f2-be36-cfd8-8799afb72101@arm.com> (raw)
In-Reply-To: <3e9fb07b-a330-6a3a-0e0e-2221819c5483@akeo.ie>
On 10/5/20 2:07 PM, Pete Batard wrote:
> With Andrei's reply, that's an RB for me:
>
> On 2020.09.29 15:01, Samer El-Haj-Mahmoud wrote:
>> Thanks Pete and Andrei. Should we count these as RB or AB for the patch?
>>
>> Reviewed-by: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
>>
>> *From:* devel@edk2.groups.io <devel@edk2.groups.io> *On Behalf Of
>> *Andrei Warkentin via groups.io
>> *Sent:* Monday, September 21, 2020 4:01 PM
>> *To:* Pete Batard <pete@akeo.ie>; Jeff Booher-Kaeding
>> <Jeff.Booher-Kaeding@arm.com>; devel@edk2.groups.io
>> *Cc:* Ard Biesheuvel <Ard.Biesheuvel@arm.com>; Leif Lindholm
>> <leif@nuviainc.com>
>> *Subject:* Re: [edk2-devel] [PATCH v1 1/1]
>> Platform/RaspberryPi/ConfigDxe: Fix JTAG Pinout for Pi3/4
>>
>> Hi folks,
>>
>> No objection at all. IIRC the original pin selection was driven by an
>> article I read about using OpenOCD with Pi 3.
>>
>> A
>>
>> ------------------------------------------------------------------------
>>
>> *From:*Pete Batard <pete@akeo.ie <mailto:pete@akeo.ie>>
>> *Sent:* Tuesday, September 15, 2020 7:26 AM
>> *To:* Jeff Booher-Kaeding <jeff.booher-kaeding@arm.com
>> <mailto:jeff.booher-kaeding@arm.com>>; devel@edk2.groups.io
>> <mailto:devel@edk2.groups.io> <devel@edk2.groups.io
>> <mailto:devel@edk2.groups.io>>
>> *Cc:* Ard Biesheuvel <ard.biesheuvel@arm.com
>> <mailto:ard.biesheuvel@arm.com>>; Leif Lindholm <leif@nuviainc.com
>> <mailto:leif@nuviainc.com>>; Andrei Warkentin <awarkentin@vmware.com
>> <mailto:awarkentin@vmware.com>>
>> *Subject:* Re: [PATCH v1 1/1] Platform/RaspberryPi/ConfigDxe: Fix JTAG
>> Pinout for Pi3/4
>>
>> Copying Andrei on this, as the existing JTAG pinout is not technically
>> incorrect, since GPIO pin 4 can be used for TDI in ALT5 mode, and we are
>> using the relevant ALT mode in the existing code. See
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsysprogs.com%2FVisualKernel%2Ftutorials%2Fraspberry%2Fjtagsetup%2F&data=02%7C01%7Cawarkentin%40vmware.com%7C1c1badf5e6f1433b44b508d859728a32%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637357695767996220&sdata=rGIzM4Io36gFJrAK%2F4xZs0fm0DpXVvamhOYYXfc09ek%3D&reserved=0
>>
>>
>> As far as I'm concerned, I think it makes sense to use the same ALT mode
>> and have all the JTAG pins grouped, but I'd like to confirm whether we
>> deliberately chose not to use GPIO 26 in order to leave it available for
>> some other purpose, before I approve this patch.
>>
>> If Andrei says he's okay with it, then I see no objection to this change.
>>
>> Regards,
>>
>> /Pete
>>
>> On 2020.09.14 22:32, Jeff Booher-Kaeding wrote:
>> > Updated the pinout to match the Pi4 datasheet, tested with the
>> RPi4, Pi3 Datasheet has same pinout.
>> >
>> > Signed-off-by: Jeff Booher-Kaeding <Jeff.booher-kaeding@arm.com
>> <mailto:Jeff.booher-kaeding@arm.com>>
>> >
>> > Cc: Ard Biesheuvel <ard.biesheuvel@arm.com
>> <mailto:ard.biesheuvel@arm.com>>
>> > Cc: Leif Lindholm <leif@nuviainc.com <mailto:leif@nuviainc.com>>
>> > Cc: Pete Batard <pete@akeo.ie <mailto:pete@akeo.ie>>
Pushed as fc49849a8ebc..8ef23e848b76
Thanks all,
prev parent reply other threads:[~2020-10-05 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 21:32 [PATCH v1 1/1] Platform/RaspberryPi/ConfigDxe: Fix JTAG Pinout for Pi3/4 Jeff.Booher-Kaeding
2020-09-15 12:26 ` Pete Batard
2020-09-21 20:01 ` Andrei Warkentin
2020-09-29 14:01 ` [edk2-devel] " Samer El-Haj-Mahmoud
2020-10-05 12:07 ` Pete Batard
2020-10-05 14:30 ` Ard Biesheuvel [this message]
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-list 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=4a00f26e-f7f2-be36-cfd8-8799afb72101@arm.com \
--to=devel@edk2.groups.io \
/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