linux-kernel - Re: [PATCH v2] usb: phy: msm: Make phy

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]

Message-ID: <53F5925E.3010802@linaro.org>
Date:	Thu, 21 Aug 2014 07:31:58 +0100
From:	Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To:	balbi@...com
CC:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v2] usb: phy: msm: Make phy_reset clk and reset line optional.

Thanks Felipe,

On 20/08/14 16:57, Felipe Balbi wrote:
> On Thu, Jul 17, 2014 at 09:16:40PM +0100, Srinivas Kandagatla wrote:
>> This patch makes the phy reset clk and reset line optional as this clk
>> is not available on boards like IFC6410 with APQ8064.
>>
>> phy-reset clk is only used as argument to the mach level callbacks, so
>> this patch adds condition before clk_get calls so that the driver
>> wouldn't fail on SOCs which do not have this support.
>>
>> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
>> ---
>> Hi Felipe,
>>
>> With this new patch now the error message is only printed if the SOC actually supports
>> the phy reset clk, for SOCs like APQ8064 where there is no phy reset clock or
>> the callback which takes it there is no point in doing a clk_get call in the first place.
>
> doesn't apply. Please rebase on top of v3.17-rc1
>
this is because a previous version of the same patch got applied.
Anyway I will rebase this patch and send v3.

thanks,
srini
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/