* i2c error for ME port
@ 2019-11-25 19:39 Vijay Khemka
2019-11-25 19:41 ` James Feist
0 siblings, 1 reply; 8+ messages in thread
From: Vijay Khemka @ 2019-11-25 19:39 UTC (permalink / raw)
To: james.feist, jason.m.bills; +Cc: openbmc
[-- Attachment #1: Type: text/plain, Size: 7260 bytes --]
Hi James/Jason,
I am seeing following i2c error on i2c bus connected to ME. It is one time output whenever server is powered on or reboot. Please suggest you can think of anything here.
Regards
-Vijay
[ 7358.450768] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after processed read.
[ 7358.465565] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after processed read.
[ 7358.480358] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after processed read.
[ 7358.499663] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after processed read.
[ 7358.514873] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after processed read.
[ 7358.591790] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7358.610955] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000002, but was 0x00000002
[ 7358.651381] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7358.670515] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000004, but was 0x00000004
[ 7358.689601] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7358.708712] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000002, but was 0x00000002
[ 7358.728303] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7358.747422] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000004, but was 0x00000004
[ 7358.766525] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7358.785590] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000002, but was 0x00000002
[ 7358.810138] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7358.829301] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000004, but was 0x00000004
[ 7358.848392] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7358.867479] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000002, but was 0x00000002
[ 7358.887271] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7358.906383] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000004, but was 0x00000004
[ 7358.925481] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7358.944558] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000002, but was 0x00000002
[ 7358.964950] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7358.984050] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000004, but was 0x00000004
[ 7359.003147] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7359.022223] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000002, but was 0x00000002
[ 7359.042183] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7359.061325] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000004, but was 0x00000004
[ 7359.080423] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7359.099500] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000002, but was 0x00000002
[ 7359.121159] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7359.140294] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000004, but was 0x00000004
[ 7359.159381] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7359.178452] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000002, but was 0x00000002
[ 7359.198150] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7359.217286] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000004, but was 0x00000004
[ 7359.236402] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7359.255486] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000002, but was 0x00000002
[ 7359.275289] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7359.294409] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000004, but was 0x00000004
[ 7359.313490] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000084, but was 0x00000084
[ 7359.332585] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000001, but was 0x00000001
[ 7359.351578] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after processed read.
[ 7359.366182] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000004, but was 0x00000004
[ 7359.385132] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000001, but was 0x00000001
[ 7359.404090] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after processed read.
[ 7359.418701] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000004, but was 0x00000004
[ 7359.437650] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000001, but was 0x00000001
[ 7359.456611] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after processed read.
[ 7359.471220] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000004, but was 0x00000004
[ 7359.490170] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000001, but was 0x00000001
[ 7359.509683] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after processed read.
[ 7359.524307] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq. expected 0x80000004, but was 0x00000004
Jan 01 02:02:41 tiogapass psusensor[316]: PredictiveFailure assert
Jan 01 02:02:41 tiogapass psusensor[316]: PredictiveFailure assert
Jan 01 02:02:41 tiogapass psusensor[316]: PredictiveFailure assert
Jan 01 02:02:41 tiogapass psusensor[316]: PredictiveFailure assert
Jan 01 02:02:41 tiogapass psusensor[316]: PredictiveFailure assert
Jan 01 02:02:41 tiogapass psusensor[316]: PredictiveFailure assert
Jan 01 02:02:41 tiogapass psusensor[316]: PredictiveFailure assert
Jan 01 02:02:41 tiogapass psusensor[316]: PredictiveFailure assert
Jan 01 02:02:41 tiogapass psusensor[316]: PredictiveFailure assert
Jan 01 02:02:42 tiogapass psusensor[316]: PredictiveFailure deassert
Jan 01 02:02:42 tiogapass psusensor[316]: PredictiveFailure deassert
Jan 01 02:02:42 tiogapass psusensor[316]: PredictiveFailure deassert
Jan 01 02:02:42 tiogapass psusensor[316]: PredictiveFailure deassert
Jan 01 02:02:42 tiogapass psusensor[316]: PredictiveFailure deassert
Jan 01 02:02:42 tiogapass psusensor[316]: PredictiveFailure deassert
Jan 01 02:02:42 tiogapass psusensor[316]: PredictiveFailure deassert
Jan 01 02:02:42 tiogapass psusensor[316]: PredictiveFailure deassert
Jan 01 02:02:42 tiogapass psusensor[316]: PredictiveFailure deassert
[-- Attachment #2: Type: text/html, Size: 13746 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: i2c error for ME port
2019-11-25 19:39 i2c error for ME port Vijay Khemka
@ 2019-11-25 19:41 ` James Feist
2019-11-25 20:20 ` Jae Hyun Yoo
0 siblings, 1 reply; 8+ messages in thread
From: James Feist @ 2019-11-25 19:41 UTC (permalink / raw)
To: Vijay Khemka, jason.m.bills; +Cc: openbmc, Jae Hyun Yoo
On 11/25/19 11:39 AM, Vijay Khemka wrote:
> Hi James/Jason,
+ Jae, any ideas?
>
> I am seeing following i2c error on i2c bus connected to ME. It is one
> time output whenever server is powered on or reboot. Please suggest you
> can think of anything here.
>
> Regards
>
> -Vijay
>
> [ 7358.450768] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
> processed read.
>
> [ 7358.465565] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
> processed read.
>
> [ 7358.480358] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
> processed read.
>
> [ 7358.499663] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
> processed read.
>
> [ 7358.514873] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
> processed read.
>
> [ 7358.591790] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7358.610955] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000002, but was 0x00000002
>
> [ 7358.651381] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7358.670515] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000004, but was 0x00000004
>
> [ 7358.689601] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7358.708712] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000002, but was 0x00000002
>
> [ 7358.728303] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7358.747422] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000004, but was 0x00000004
>
> [ 7358.766525] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7358.785590] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000002, but was 0x00000002
>
> [ 7358.810138] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7358.829301] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000004, but was 0x00000004
>
> [ 7358.848392] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7358.867479] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000002, but was 0x00000002
>
> [ 7358.887271] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7358.906383] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000004, but was 0x00000004
>
> [ 7358.925481] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7358.944558] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000002, but was 0x00000002
>
> [ 7358.964950] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7358.984050] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000004, but was 0x00000004
>
> [ 7359.003147] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7359.022223] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000002, but was 0x00000002
>
> [ 7359.042183] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7359.061325] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000004, but was 0x00000004
>
> [ 7359.080423] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7359.099500] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000002, but was 0x00000002
>
> [ 7359.121159] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7359.140294] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000004, but was 0x00000004
>
> [ 7359.159381] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7359.178452] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000002, but was 0x00000002
>
> [ 7359.198150] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7359.217286] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000004, but was 0x00000004
>
> [ 7359.236402] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7359.255486] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000002, but was 0x00000002
>
> [ 7359.275289] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7359.294409] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000004, but was 0x00000004
>
> [ 7359.313490] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000084, but was 0x00000084
>
> [ 7359.332585] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000001, but was 0x00000001
>
> [ 7359.351578] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
> processed read.
>
> [ 7359.366182] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000004, but was 0x00000004
>
> [ 7359.385132] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000001, but was 0x00000001
>
> [ 7359.404090] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
> processed read.
>
> [ 7359.418701] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000004, but was 0x00000004
>
> [ 7359.437650] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000001, but was 0x00000001
>
> [ 7359.456611] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
> processed read.
>
> [ 7359.471220] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000004, but was 0x00000004
>
> [ 7359.490170] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000001, but was 0x00000001
>
> [ 7359.509683] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
> processed read.
>
> [ 7359.524307] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
> expected 0x80000004, but was 0x00000004
>
> Jan 01 02:02:41 tiogapass psusensor[316]: *PredictiveFailure assert*
>
> Jan 01 02:02:41 tiogapass psusensor[316]: *PredictiveFailure assert*
>
> Jan 01 02:02:41 tiogapass psusensor[316]: *PredictiveFailure assert*
>
> Jan 01 02:02:41 tiogapass psusensor[316]: *PredictiveFailure assert*
>
> Jan 01 02:02:41 tiogapass psusensor[316]: *PredictiveFailure assert*
>
> Jan 01 02:02:41 tiogapass psusensor[316]: *PredictiveFailure assert*
>
> Jan 01 02:02:41 tiogapass psusensor[316]: *PredictiveFailure assert*
>
> Jan 01 02:02:41 tiogapass psusensor[316]: *PredictiveFailure assert*
>
> Jan 01 02:02:41 tiogapass psusensor[316]: *PredictiveFailure assert*
>
> Jan 01 02:02:42 tiogapass psusensor[316]: *PredictiveFailure deassert*
>
> Jan 01 02:02:42 tiogapass psusensor[316]: *PredictiveFailure deassert*
>
> Jan 01 02:02:42 tiogapass psusensor[316]: *PredictiveFailure deassert*
>
> Jan 01 02:02:42 tiogapass psusensor[316]: *PredictiveFailure deassert*
>
> Jan 01 02:02:42 tiogapass psusensor[316]: *PredictiveFailure deassert*
>
> Jan 01 02:02:42 tiogapass psusensor[316]: *PredictiveFailure deassert*
>
> Jan 01 02:02:42 tiogapass psusensor[316]: *PredictiveFailure deassert*
>
> Jan 01 02:02:42 tiogapass psusensor[316]: *PredictiveFailure deassert*
>
> Jan 01 02:02:42 tiogapass psusensor[316]: *PredictiveFailure deassert*
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: i2c error for ME port
2019-11-25 19:41 ` James Feist
@ 2019-11-25 20:20 ` Jae Hyun Yoo
2019-11-25 23:02 ` Vijay Khemka
0 siblings, 1 reply; 8+ messages in thread
From: Jae Hyun Yoo @ 2019-11-25 20:20 UTC (permalink / raw)
To: James Feist, Vijay Khemka, jason.m.bills; +Cc: openbmc
Hi Vijay,
On 11/25/2019 11:41 AM, James Feist wrote:
> On 11/25/19 11:39 AM, Vijay Khemka wrote:
>> Hi James/Jason,
>
> + Jae, any ideas?
>
>
>>
>> I am seeing following i2c error on i2c bus connected to ME. It is one
>> time output whenever server is powered on or reboot. Please suggest
>> you can think of anything here.
>>
>> Regards
>>
>> -Vijay
>>
>> [ 7358.450768] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
>> processed read.
>>
>> [ 7358.465565] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
>> processed read.
>>
>> [ 7358.480358] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
>> processed read.
>>
>> [ 7358.499663] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
>> processed read.
>>
>> [ 7358.514873] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
>> processed read.
>>
>> [ 7358.591790] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
>> expected 0x80000084, but was 0x00000084
Looks like you set the second slave address for i2c4 bus. It indicates
'address 2' match event but current driver doesn't handle this event.
Can you share your i2c4 bus node setting in device tree?
Cheers,
Jae
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: i2c error for ME port
2019-11-25 20:20 ` Jae Hyun Yoo
@ 2019-11-25 23:02 ` Vijay Khemka
2019-11-25 23:20 ` Jae Hyun Yoo
0 siblings, 1 reply; 8+ messages in thread
From: Vijay Khemka @ 2019-11-25 23:02 UTC (permalink / raw)
To: Jae Hyun Yoo, James Feist, jason.m.bills; +Cc: openbmc
On 11/25/19, 12:21 PM, "Jae Hyun Yoo" <jae.hyun.yoo@linux.intel.com> wrote:
Hi Vijay,
On 11/25/2019 11:41 AM, James Feist wrote:
> On 11/25/19 11:39 AM, Vijay Khemka wrote:
>> Hi James/Jason,
>
> + Jae, any ideas?
>
>
>>
>> I am seeing following i2c error on i2c bus connected to ME. It is one
>> time output whenever server is powered on or reboot. Please suggest
>> you can think of anything here.
>>
>> Regards
>>
>> -Vijay
>>
>> [ 7358.450768] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
>> processed read.
>>
>> [ 7358.465565] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
>> processed read.
>>
>> [ 7358.480358] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
>> processed read.
>>
>> [ 7358.499663] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
>> processed read.
>>
>> [ 7358.514873] aspeed-i2c-bus 1e78a140.i2c-bus: Expected ACK after
>> processed read.
>>
>> [ 7358.591790] aspeed-i2c-bus 1e78a140.i2c-bus: irq handled != irq.
>> expected 0x80000084, but was 0x00000084
Looks like you set the second slave address for i2c4 bus. It indicates
'address 2' match event but current driver doesn't handle this event.
Can you share your i2c4 bus node setting in device tree?
&i2c4 {
status = "okay";
// BMC Debug Header
ipmb0@10 {
compatible = "ipmb-dev";
reg = <0x10>;
i2c-protocol;
};
};
Cheers,
Jae
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: i2c error for ME port
2019-11-25 23:02 ` Vijay Khemka
@ 2019-11-25 23:20 ` Jae Hyun Yoo
2019-11-25 23:37 ` Vijay Khemka
0 siblings, 1 reply; 8+ messages in thread
From: Jae Hyun Yoo @ 2019-11-25 23:20 UTC (permalink / raw)
To: Vijay Khemka, James Feist, jason.m.bills; +Cc: openbmc
> &i2c4 {
> status = "okay";
> // BMC Debug Header
> ipmb0@10 {
> compatible = "ipmb-dev";
> reg = <0x10>;
> i2c-protocol;
> };
> };
If it's for BMC-ME channel, you should add 'multi-master;' to enable H/W
arbitration. Also, you should set the slave address like below after
including '#include <dt-bindings/i2c/i2c.h>' in dts file.
reg = <(0x10 | I2C_OWN_SLAVE_ADDRESS)>;
Cheers,
Jae
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: i2c error for ME port
2019-11-25 23:20 ` Jae Hyun Yoo
@ 2019-11-25 23:37 ` Vijay Khemka
2019-11-25 23:39 ` Jae Hyun Yoo
0 siblings, 1 reply; 8+ messages in thread
From: Vijay Khemka @ 2019-11-25 23:37 UTC (permalink / raw)
To: Jae Hyun Yoo, James Feist, jason.m.bills; +Cc: openbmc
On 11/25/19, 3:21 PM, "Jae Hyun Yoo" <jae.hyun.yoo@linux.intel.com> wrote:
> &i2c4 {
> status = "okay";
> // BMC Debug Header
> ipmb0@10 {
> compatible = "ipmb-dev";
> reg = <0x10>;
> i2c-protocol;
> };
> };
If it's for BMC-ME channel, you should add 'multi-master;' to enable H/W
arbitration. Also, you should set the slave address like below after
including '#include <dt-bindings/i2c/i2c.h>' in dts file.
reg = <(0x10 | I2C_OWN_SLAVE_ADDRESS)>;
I changed to this
&i2c4 {
status = "okay";
multi-master;
// BMC Debug Header
ipmb0@10 {
compatible = "ipmb-dev";
reg = <0x40000010>;
i2c-protocol;
};
};
But no improvement. In fact sometimes I am unable to communicate with ME via i2c.
Cheers,
Jae
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: i2c error for ME port
2019-11-25 23:37 ` Vijay Khemka
@ 2019-11-25 23:39 ` Jae Hyun Yoo
2019-11-25 23:54 ` Vijay Khemka
0 siblings, 1 reply; 8+ messages in thread
From: Jae Hyun Yoo @ 2019-11-25 23:39 UTC (permalink / raw)
To: Vijay Khemka, James Feist, jason.m.bills; +Cc: openbmc
On 11/25/2019 3:37 PM, Vijay Khemka wrote:
>
>
> On 11/25/19, 3:21 PM, "Jae Hyun Yoo" <jae.hyun.yoo@linux.intel.com> wrote:
>
> > &i2c4 {
> > status = "okay";
> > // BMC Debug Header
> > ipmb0@10 {
> > compatible = "ipmb-dev";
> > reg = <0x10>;
> > i2c-protocol;
> > };
> > };
>
> If it's for BMC-ME channel, you should add 'multi-master;' to enable H/W
> arbitration. Also, you should set the slave address like below after
> including '#include <dt-bindings/i2c/i2c.h>' in dts file.
>
> reg = <(0x10 | I2C_OWN_SLAVE_ADDRESS)>;
>
> I changed to this
> &i2c4 {
> status = "okay";
> multi-master;
> // BMC Debug Header
> ipmb0@10 {
> compatible = "ipmb-dev";
What happens if you use "slave-mqueue" instead? Are you modifying IPMB
channel support using the ipmb kernel driver?
> reg = <0x40000010>;
> i2c-protocol;
> };
> };
> But no improvement. In fact sometimes I am unable to communicate with ME via i2c.
> Cheers,
>
> Jae
>
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: i2c error for ME port
2019-11-25 23:39 ` Jae Hyun Yoo
@ 2019-11-25 23:54 ` Vijay Khemka
0 siblings, 0 replies; 8+ messages in thread
From: Vijay Khemka @ 2019-11-25 23:54 UTC (permalink / raw)
To: Jae Hyun Yoo, James Feist, jason.m.bills; +Cc: openbmc
On 11/25/19, 3:40 PM, "Jae Hyun Yoo" <jae.hyun.yoo@linux.intel.com> wrote:
On 11/25/2019 3:37 PM, Vijay Khemka wrote:
>
>
> On 11/25/19, 3:21 PM, "Jae Hyun Yoo" <jae.hyun.yoo@linux.intel.com> wrote:
>
> > &i2c4 {
> > status = "okay";
> > // BMC Debug Header
> > ipmb0@10 {
> > compatible = "ipmb-dev";
> > reg = <0x10>;
> > i2c-protocol;
> > };
> > };
>
> If it's for BMC-ME channel, you should add 'multi-master;' to enable H/W
> arbitration. Also, you should set the slave address like below after
> including '#include <dt-bindings/i2c/i2c.h>' in dts file.
>
> reg = <(0x10 | I2C_OWN_SLAVE_ADDRESS)>;
>
> I changed to this
> &i2c4 {
> status = "okay";
> multi-master;
> // BMC Debug Header
> ipmb0@10 {
> compatible = "ipmb-dev";
What happens if you use "slave-mqueue" instead? Are you modifying IPMB
channel support using the ipmb kernel driver?
No, I am just using this IPMB kernel driver as receiving and sending ipmb packets.
All channel support is in ipmbbridge application only.
Let me switch back to mqueue slave driver and see if problem stays.
> reg = <0x40000010>;
> i2c-protocol;
> };
> };
> But no improvement. In fact sometimes I am unable to communicate with ME via i2c.
> Cheers,
>
> Jae
>
>
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2019-11-25 23:54 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-25 19:39 i2c error for ME port Vijay Khemka
2019-11-25 19:41 ` James Feist
2019-11-25 20:20 ` Jae Hyun Yoo
2019-11-25 23:02 ` Vijay Khemka
2019-11-25 23:20 ` Jae Hyun Yoo
2019-11-25 23:37 ` Vijay Khemka
2019-11-25 23:39 ` Jae Hyun Yoo
2019-11-25 23:54 ` Vijay Khemka
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.