<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX Processors中的主题 Re: FEC PHY_REGISTER_FIXUP_FOR_UID</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/FEC-PHY-REGISTER-FIXUP-FOR-UID/m-p/692208#M107304</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hai Victor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Thankyou for your quick response regarding the phy_uid_fixup.&amp;nbsp; &amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;C.Himabindu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 14 Jul 2017 09:13:52 GMT</pubDate>
    <dc:creator>himabindu</dc:creator>
    <dc:date>2017-07-14T09:13:52Z</dc:date>
    <item>
      <title>FEC PHY_REGISTER_FIXUP_FOR_UID</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/FEC-PHY-REGISTER-FIXUP-FOR-UID/m-p/692206#M107302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Currently I am working on IMX6 Sololite Linux Kernel Version-3.10.17. I tried with the Latest Kernel version-4.1.2.&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;FEC Driver :-&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;Can I get the usage of phy_register_fixup_for_uid(PHY_ID_KSZ9021, MICREL_PHY_ID_MASK,ksz9021rn_phy_fixup); &lt;BR /&gt;which i came across in Linux Kernel Version-3.0.35 instead of phy-reset.&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;C.Himabindu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Jul 2017 12:06:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/FEC-PHY-REGISTER-FIXUP-FOR-UID/m-p/692206#M107302</guid>
      <dc:creator>himabindu</dc:creator>
      <dc:date>2017-07-11T12:06:51Z</dc:date>
    </item>
    <item>
      <title>Re: FEC PHY_REGISTER_FIXUP_FOR_UID</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/FEC-PHY-REGISTER-FIXUP-FOR-UID/m-p/692207#M107303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sometimes the specific interaction between the platform and the PHY requires special handling.&lt;BR /&gt;For instance, to change where the PHY's clock input is, or to add a delay to account for latency issues in the data path.&lt;BR /&gt;In order to support such contingencies, the PHY Layer allows platform code to register fixups to be run when the PHY is brought up (or subsequently reset).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the PHY Layer brings up a PHY it checks to see if there are any fixups registered for it,&lt;BR /&gt;matching based on UID (contained in the PHY device's phy_id field) and the bus identifier (contained in phydev-&amp;gt;dev.bus_id).&lt;BR /&gt;Both must match, however two constants, PHY_ANY_ID and PHY_ANY_UID, are provided as wildcards for the bus ID and UID, respectively.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When a match is found, the PHY layer will invoke the run function associated with the fixup.&lt;BR /&gt;This function is passed a pointer to the phy_device of interest.&lt;BR /&gt;It should therefore only operate on that PHY.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Victor&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Jul 2017 08:25:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/FEC-PHY-REGISTER-FIXUP-FOR-UID/m-p/692207#M107303</guid>
      <dc:creator>b36401</dc:creator>
      <dc:date>2017-07-14T08:25:11Z</dc:date>
    </item>
    <item>
      <title>Re: FEC PHY_REGISTER_FIXUP_FOR_UID</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/FEC-PHY-REGISTER-FIXUP-FOR-UID/m-p/692208#M107304</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hai Victor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Thankyou for your quick response regarding the phy_uid_fixup.&amp;nbsp; &amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;C.Himabindu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Jul 2017 09:13:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/FEC-PHY-REGISTER-FIXUP-FOR-UID/m-p/692208#M107304</guid>
      <dc:creator>himabindu</dc:creator>
      <dc:date>2017-07-14T09:13:52Z</dc:date>
    </item>
  </channel>
</rss>

