From: Thomas Zimmermann <tzimmermann@suse.de>
To: Kuo-Hsiang Chou <kuohsiang_chou@aspeedtech.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Ryan Chen" <ryan_chen@aspeedtech.com>,
"airlied@linux.ie" <airlied@linux.ie>,
"清水修(o-shimizu)-台灣NEC" <o-shimizu@nec.com.tw>,
"Jenmin Yuan" <jenmin_yuan@aspeedtech.com>,
"airlied@redhat.com" <airlied@redhat.com>,
"Arc Sung" <arc_sung@aspeedtech.com>,
"Luke Chen" <luke_chen@aspeedtech.com>
Subject: Re: [PATCH] drm/ast: Atomic CR/SR reg R/W
Date: Fri, 3 Dec 2021 09:46:43 +0100 [thread overview]
Message-ID: <4a7ce84d-faef-4fb2-d36d-5cff2fba8ecf@suse.de> (raw)
In-Reply-To: <HK2PR06MB3300EB8A7BEB41907FB7FC5F8C6A9@HK2PR06MB3300.apcprd06.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 4748 bytes --]
Hi
Am 03.12.21 um 02:23 schrieb Kuo-Hsiang Chou:
>
>
> -----Original Message-----
> From: Kuo-Hsiang Chou
> Sent: Thursday, September 30, 2021 3:19 PM
> To: Thomas Zimmermann <tzimmermann@suse.de>; dri-devel@lists.freedesktop.org; linux-kernel@vger.kernel.org
> Subject: RE: [PATCH] drm/ast: Atomic CR/SR reg R/W
>
> Hi
>
> -----Original Message-----
> From: Thomas Zimmermann [mailto:tzimmermann@suse.de]
> Sent: Monday, September 20, 2021 4:17 PM
> To: Kuo-Hsiang Chou <kuohsiang_chou@aspeedtech.com>; dri-devel@lists.freedesktop.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] drm/ast: Atomic CR/SR reg R/W
>
> Hi
>
> Am 17.09.21 um 09:22 schrieb KuoHsiang Chou:
>> 1. Avoid IO-index racing
>> 2. IO-index racing happened on resolustion switching
>> and mouse moving at the same time
>> 3. System hung while IO-index racing occurred.
>
> I'd say that there's something else going one here. Mode setting and cursor movement should be protected against each other by DRM locking.
> Changing these low-level functions would not solve the issues. I'll try to reproduce the problem ASAP.
>
> Hi Thomas,
>
> Sorry to interrupt you again!
> May I understand the review's situation? Thanks!
Look, you really have to work with us during the review process. Don't
just expect us to tell you what to do.
I'm not going to merge this patch. As I said, I don't think it fixes the
problem. Mouse movement and resolution switching should not interfere
with each other. The DRM framework should guarantee that.
I cannot reproduce the issue, but there's most likely something else
happening here. How can the system switch resolution and change the
mouse at the same time?
Best regards
Thomas
>
> Hi Tomas,
> Good day!
> May I understand the review status, or is there anything I can do to improve it? Thanks!
>
> Best Regards,
> Kuo-Hsiang Chou
>
> Best Regards,
> Kuo-Hsiang Chou
>
> Best regards
> Thomas
>
>>
>> Signed-off-by: KuoHsiang Chou <kuohsiang_chou@aspeedtech.com>
>> ---
>> drivers/gpu/drm/ast/ast_main.c | 48 +++++++++++++++++++++++++---------
>> 1 file changed, 36 insertions(+), 12 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/ast/ast_main.c
>> b/drivers/gpu/drm/ast/ast_main.c index 79a361867..1d8fa70c5 100644
>> --- a/drivers/gpu/drm/ast/ast_main.c
>> +++ b/drivers/gpu/drm/ast/ast_main.c
>> @@ -41,28 +41,52 @@ void ast_set_index_reg_mask(struct ast_private *ast,
>> uint32_t base, uint8_t index,
>> uint8_t mask, uint8_t val)
>> {
>> - u8 tmp;
>> - ast_io_write8(ast, base, index);
>> - tmp = (ast_io_read8(ast, base + 1) & mask) | val;
>> - ast_set_index_reg(ast, base, index, tmp);
>> + uint16_t volatile usData;
>> + uint8_t volatile jData;
>> +
>> + do {
>> + ast_io_write8(ast, base, index);
>> + usData = ast_io_read16(ast, base);
>> + } while ((uint8_t)(usData) != index);
>> +
>> + jData = (uint8_t)(usData >> 8);
>> + jData &= mask;
>> + jData |= val;
>> + usData = ((uint16_t) jData << 8) | (uint16_t) index;
>> + ast_io_write16(ast, base, usData);
>> }
>>
>> uint8_t ast_get_index_reg(struct ast_private *ast,
>> uint32_t base, uint8_t index)
>> {
>> - uint8_t ret;
>> - ast_io_write8(ast, base, index);
>> - ret = ast_io_read8(ast, base + 1);
>> - return ret;
>> + uint16_t volatile usData;
>> + uint8_t volatile jData;
>> +
>> + do {
>> + ast_io_write8(ast, base, index);
>> + usData = ast_io_read16(ast, base);
>> + } while ((uint8_t)(usData) != index);
>> +
>> + jData = (uint8_t)(usData >> 8);
>> +
>> + return jData;
>> }
>>
>> uint8_t ast_get_index_reg_mask(struct ast_private *ast,
>> uint32_t base, uint8_t index, uint8_t mask)
>> {
>> - uint8_t ret;
>> - ast_io_write8(ast, base, index);
>> - ret = ast_io_read8(ast, base + 1) & mask;
>> - return ret;
>> + uint16_t volatile usData;
>> + uint8_t volatile jData;
>> +
>> + do {
>> + ast_io_write8(ast, base, index);
>> + usData = ast_io_read16(ast, base);
>> + } while ((uint8_t)(usData) != index);
>> +
>> + jData = (uint8_t)(usData >> 8);
>> + jData &= mask;
>> +
>> + return jData;
>> }
>>
>> static void ast_detect_config_mode(struct drm_device *dev, u32
>> *scu_rev)
>> --
>> 2.18.4
>>
>
> --
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Felix Imendörffer
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2021-12-03 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 7:22 KuoHsiang Chou
2021-09-20 8:17 ` Thomas Zimmermann
2021-09-30 7:19 ` Kuo-Hsiang Chou
2021-12-03 1:23 ` Kuo-Hsiang Chou
2021-12-03 8:46 ` Thomas Zimmermann [this message]
2021-12-06 1:38 ` Kuo-Hsiang Chou
2022-05-02 14:32 ` Thomas Zimmermann
2022-05-03 0:38 ` Kuo-Hsiang Chou
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=4a7ce84d-faef-4fb2-d36d-5cff2fba8ecf@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=arc_sung@aspeedtech.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jenmin_yuan@aspeedtech.com \
--cc=kuohsiang_chou@aspeedtech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke_chen@aspeedtech.com \
--cc=o-shimizu@nec.com.tw \
--cc=ryan_chen@aspeedtech.com \
/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®