public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: YC Chen <yc_chen@aspeedtech•com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>,
	"dri-devel@lists•freedesktop.org"
	<dri-devel@lists•freedesktop.org>
Cc: "airlied@redhat•com" <airlied@redhat•com>,
	"eich@suse•come" <eich@suse•come>,
	"linuxppc-dev@ozlabs•org" <linuxppc-dev@ozlabs•org>,
	"YC Chen" <yc_chen@aspeedtech•com>
Subject: RE: [PATCH 01/12] drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS
Date: Fri, 24 Feb 2017 07:04:56 +0000	[thread overview]
Message-ID: <a22be99daa224f05bccaffe7a879096d@TWMBX01.aspeed.com> (raw)
In-Reply-To: <20170223225357.9572-1-benh@kernel.crashing.org>

Tested-by: Y.C. Chen <yc_chen@aspeedtech•com>

-----Original Message-----
From: Benjamin Herrenschmidt [mailto:benh@kernel•crashing.org]=20
Sent: Friday, February 24, 2017 6:54 AM
To: dri-devel@lists•freedesktop.org
Cc: YC Chen <yc_chen@aspeedtech•com>; airlied@redhat•com; eich@suse•come; l=
inuxppc-dev@ozlabs•org
Subject: [PATCH 01/12] drm/ast: Fix AST2400 POST failure without BMC FW or =
VBIOS

From: "Y.C. Chen" <yc_chen@aspeedtech•com>

The current POST code for the AST2300/2400 family doesn't work properly if =
the chip hasn't been initialized previously by either the BMC own FW or the=
 VBIOS. This fixes it.

Signed-off-by: Y.C. Chen <yc_chen@aspeedtech•com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel•crashing.org>

      parent reply	other threads:[~2017-02-24  7:25 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 22:53 [PATCH 01/12] drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS Benjamin Herrenschmidt
2017-02-23 22:53 ` [PATCH 02/12] drm/ast: Handle configuration without P2A bridge Benjamin Herrenschmidt
2017-02-24  2:21   ` Joel Stanley
2017-02-24  2:26     ` Benjamin Herrenschmidt
2017-02-24  2:32     ` Benjamin Herrenschmidt
2017-02-24  2:41     ` [PATCH v5 2/12] " Benjamin Herrenschmidt
2017-02-24  2:43       ` Joel Stanley
2017-02-24  7:06   ` [PATCH 02/12] " YC Chen
2017-02-23 22:53 ` [PATCH 03/12] drm/ast: const'ify mode setting tables Benjamin Herrenschmidt
2017-02-24  2:21   ` Joel Stanley
2017-02-23 22:53 ` [PATCH 04/12] drm/ast: Remove spurrious include Benjamin Herrenschmidt
2017-02-24  2:24   ` Joel Stanley
2017-02-23 22:53 ` [PATCH 05/12] drm/ast: Fix calculation of MCLK Benjamin Herrenschmidt
2017-02-24  2:24   ` Joel Stanley
2017-02-24  2:38     ` Benjamin Herrenschmidt
2017-02-24  3:12       ` Joel Stanley
2017-02-24  7:06   ` YC Chen
2017-02-23 22:53 ` [PATCH 06/12] drm/ast: Base support for AST2500 Benjamin Herrenschmidt
2017-02-24  2:22   ` Joel Stanley
2017-02-23 22:53 ` [PATCH 07/12] drm/ast: Fixed vram size incorrect issue on POWER Benjamin Herrenschmidt
2017-02-24  2:24   ` Joel Stanley
2017-02-24  7:07   ` YC Chen
2017-02-23 22:53 ` [PATCH 08/12] drm/ast: Factor mmc_test code in POST code Benjamin Herrenschmidt
2017-02-24  2:21   ` Joel Stanley
2017-02-24  7:07   ` YC Chen
2017-02-23 22:53 ` [PATCH 09/12] drm/ast: Rename ast_init_dram_2300 to ast_post_chip_2300 Benjamin Herrenschmidt
2017-02-24  2:21   ` Joel Stanley
2017-02-24  7:08   ` YC Chen
2017-02-23 22:53 ` [PATCH 10/12] drm/ast: POST code for the new AST2500 Benjamin Herrenschmidt
2017-02-24  2:21   ` Joel Stanley
2017-02-23 22:53 ` [PATCH 11/12] drm/ast: Fix test for VGA enabled Benjamin Herrenschmidt
2017-02-23 23:24   ` Benjamin Herrenschmidt
2017-02-24  7:09   ` YC Chen
2017-02-23 22:53 ` [PATCH 12/12] drm/ast: Call open_key before enable_mmio in POST code Benjamin Herrenschmidt
2017-02-24  2:21   ` Joel Stanley
2017-02-24  7:09   ` YC Chen
2017-02-23 23:07 ` [PATCH 01/12] drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS Benjamin Herrenschmidt
2017-02-24  2:23 ` Joel Stanley
2017-02-24  7:04 ` YC Chen [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=a22be99daa224f05bccaffe7a879096d@TWMBX01.aspeed.com \
    --to=yc_chen@aspeedtech$(echo .)com \
    --cc=airlied@redhat$(echo .)com \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=dri-devel@lists$(echo .)freedesktop.org \
    --cc=eich@suse$(echo .)come \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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