Hi Andrejs,
On Wed, Dec 20, 2023 at 7:39 AM Andrejs Cainikovs
<andrejs.cainik...@gmail.com> wrote:
> diff --git a/arch/arm/dts/fsl-imx8qxp-colibri-u-boot.dtsi
> b/arch/arm/dts/fsl-imx8qxp-colibri-u-boot.dtsi
> index a6af4e5e2b7..6ab6b1f9ee6 100644
> --- a/arch/arm/dts/fsl-imx8qxp-colibri-u-boot.dtsi
> +++ b/arch/arm/dts/fsl-imx8qxp-colibri-u-boot.dtsi
> @@ -84,6 +84,21 @@
> bootph-some-ram;
> };
>
> +&gpio_expander_43 {
> + usb-bypass-n-hog {
> + gpio-hog;
> + gpios = <5 GPIO_ACTIVE_LOW>;
> + line-name = "usb-bypass-n";
> + output-high;
> + };
> + usb-reset-n-hog {
> + gpio-hog;
> + gpios = <4 GPIO_ACTIVE_LOW>;
> + line-name = "usb-reset-n";
> + output-low;
> + };
> +};
Patch looks good from a U-Boot perspective, but just want to
understand why the imx8qxp/imx8qm boards
in U-Boot use devicetrees based on downstream NXP instead of the
mainline kernel dts?
Shouldn't this 'hub out of reset' be added in mainline Linux first and
then just sync the dts in U-Boot?
