<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:PMingLiU;
panose-1:2 2 5 0 0 0 0 0 0 0;}
@font-face
{font-family:MingLiU;
panose-1:2 2 5 9 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:PMingLiU;
panose-1:2 1 6 1 0 1 1 1 1 1;}
@font-face
{font-family:MingLiU;
panose-1:2 1 6 9 0 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML \9810\8A2D\683C\5F0F \5B57\5143";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:MingLiU;}
span.HTML
{mso-style-name:"HTML \9810\8A2D\683C\5F0F \5B57\5143";
mso-style-priority:99;
mso-style-link:"HTML \9810\8A2D\683C\5F0F";
font-family:MingLiU;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="ZH-TW" link="#0563C1" vlink="#954F72" style="text-justify-trim:punctuation">
<div class="WordSection1">
<pre><span lang="EN-US" style="font-family:"Calibri",sans-serif;color:black">Hi </span><span lang="EN-US" style="font-family:"Calibri",sans-serif;color:black">Patrick<o:p></o:p></span></pre>
<pre><span lang="EN-US" style="color:black"><o:p> </o:p></span></pre>
<pre><i><span lang="EN-US" style="color:black">> I looked briefly at the datasheet for this hardware [1]. It appears to<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> expose an SMBus interface for the features you mentioned. The most<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> straight-forward way to get this implemented is to create a kernel<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> driver for most of the features you mentioned. If you implement a<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> driver for this hardware that interacts with the hwmon, eeprom, and LED/GPIO<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> subsystems in the kernel(*), you'll be able to reuse a lot of existing<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> OpenBMC functionality without rewriting any userspace code.<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">><o:p> </o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> - Sensor<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> - Kernel: hwmon<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> - Userspace: phosphor-hwmon or dbus-sensors<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> - VPD<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> - Kernel: eeprom<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> - Userspace: entity-manager (I think)<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> - LED control<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> - Kernel: LED / GPIO<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> - Userspace: phosphor-led-manager<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">><o:p> </o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> The only part that wouldn't be covered would be the "Brick Protection".<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> We'd need to see some more information on how this is exposed but you<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> might be able to work it into the existing phosphor-bmc-code-mgmt<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> repository. For power supplies, they did create a separate repository<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> (phosphor-psu-code-mgmt) but I think they relied on some kernel APIs for<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> doing part of the work.<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">><o:p> </o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> (*) Depending on how the bittware hardware is implemented at an SMBus<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> level you may end up with multiple smaller drivers (this is better).<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> If there is a single SMBus address for all these functions, you'll<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> likely end up with one big driver.<o:p></o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">><o:p> </o:p></span></i></pre>
<pre><i><span lang="EN-US" style="color:black">> 1. </span></i><span lang="EN-US"><a href="https://www.bittware.com/wp-content/uploads/datasheets/ds-250-soc.pdf"><i>https://www.bittware.com/wp-content/uploads/datasheets/ds-250-soc.pdf</i></a><i><span style="color:black"><o:p></o:p></span></i></span></pre>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<pre><span lang="EN-US" style="font-family:"Calibri",sans-serif;color:black">Sorry for late reply.<o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></pre>
<pre><span lang="EN-US" style="font-family:"Calibri",sans-serif;color:black">Because the 250-soc card needs to adjust the io expander to get the relevant information (e.g. temperature, VPD ...).<o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-family:"Calibri",sans-serif;color:black">I think a dynamic detection function may be needed to handle the presence of the card and dynamically adjust the io expander.<o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-family:"Calibri",sans-serif;color:black">On the other hand, I just want to be able to integrate all the functions.<o:p></o:p></span></pre>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Ben<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<p><span style="font-family:'Calibri';font-size:11pt; color:#000000;"><b>---------------------------------------------------------------------------------------------------------------------------------------------------------------</b></span></p>
<p><span style="font-family:'Calibri';font-size:11pt; color:#000000;"><b>This email contains confidential or legally privileged information and is for the sole use of its intended recipient. </b></span></p>
<p><span style="font-family:'Calibri';font-size:11pt; color:#000000;"><b>Any unauthorized review, use, copying or distribution of this email or the content of this email is strictly prohibited.</b></span></p>
<p><span style="font-family:'Calibri';font-size:11pt; color:#000000;"><b>If you are not the intended recipient, you may reply to the sender and should delete this e-mail immediately.</b></span></p>
<p><span style="font-family:'Calibri';font-size:11pt; color:#000000;"><b>---------------------------------------------------------------------------------------------------------------------------------------------------------------</b></span></p></body>
</html>