From: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
To: qianlihu <wangzhiqiang8906@gmail.com>, openbmc@lists.ozlabs.org
Subject: Re: [HELP] ipmi-kcs didn't work
Date: Wed, 14 Nov 2018 09:17:53 -0800 [thread overview]
Message-ID: <3022407b-fa4e-9e80-2044-69dbf4f03586@linux.intel.com> (raw)
In-Reply-To: <CAHkHK08zcycaqmg_Pkq=Oe+8xC8TBYsCoBGLA0CCwH0qvwicWg@mail.gmail.com>
Hi,
On 11/14/2018 2:38 AM, qianlihu wrote:
> Hi,
>
> I add ipmi kcs node,but it didn't work
>
> here is the patch for dts.
>
> lpc_bmc: lpc-bmc@0 {
> - compatible = "aspeed,ast2500-lpc-bmc";
> + compatible = "aspeed,ast2500-lpc-bmc", "simple-mfd", "syscon";
> +
> reg = <0x0 0x80>;
> + reg-io-width = <4>;
> +
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0x0 0x0 0x80>;
> +
> + kcs3: kcs3@0 {
> + compatible = "aspeed,ast2500-kcs-bmc";
> + reg = <0x0 0x80>;
> + interrupts = <8>;
> + kcs_chan = <3>;
> + kcs_addr = <0xca2>;
Probably, you should add a clock setting for KCS H/W block into here.
clocks = <&syscon ASPEED_CLK_GATE_LCLK>;
Cheers,
Jae
> + status = "disabled";
> +
> + };
> };
>
> +&kcs3 {
> + status = "okay";
> +};
>
>
> The device node /dev/ipmi-kcs3 is created.
>
>
> root@sanjose:/tmp# ./kcsbridged --vv --d /dev/ipmi-kcs3
> Debug logging
> Starting
> Registering dbus methods/signals
> Requesting dbus name: org.openbmc.HostIpmi
> Getting dbus file descriptors
> Opening /dev/ipmi-kcs3
> Creating timer fd
> Entering polling loop
> Processed 1 dbus events
> Processed 1 dbus events
> Processed 1 dbus events
> Processed 1 dbus events
> Processed 1 dbus events
> Processed 1 dbus events
> Processed 1 dbus events
>
> but there is nothing output.
>
next prev parent reply other threads:[~2018-11-14 17:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 10:38 [HELP] ipmi-kcs didn't work qianlihu
2018-11-14 17:17 ` Jae Hyun Yoo [this message]
2018-11-15 1:49 ` qianlihu
2018-11-15 19:30 ` Jae Hyun Yoo
2018-11-16 10:27 ` qianlihu
2018-11-29 18:42 ` Vijay Khemka
2018-11-29 18:57 ` Jae Hyun Yoo
2018-11-30 3:00 ` Samuel Jiang
2018-11-30 15:31 ` Jae Hyun Yoo
2018-11-30 18:57 ` Vijay Khemka
2018-11-30 19:29 ` Jae Hyun Yoo
2018-11-30 22:39 ` Vijay Khemka
2018-11-30 23:04 ` Jae Hyun Yoo
2018-12-01 14:09 ` Samuel Jiang
2018-12-01 14:29 ` Samuel Jiang
2018-12-03 1:55 ` Samuel Jiang
2018-12-03 15:54 ` Jae Hyun Yoo
2018-12-03 19:37 ` Vijay Khemka
2018-12-03 20:16 ` Jae Hyun Yoo
2018-12-04 6:18 ` Ryan Chen
2018-12-04 15:44 ` Jae Hyun Yoo
2018-12-04 23:59 ` Vijay Khemka
2018-12-05 1:04 ` Ryan Chen
2018-12-05 14:54 ` Jae Hyun Yoo
2018-12-05 14:51 ` Jae Hyun Yoo
2018-12-05 6:45 ` Samuel Jiang
2018-12-05 8:43 ` Ryan Chen
2018-12-05 15:01 ` Jae Hyun Yoo
2018-12-06 8:53 ` Samuel Jiang
2018-12-04 2:18 ` Vijay Khemka
2018-12-03 12:52 ` qianlihu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3022407b-fa4e-9e80-2044-69dbf4f03586@linux.intel.com \
--to=jae.hyun.yoo@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=wangzhiqiang8906@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.