<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Modest Destiny (Posts about Embedded)</title><link>https://blog.modest-destiny.com/</link><description></description><atom:link href="https://blog.modest-destiny.com/categories/embedded.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2021 Adam Basfop Cavendish </copyright><lastBuildDate>Mon, 22 Mar 2021 08:19:52 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Linux Device Tree Pinctrl Tutorial</title><link>https://blog.modest-destiny.com/posts/linux-device-tree-pinctrl-tutorial/</link><dc:creator>Adam Basfop Cavendish</dc:creator><description>&lt;div&gt;&lt;p&gt;When porting drivers on a specific board for a comparatively new linux kernel, it is common to edit the linux device tree files to put together all the device configurations with register values, working modes and pin control offsets set to expected values.&lt;/p&gt;
&lt;p&gt;Here in this post we focus on the exact steps one needs to find the correct pin control offset for specific devices. Here we'd take TI's AM4379 (AM437x) chip as an example for this tutorial.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blog.modest-destiny.com/posts/linux-device-tree-pinctrl-tutorial/"&gt;Read more…&lt;/a&gt; (8 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>Device Tree</category><category>Embedded</category><category>Kernel</category><category>Linux</category><guid>https://blog.modest-destiny.com/posts/linux-device-tree-pinctrl-tutorial/</guid><pubDate>Thu, 09 Aug 2018 12:09:17 GMT</pubDate></item></channel></rss>