From: Graeme Gregory <quic_ggregory@quicinc.com>
To: Quan Nguyen <quan@os.amperecomputing.com>
Cc: <devicetree@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
<linux-aspeed@lists.ozlabs.org>, Corey Minyard <minyard@acm.org>,
Andrew Jeffery <andrew@aj.id.au>, <openbmc@lists.ozlabs.org>,
<thang@os.amperecomputing.com>,
Phong Vo <phong@os.amperecomputing.com>,
<linux-kernel@vger.kernel.org>, Wolfram Sang <wsa@kernel.org>,
Brendan Higgins <brendan.higgins@linux.dev>,
Rob Herring <robh+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
<openipmi-developer@lists.sourceforge.net>,
Open Source Submission <patches@amperecomputing.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-i2c@vger.kernel.org>
Subject: Re: [PATCH v10 1/3] ipmi: ssif_bmc: Add SSIF BMC driver
Date: Fri, 14 Oct 2022 14:05:17 +0100 [thread overview]
Message-ID: <20221014130517.y4mdinylnwfrg6u2@ggregory-linuxws> (raw)
In-Reply-To: <72c8a5bc-830d-25a9-0528-5d428dd9f163@quicinc.com>
On Mon, Oct 10, 2022 at 12:08:24PM +0100, Graeme Gregory wrote:
>
> On 10/10/2022 02:28, Quan Nguyen wrote:
> >
> >
> > On 07/10/2022 20:26, Graeme Gregory wrote:
> > >
> > > On 04/10/2022 10:31, Quan Nguyen wrote:
> > > > The SMBus system interface (SSIF) IPMI BMC driver can be used to
> > > > perform
> > > > in-band IPMI communication with their host in management (BMC) side.
> > > >
> > > > Thanks Dan for the copy_from_user() fix in the link below.
> > > >
> > > > Link: https://lore.kernel.org/linux-arm-kernel/20220310114119.13736-4-quan@os.amperecomputing.com/
> > > > Signed-off-by: Quan Nguyen <quan@os.amperecomputing.com>
> > >
> > > I have been testing this on our hardware and I don't seem to be able
> > > to get this driver working. I was using an older version.
> > >
> > > I have hacked ssifbridged to deal with the change in len from u8 to
> > > unsigned int.
> > >
> > > It works as long as I only ever send SSIF commands, any attempt to
> > > read a response crashes the state machine and the driver never
> > > recovers. No further SSIF comms is possible! (slave doesnt even ACK
> > > writes).
> > >
> > > A couple of comments below on possible state machine errors.
> > >
> > > Its possible I am doing something wrong!
> > >
> >
> > Thanks Graeme for the test and the comments.
> >
> > What's your testing hardware?
> >
> > This was tested with Aspeed ast2500 and ast2600 with the patch series
> > [1] below applied.
> >
> > If you use the same hw, could you pick the series and see if any thing
> > improve ?
> >
> > [1] https://lore.kernel.org/all/20210616031046.2317-1-quan@os.amperecomputing.com/
> >
> Thanks, that patch series does stop the state machine crashing.
>
> I am testing on AST2600EVB with A1 rev, but we also have our own DC-SCM with
> A3 chip.
>
> Responses are still not working for me, but I think that may be an error in
> my ssifbridged hacks.
>
> Oct 10 10:54:55 qcom-evb-proto-ccf37d18ea0c ssifbridged[335]: Read ssif
> request message with len=13 netfn=44 lun=0 cmd=2
>
> Oct 10 10:54:55 qcom-evb-proto-ccf37d18ea0c ipmid[312]: BootCode:
> 000000000000000000
>
> Oct 10 10:54:55 qcom-evb-proto-ccf37d18ea0c ssifbridged[335]: Send ssif
> respond message with len=4 netfn=45 lun=0 cmd=2 cc=0
>
> Oct 10 10:54:55 qcom-evb-proto-ccf37d18ea0c kernel: ipmi-ssif-host 0-0010:
> Warn: on_read_requested_event unexpected READ REQUESTED in state=SSIF_READY
>
> Oct 10 10:54:55 qcom-evb-proto-ccf37d18ea0c kernel: ipmi-ssif-host 0-0010:
> Warn: on_stop_event unexpected SLAVE STOP in state=SSIF_ABORTING
>
Just to close the loop on this, I have now fully tested this driver on
our setup internally.
Final hitch turned out to be an aardvark not issuing STOP events between
reads/writes.
Thanks for the work.
Graeme
next prev parent reply other threads:[~2022-10-14 13:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 9:31 [PATCH v10 0/3] Add SSIF BMC driver Quan Nguyen
2022-10-04 9:31 ` [PATCH v10 1/3] ipmi: ssif_bmc: " Quan Nguyen
2022-10-07 13:26 ` Graeme Gregory
2022-10-10 1:28 ` Quan Nguyen
2022-10-10 11:08 ` Graeme Gregory
2022-10-14 13:05 ` Graeme Gregory [this message]
2022-10-15 3:24 ` Quan Nguyen
2022-10-04 9:31 ` [PATCH v10 2/3] bindings: ipmi: Add binding for " Quan Nguyen
2022-10-04 9:31 ` [PATCH v10 3/3] i2c: aspeed: Assert NAK when slave is busy Quan Nguyen
2022-10-05 19:06 ` Wolfram Sang
2022-10-06 6:44 ` Quan Nguyen
2022-10-06 15:33 ` Wolfram Sang
2022-10-05 23:53 ` [PATCH v10 0/3] Add SSIF BMC driver Corey Minyard
2022-10-06 6:42 ` Quan Nguyen
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=20221014130517.y4mdinylnwfrg6u2@ggregory-linuxws \
--to=quic_ggregory@quicinc.com \
--cc=andrew@aj.id.au \
--cc=brendan.higgins@linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openbmc@lists.ozlabs.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=patches@amperecomputing.com \
--cc=phong@os.amperecomputing.com \
--cc=quan@os.amperecomputing.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=thang@os.amperecomputing.com \
--cc=wsa@kernel.org \
/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).