On 10/23/2017 05:12 PM, Guenter Roeck wrote:
On Mon, Oct 23, 2017 at 10:23:02AM -0500, Eddie James wrote:
On 10/21/2017 11:10 AM, Guenter Roeck wrote:
On Thu, Oct 19, 2017 at 03:57:08PM -0500, eaja...@linux.vnet.ibm.com wrote:
From: "Edward A. James"
The MFR_ID and MFR_MODEL, which are ma
On Mon, Oct 23, 2017 at 10:23:02AM -0500, Eddie James wrote:
>
>
> On 10/21/2017 11:10 AM, Guenter Roeck wrote:
> >On Thu, Oct 19, 2017 at 03:57:08PM -0500, eaja...@linux.vnet.ibm.com wrote:
> >>From: "Edward A. James"
> >>
> >>The MFR_ID and MFR_MODEL, which are manually read before probing the
On 10/21/2017 11:10 AM, Guenter Roeck wrote:
On Thu, Oct 19, 2017 at 03:57:08PM -0500, eaja...@linux.vnet.ibm.com wrote:
From: "Edward A. James"
The MFR_ID and MFR_MODEL, which are manually read before probing the
pmbus core, are only valid for the two pages that the ir35221 has
available.
On Thu, Oct 19, 2017 at 03:57:08PM -0500, eaja...@linux.vnet.ibm.com wrote:
> From: "Edward A. James"
>
> The MFR_ID and MFR_MODEL, which are manually read before probing the
> pmbus core, are only valid for the two pages that the ir35221 has
> available. Since we don't know the state of the dev
From: "Edward A. James"
The MFR_ID and MFR_MODEL, which are manually read before probing the
pmbus core, are only valid for the two pages that the ir35221 has
available. Since we don't know the state of the device when we start
probing, set the page number first before reading id and model.
Sig
5 matches
Mail list logo