linux-kernel - Re: [PATCH v1 3/6] usb: host: Stops USB controller init if PLL fails to lock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 21 Jan 2019 11:16:52 +0300
From:   Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To:     Yinbo Zhu <yinbo.zhu@....com>,
        Alan Stern <stern@...land.harvard.edu>
Cc:     xiaobo.xie@....com, jerry.huang@....com, ran.wang_1@....com,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Ramneek Mehresh <ramneek.mehresh@...escale.com>,
        Nikhil Badola <nikhil.badola@...escale.com>,
        Suresh Gupta <suresh.gupta@...escale.com>,
        linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 3/6] usb: host: Stops USB controller init if PLL fails
 to lock

Hello!

On 21.01.2019 6:13, Yinbo Zhu wrote:

> From: yinbo.zhu <yinbo.zhu@....com>
> 
> USB erratum-A006918 workaround tries to start internal PHY inside
> uboot (when PLL fails to lock). However, if the workaround also
> fails, then USB initialization is also stopped inside Linux.
> Erratum-A006918 workaround failure creates "fsl,erratum_a006918"
> node in device-tree. Presence of this node in device-tree is
> used to stop USB controller initialization in Linux
> 
> Signed-off-by: Ramneek Mehresh <ramneek.mehresh@...escale.com>
> Signed-off-by: Suresh Gupta <suresh.gupta@...escale.com>
> Signed-off-by: yinbo.zhu <yinbo.zhu@....com>
> ---
>   drivers/usb/host/ehci-fsl.c      |    5 +++++
>   drivers/usb/host/fsl-mph-dr-of.c |    5 +++++
>   2 files changed, 10 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/usb/host/ehci-fsl.c b/drivers/usb/host/ehci-fsl.c
> index a28ec1e..6884130 100644
> --- a/drivers/usb/host/ehci-fsl.c
> +++ b/drivers/usb/host/ehci-fsl.c
> @@ -224,6 +224,11 @@ static int ehci_fsl_setup_phy(struct usb_hcd *hcd,
>   		portsc |= PORT_PTS_PTW;
>   		/* fall through */
>   	case FSL_USB2_PHY_UTMI:
> +		if (pdata->has_fsl_erratum_a006918) {
> +			pr_warn("fsl-ehci: USB PHY clock invalid\n");
> +			return -EINVAL;
> +		}
> +
>   	case FSL_USB2_PHY_UTMI_DUAL:
>   		/* PHY_CLK_VALID bit is de-featured from all controller
>   		 * versions below 2.4 and is to be checked only for
> diff --git a/drivers/usb/host/fsl-mph-dr-of.c b/drivers/usb/host/fsl-mph-dr-of.c
> index 677f9d5..7e07701 100644
> --- a/drivers/usb/host/fsl-mph-dr-of.c
> +++ b/drivers/usb/host/fsl-mph-dr-of.c
> @@ -225,6 +225,11 @@ static int fsl_usb2_mph_dr_of_probe(struct platform_device *ofdev)
>   	pdata->has_fsl_erratum_a005697 =
>   		of_property_read_bool(np, "fsl,usb_erratum-a005697");
>   
> +	if (of_get_property(np, "fsl,erratum_a006918", NULL))

    of_property_read_bool() perhaps?

> +		pdata->has_fsl_erratum_a006918 = 1;
> +	else
> +		pdata->has_fsl_erratum_a006918 = 0;
> +
>   	/*
>   	 * Determine whether phy_clk_valid needs to be checked
>   	 * by reading property in device tree

MBR, Sergei