linux-kernel - [RFC] Generic PHY interface extention for dynamic configuration

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 9 Sep 2015 10:52:34 +0800
From:	Shawn Lin <shawn.lin@...k-chips.com>
To:	Kishon Vijay Abraham I <kishon@...com>
Cc:	shawn.lin@...k-chips.com, linux-kernel@...r.kernel.org
Subject: [RFC] Generic PHY interface extention for dynamic configuration

Hi Kishon,

	Now, Generic PHY framework just provide four interfaces(AKA: 
init/exit/power_on/power_off). Also, these fours itfs take struct phy as
unique argument.Is it means that the generic PHY framework can't support 
to modify PHY configuration at run-time for diff cases?
	Actually I'm writing some code for supporting emmc controller's phy. 
And sometimes it indeed need to modify the phy's configuration. But I 
have no idea about how to deal with it in current framework. So I send 
this RFC to you and mailing.
	
Thanks.

-- 
Best Regards
Shawn Lin

--
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/