From: Jammy Huang <jammy_huang@aspeedtech.com>
To: <airlied@redhat.com>, <tzimmermann@suse.de>, <airlied@gmail.com>,
<daniel@ffwll.ch>
Cc: <dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<giantl@nvidia.com>
Subject: Re: [PATCH] drm/ast: Fix ARM compatibility
Date: Fri, 7 Apr 2023 10:09:24 +0800 [thread overview]
Message-ID: <d72b0fd9-844e-a422-45b6-261d73dbad18@aspeedtech.com> (raw)
In-Reply-To: <20230302021905.2777-1-jammy_huang@aspeedtech.com>
Hi Thomas,
Could you help review this patch??
We met some problem on nvidia's ARM platfrom and need this patch to fix it.
On 2023/3/2 上午 10:19, Jammy Huang wrote:
> ARM architecture only has 'memory', so all devices are accessed by MMIO.
>
> Signed-off-by: Jammy Huang <jammy_huang@aspeedtech.com>
> ---
> drivers/gpu/drm/ast/ast_main.c | 17 +----------------
> 1 file changed, 1 insertion(+), 16 deletions(-)
>
> diff --git a/drivers/gpu/drm/ast/ast_main.c b/drivers/gpu/drm/ast/ast_main.c
> index 794ffd4a29c5..f86d01e9f024 100644
> --- a/drivers/gpu/drm/ast/ast_main.c
> +++ b/drivers/gpu/drm/ast/ast_main.c
> @@ -424,22 +424,7 @@ struct ast_device *ast_device_create(const struct drm_driver *drv,
> if (!ast->regs)
> return ERR_PTR(-EIO);
>
> - /*
> - * If we don't have IO space at all, use MMIO now and
> - * assume the chip has MMIO enabled by default (rev 0x20
> - * and higher).
> - */
> - if (!(pci_resource_flags(pdev, 2) & IORESOURCE_IO)) {
> - drm_info(dev, "platform has no IO space, trying MMIO\n");
> - ast->ioregs = ast->regs + AST_IO_MM_OFFSET;
> - }
> -
> - /* "map" IO regs if the above hasn't done so already */
> - if (!ast->ioregs) {
> - ast->ioregs = pcim_iomap(pdev, 2, 0);
> - if (!ast->ioregs)
> - return ERR_PTR(-EIO);
> - }
> + ast->ioregs = ast->regs + AST_IO_MM_OFFSET;
>
> ast_detect_chip(dev, &need_post);
>
>
> base-commit: 254986e324add8a30d0019c6da59f81adc8b565f
--
Best Regards
Jammy
next prev parent reply other threads:[~2023-04-07 2:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 2:19 Jammy Huang
2023-04-07 2:09 ` Jammy Huang [this message]
2023-04-17 11:51 ` Thomas Zimmermann
[not found] ` <c5fb047b-ed55-be1f-56ae-3b21b1d1dd29@aspeedtech.com>
2023-04-18 7:24 ` Thomas Zimmermann
2023-04-18 7:55 ` Jammy Huang
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=d72b0fd9-844e-a422-45b6-261d73dbad18@aspeedtech.com \
--to=jammy_huang@aspeedtech.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=giantl@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®