Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp2821931pxb; Mon, 18 Oct 2021 02:36:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxvv2DO5gfJUD4Hs8j6nsctLUANkoj2e6AAYm510Gywnejyrej7IvkP490Qx98Cf1krWu5O X-Received: by 2002:a05:6402:35c5:: with SMTP id z5mr43177498edc.388.1634549792745; Mon, 18 Oct 2021 02:36:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634549792; cv=none; d=google.com; s=arc-20160816; b=YKEY01Xq/D69xohoaLEO4chYuF0h37oUkYq1Nlh6JWW+nENGwZPYjLMlRbn6ujC+eF SgGEcC+yLkREk3xqwFoa5R3uJweXoRSdD7iF+eREUEtd0GvHjBoUuU5mLThK1YEg7KTL NradcZxM4X2n7J/MMko928f6YJTFe+QQURcO3Pvx4cw8nvxhUQsT4ni/A9mtkVU5onpe gtAmfGxmujeWr/KTfP6CvT0Zq3rSlq4Y5TuXV2y1gPe9dLH02R0GV8bWKyFKNNErwE+P R2zXRgmrT7VeIt0iEdU5T8EGXeKHzObSxW6PkuVw7WK54oaNfe3Da1OlcT/synQTae5S jmAw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=dN3jaiYjLawK7nT0Eg1pV54bO8/lRqF1GlWMup9deJs=; b=N4Sv0YZnuWkFh4PWM63w5S1dSiLLG8m5juaUrSw4xxkci0oilmuf75xO6U2w1wv3Ya bCBfWRzF3VNaesTVN6K2vdi9cXVc8xgxLdEVzebwHwChIt2zgpYQxEhapgtbhBR4UFNW 3QtHoaFlsXyG2dtPBI7vuKpXURatZv7P/UNNk0pm608VgV4650SLs8cjV9rcS0pfENAe egf6LTGDiAkrT5ILFzd22Ma7j42Hheg6uP2qTY+hotPNMCGoCHFd47vZOfceBQ5oRu3I an2iIrB0/mxQ8W/Jli9tJIpC9rwaeccfakr96jvK+9raEP7adkv1OwhpZYSuH4Dctcrp WBAA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l4si18915410ejq.419.2021.10.18.02.36.09; Mon, 18 Oct 2021 02:36:32 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231408AbhJRJgU (ORCPT + 99 others); Mon, 18 Oct 2021 05:36:20 -0400 Received: from mx3.molgen.mpg.de ([141.14.17.11]:34619 "EHLO mx1.molgen.mpg.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S231305AbhJRJgU (ORCPT ); Mon, 18 Oct 2021 05:36:20 -0400 Received: from [192.168.0.2] (ip5f5aef76.dynamic.kabel-deutschland.de [95.90.239.118]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) (Authenticated sender: pmenzel) by mx.molgen.mpg.de (Postfix) with ESMTPSA id DC0C361E5FE33; Mon, 18 Oct 2021 11:34:06 +0200 (CEST) Subject: Re: [PATCH 4/6] media: aspeed: Support aspeed mode to reduce compressed data To: Jammy Huang Cc: eajames@linux.ibm.com, Mauro Carvalho Chehab , joel@jms.id.au, andrew@aj.id.au, linux-media@vger.kernel.org, openbmc@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org, "linux-aspeed@lists.ozlabs.org" , linux-kernel@vger.kernel.org References: <20211014034819.2283-1-jammy_huang@aspeedtech.com> <20211014034819.2283-5-jammy_huang@aspeedtech.com> <5675befe-48df-9f09-f30f-d407538ad070@aspeedtech.com> From: Paul Menzel Message-ID: <5466798e-32c1-81f5-3428-7bbfe31cdea7@molgen.mpg.de> Date: Mon, 18 Oct 2021 11:34:06 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: <5675befe-48df-9f09-f30f-d407538ad070@aspeedtech.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Jammy, Am 18.10.21 um 10:51 schrieb Jammy Huang: > On 2021/10/14 下午 02:47, Paul Menzel wrote: >> Am 14.10.21 um 05:48 schrieb Jammy Huang: >>> aspeed support differential jpeg format which only compress the parts >> support*s* >> >>> which are changed. In this way, it reduces both the amount of data to be >>> transferred by network and those to be decoded on the client side. >> Please mention the datasheet name and revision and section, where this >> functionality is described. > > Sorry but our datasheet is confidential. The basic idea of this > feature is that we can just compress the blocks which is different > with previous frame rather than full frame. This idea is similar to > the I & P frame in multimedia. It’s still good to have the name and revision of the datasheet, the code was developed against documented. (Public datasheets would be even better, also for review.) >> Which chips support it? > AST2400/2500/2600 all support it. >> >>> 4 new ctrls are added: >>> *Aspeed JPEG Format: to control aspeed's partial jpeg on/off >>> *Aspeed Compression Mode: to control aspeed's compression mode >>> *Aspeed HQ Mode: to control aspeed's HQ mode on/off >>> *Aspeed HQ Quality: to control the quality of aspeed's HQ mode >> Please add a space after the bullet points. >> >> Excuse my ignorance, how can these options be controlled? > > * Aspeed JPEG Format: to control jpeg format >   0: standard jpeg, 1: aspeed jpeg > * Aspeed Compression Mode: to control aspeed's compression mode >   0: DCT Only, 1: DCT VQ mix 2-color, 2: DCT VQ mix 4-color >   This is AST2400 only. It will adapt JPEG or VQ encoding method according >   to the context automatically. > * Aspeed HQ Mode: to control aspeed's HQ mode on/off >   0: disabled, 1: enabled > * Aspeed HQ Quality: to control the quality(0~11) of aspeed's HQ mode, >   only usefull if Aspeed HQ mode is enabled Thank you. So some sysfs file? >>> Aspeed JPEG Format requires an additional buffer, called bcd, to store >>> the information that which macro block in the new frame is different >> s/that which/which/ >> >>> from the old one. >>> >>> To have bcd correctly working, we need to swap the buffers for src0/1 to >>> make src1 refer to previous frame and src0 to the coming new frame. >> How did you test it? What do the clients need to support? >> >> Did you test, how much bandwidth is saved? Some numbers would be nice. > I tested it by aspeed's kvm client which support decoding the aspeed > format. Currently, I am porting this feature to novnc to have openbmc > support it. Nice. > The bandwidth saved is variant. It depends on how many blocks is > different between new and old frame.If the new frame is identical > with the previous one, the compressed frame only needs 12 Bytes. Thank you for the explanation. Kind regards, Paul