From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] [PATCH] Platform/RaspberryPi: Dynamically build UARTs info in ACPI To: Sunny Wang ,devel@edk2.groups.io From: =?UTF-8?B?TWFyaW8gQsSDbMSDbmljxIM=?= X-Originating-Location: Galati, RO (5.13.251.2) X-Originating-Platform: Windows Chrome 89 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Thu, 11 Mar 2021 07:57:24 -0800 References: <20210306092406.1706-1-sunny.hsuanwen.wang@gmail.com> In-Reply-To: <20210306092406.1706-1-sunny.hsuanwen.wang@gmail.com> Message-ID: <18749.1615478244192381855@groups.io> Content-Type: multipart/alternative; boundary="zahDKJXWzxuKREV7XOqD" --zahDKJXWzxuKREV7XOqD Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable >=20 > +=3D0D > + PinFunction (Exclusive, PullDown, BCM_ALT3, "\\_SB.GDV0.GPI0", 0, Reso= = =3D > urceConsumer, , ) { 32, 33 }=3D0D > +=3D0D > + // fake the CTS signal as we don't support HW flow control yet=3D0D > + // BCM_ALT2 is set as output (low) by default=3D0D > + PinFunction (Exclusive, PullNone, BCM_ALT2, "\\_SB.GDV0.GPI0", 0, Reso= = =3D > urceConsumer, , ) { 31 }=3D0D > })=3D0D >=20 I think it's better to do the pin muxing in ConfigDxe, depending on which = UART is free to be used for Bluetooth. --zahDKJXWzxuKREV7XOqD Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
+=3D0D
+ Pin= Function (Exclusive, PullDown, BCM_ALT3, "\\_SB.GDV0.GPI0", 0, Reso=3D
urceConsumer, , ) { 32, 33 }=3D0D
+=3D0D
+ // fake t= he CTS signal as we don't support HW flow control yet=3D0D
+ // = BCM_ALT2 is set as output (low) by default=3D0D
+ PinFunction (Exc= lusive, PullNone, BCM_ALT2, "\\_SB.GDV0.GPI0", 0, Reso=3D
urceC= onsumer, , ) { 31 }=3D0D
})=3D0D
I think it's better to do the pin m= uxing in ConfigDxe, depending on which UART is free to be used for Bluetoot= h.
--zahDKJXWzxuKREV7XOqD--