From: Andrew Jeffery <andrew@aj.id.au>
To: Eugene.Cho@dell.com, cyrilbur@gmail.com
Cc: openbmc@lists.ozlabs.org
Subject: Re: common bmc mailbox driver
Date: Fri, 11 May 2018 10:29:20 +0930 [thread overview]
Message-ID: <1526000360.3946551.1368145784.74E52A28@webmail.messagingengine.com> (raw)
In-Reply-To: <28825ffd2af2405eacbb48f1388992f8@AUSX13MPC105.AMER.DELL.COM>
Hi Eugene,
On Thu, 10 May 2018, at 22:34, Eugene.Cho@dell.com wrote:
> Hey Cyril,
> I was recently following your upstream submission attempt for the
> aspeed mbox/mailbox, was wondering if there was been any progress since?
FYI Cyril's moved on from IBM and OpenBMC, and so may have lost some motivation here.
>
> Reason I ask - is Nuvoton also has a "mailbox" for bmc<->host
> communication, which does the same thing (shared memory + interrupts
> both ways), and was wondering if we could just have 1 driver for both,
> instead 2 separate drivers.
>
> Glancing at the aspeed driver, only key difference I see is the setting
> and handling the interrupt. Thoughts on this?
(Somewhat unfortunately) the ASPEED mailbox driver isn't upstream yet due to push-back from the upstream mailbox subsystem maintainer*. Similar to the misc driver it sounds like we should work together to get things moving.
* It turns out the mailbox subsystem as it stands doesn't fit our needs - it's written from the perspective of the host kernel communicating with some firmware black box on the other side of the mailbox, rather than the kernel of interest *being* the black box.
Andrew
next prev parent reply other threads:[~2018-05-11 0:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 13:04 common bmc mailbox driver Eugene.Cho
2018-05-11 0:59 ` Andrew Jeffery [this message]
2018-05-22 10:37 ` Cyril Bur
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=1526000360.3946551.1368145784.74E52A28@webmail.messagingengine.com \
--to=andrew@aj.id.au \
--cc=Eugene.Cho@dell.com \
--cc=cyrilbur@gmail.com \
--cc=openbmc@lists.ozlabs.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 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.