From: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
To: Zev Weiss <zev@bewilderbeest.net>
Cc: Joel Stanley <joel@jms.id.au>,
Jae Hyun Yoo <jae.hyun.yoo@intel.com>,
Rob Herring <robh+dt@kernel.org>, Corey Minyard <minyard@acm.org>,
Andrew Jeffery <andrew@aj.id.au>, Cedric Le Goater <clg@kaod.org>,
Haiyue Wang <haiyue.wang@linux.intel.com>,
devicetree <devicetree@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-aspeed <linux-aspeed@lists.ozlabs.org>,
openipmi-developer@lists.sourceforge.net
Subject: Re: [PATCH -next 0/4] Add LCLK control into Aspeed LPC sub drivers
Date: Tue, 2 Nov 2021 17:54:30 -0700 [thread overview]
Message-ID: <63678f47-8b4a-1385-a755-bc7c2316ca0d@linux.intel.com> (raw)
In-Reply-To: <YYHYMKDD7hz15ceR@hatter.bewilderbeest.net>
On 11/2/2021 5:30 PM, Zev Weiss wrote:
> On Tue, Nov 02, 2021 at 05:17:30PM PDT, Jae Hyun Yoo wrote:
>> Hi Zev,
>>
>> On 11/2/2021 5:04 PM, Zev Weiss wrote:
>>> On Mon, Nov 01, 2021 at 04:36:38PM PDT, Joel Stanley wrote:
>>>> On Mon, 1 Nov 2021 at 23:18, <jae.hyun.yoo@intel.com> wrote:
>>>>>
>>>>> From: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
>>>>>
>>>>> Hello all,
>>>>>
>>>>> This series is for appliying below fix to all Aspped LPC sub drivers.
>>>>> https://lore.kernel.org/all/20201208091748.1920-1-wangzhiqiang.bj@bytedance.com/
>>>>>
>>>>>
>>>>>
>>>>> An LPC sub driver can be enabled without using the lpc-ctrl driver
>>>>> or it
>>>>> can be registered ahead of lpc-ctrl depends on each system
>>>>> configuration and
>>>>> this difference introduces that LPC can be enabled without heart
>>>>> beating of
>>>>> LCLK so it causes improper handling on host interrupts when the
>>>>> host sends
>>>>> interrupts in that time frame. Then kernel eventually forcibly
>>>>> disables the
>>>>> interrupt with dumping stack and printing a 'nobody cared this irq'
>>>>> message
>>>>> out.
>>>>>
>>>>> To prevent this issue, all LPC sub drivers should enable LCLK
>>>>> individually
>>>>> so this patch adds clock control logic into the remaining Aspeed
>>>>> LPC sub
>>>>> drivers.
>>>>
>>>> Thanks for sending this out!
>>>>
>>>> This will resolve a few of the issues we have in the issue tracker:
>>>>
>>>> https://github.com/openbmc/linux/issues/210
>>>> https://github.com/openbmc/linux/issues/130
>>>>
>>>> The patches look good to me. I think you've just missed Corey's PR for
>>>> v5.16, but I will stick them in the openbmc tree once they've had a
>>>> review.
>>>>
>>>
>>> Hi Jae,
>>>
>>> I tried this series out on the same in-progress OpenBMC port from
>>> issue number 210 linked above and am still seeing problems (dmesg
>>> pasted below).
>>>
>>> I cherry-picked commit f9241fe8b9652 ("ARM: dts: aspeed: Add uart
>>> routing to device tree") from linux-next to allow the first patch to
>>> apply cleanly; is there anything else I might be missing that'd be
>>> needed to test the series properly?
>>
>> Looks like below dmesg shows an error from 'aspeed_lpc_snoop_probe'
>> which this series doesn't touch. Do you have below fix in your code
>> tree?
>>
>> https://lore.kernel.org/all/20201208091748.1920-1-wangzhiqiang.bj@bytedance.com/
>>
>>
>> Thanks,
>> Jae
>>
>
> Yes, I've got that patch (commit 3f94cf1558), and the accompanying dts
> update to add the clocks property to the lpc-snoop device (commit
> d050d049f8).
>
> However, while there is an aspeed_lpc_snoop_probe() backtrace there,
> note that there's *also* one from aspeed_kcs_probe() further on
> (starting at timestamp 3.263306).
>
>
> Zev
>
Can you please test additional changes below?
Thanks,
Jae
diff --git a/drivers/char/ipmi/kcs_bmc_aspeed.c
b/drivers/char/ipmi/kcs_bmc_aspeed.c
index 00706472cc4d..af03aea0f3ce 100644
--- a/drivers/char/ipmi/kcs_bmc_aspeed.c
+++ b/drivers/char/ipmi/kcs_bmc_aspeed.c
@@ -644,6 +644,17 @@ static int aspeed_kcs_probe(struct platform_device
*pdev)
if (rc)
goto err;
+ platform_set_drvdata(pdev, priv);
+
+ aspeed_kcs_irq_mask_update(kcs_bmc, (KCS_BMC_EVENT_TYPE_IBF |
KCS_BMC_EVENT_TYPE_OBE), 0);
+ aspeed_kcs_enable_channel(kcs_bmc, true);
+
+ rc = kcs_bmc_add_device(&priv->kcs_bmc);
+ if (rc) {
+ dev_warn(&pdev->dev, "Failed to register channel %d:
%d\n", kcs_bmc->channel, rc);
+ goto err;
+ }
+
/* Host to BMC IRQ */
rc = aspeed_kcs_config_downstream_irq(kcs_bmc, pdev);
if (rc)
@@ -658,17 +669,6 @@ static int aspeed_kcs_probe(struct platform_device
*pdev)
priv->upstream_irq.mode = aspeed_kcs_irq_none;
}
- platform_set_drvdata(pdev, priv);
-
- aspeed_kcs_irq_mask_update(kcs_bmc, (KCS_BMC_EVENT_TYPE_IBF |
KCS_BMC_EVENT_TYPE_OBE), 0);
- aspeed_kcs_enable_channel(kcs_bmc, true);
-
- rc = kcs_bmc_add_device(&priv->kcs_bmc);
- if (rc) {
- dev_warn(&pdev->dev, "Failed to register channel %d:
%d\n", kcs_bmc->channel, rc);
- goto err;
- }
-
dev_info(&pdev->dev, "Initialised channel %d at 0x%x\n",
kcs_bmc->channel, addrs[0]);
diff --git a/drivers/soc/aspeed/aspeed-lpc-snoop.c
b/drivers/soc/aspeed/aspeed-lpc-snoop.c
index eceeaf8dfbeb..044c8f6665b7 100644
--- a/drivers/soc/aspeed/aspeed-lpc-snoop.c
+++ b/drivers/soc/aspeed/aspeed-lpc-snoop.c
@@ -306,10 +306,6 @@ static int aspeed_lpc_snoop_probe(struct
platform_device *pdev)
return rc;
}
- rc = aspeed_lpc_snoop_config_irq(lpc_snoop, pdev);
- if (rc)
- goto err;
-
rc = aspeed_lpc_enable_snoop(lpc_snoop, dev, 0, port);
if (rc)
goto err;
@@ -324,6 +320,10 @@ static int aspeed_lpc_snoop_probe(struct
platform_device *pdev)
}
}
+ rc = aspeed_lpc_snoop_config_irq(lpc_snoop, pdev);
+ if (rc)
+ goto err;
+
return 0;
err:
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-11-03 0:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 23:37 [PATCH -next 0/4] Add LCLK control into Aspeed LPC sub drivers jae.hyun.yoo
2021-11-01 23:36 ` Joel Stanley
2021-11-02 12:22 ` Corey Minyard
2021-11-02 16:38 ` Jae Hyun Yoo
2021-11-03 0:04 ` Zev Weiss
2021-11-03 0:17 ` Jae Hyun Yoo
2021-11-03 0:30 ` Zev Weiss
2021-11-03 0:54 ` Jae Hyun Yoo [this message]
2021-11-03 1:09 ` Zev Weiss
2021-11-03 15:56 ` Jae Hyun Yoo
2021-11-04 1:48 ` Zev Weiss
2021-11-04 16:09 ` Jae Hyun Yoo
2021-11-01 23:37 ` [PATCH -next 1/4] ARM: dts: aspeed: add LCLK setting into LPC IBT node jae.hyun.yoo
2021-11-01 23:33 ` Joel Stanley
2021-11-01 23:48 ` Jae Hyun Yoo
2021-11-01 23:52 ` Joel Stanley
2021-11-01 23:59 ` Jae Hyun Yoo
2021-11-02 22:21 ` Andrew Jeffery
2021-11-01 23:37 ` [PATCH -next 2/4] ipmi: bt: add clock control logic jae.hyun.yoo
2021-11-01 23:32 ` Joel Stanley
2021-11-02 9:35 ` Cédric Le Goater
2021-11-02 16:36 ` Jae Hyun Yoo
2021-11-02 22:14 ` Andrew Jeffery
2021-11-01 23:37 ` [PATCH -next 3/4] ARM: dts: aspeed: add LCLK setting into LPC KCS nodes jae.hyun.yoo
2021-11-01 23:34 ` Joel Stanley
2021-11-02 22:22 ` Andrew Jeffery
2021-11-03 16:15 ` Jae Hyun Yoo
2021-11-01 23:37 ` [PATCH -next 4/4] ipmi: kcs_bmc_aspeed: add clock control logic jae.hyun.yoo
2021-11-01 23:33 ` Joel Stanley
2021-11-02 3:15 ` ChiaWei Wang
2021-11-02 3:28 ` Joel Stanley
2021-11-02 16:35 ` Jae Hyun Yoo
2021-11-03 1:55 ` ChiaWei Wang
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=63678f47-8b4a-1385-a755-bc7c2316ca0d@linux.intel.com \
--to=jae.hyun.yoo@linux.intel.com \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=devicetree@vger.kernel.org \
--cc=haiyue.wang@linux.intel.com \
--cc=jae.hyun.yoo@intel.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=robh+dt@kernel.org \
--cc=zev@bewilderbeest.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).