From: Andrew Jeffery <andrew@aj.id.au>
To: Kun Yi <kunyi@google.com>
Cc: Joel Stanley <joel@jms.id.au>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH u-boot 4/4] aspeed: Disable unnecessary features
Date: Tue, 12 Feb 2019 10:02:09 +1030 [thread overview]
Message-ID: <1549927929.1686694.1655933984.5318EBC3@webmail.messagingengine.com> (raw)
In-Reply-To: <CAGMNF6VM9SDm1c0hFLBYwSdwPHdEjA=a5ikbhJk3GFrYFwKNRQ@mail.gmail.com>
Hi Kun,
It's probably safe to reply to this now :)
On Sat, 15 Sep 2018, at 09:52, Kun Yi wrote:
> Thanks for sending the patch Andrew. I think it's a viable solution since
> linux upstream didn't like the idea of misc controls.
>
> My feature request would be that we add config options for selectively
> turning these features on/off. For example, we actually use LPC2AHB and
> PCIe2AHB downstream for host-BMC mailbox typed transfers.. It would be nice
> if we could take this patch and define the flags to enable what we needed.
We've included the patch via bitbake but I think wee should work to get it applied to
the u-boot repository. I think you're probably right - having some control over which
features are enabled or disabled would be nice. The way I see this working is that
the bitbake magic simply selects the desired configuration rather than applying the
patch.
Andrew
prev parent reply other threads:[~2019-02-11 23:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 14:58 [PATCH u-boot 0/4] Cleanups and disable unnecessary features Andrew Jeffery
2018-07-23 14:58 ` [PATCH u-boot 1/4] checkpatch: Fix unescaped brace warning Andrew Jeffery
2018-07-23 14:58 ` [PATCH u-boot 2/4] ast-g4: Fix typo in board_init() comment Andrew Jeffery
2018-07-23 14:58 ` [PATCH u-boot 3/4] arch-aspeed: Make AHBC and SDMC header guards unique Andrew Jeffery
2018-07-23 14:58 ` [PATCH u-boot 4/4] aspeed: Disable unnecessary features Andrew Jeffery
2018-09-14 23:22 ` Kun Yi
2019-02-11 23:32 ` Andrew Jeffery [this message]
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=1549927929.1686694.1655933984.5318EBC3@webmail.messagingengine.com \
--to=andrew@aj.id.au \
--cc=joel@jms.id.au \
--cc=kunyi@google.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.