Re: [PATCH v0 04/14] media: au0828: Make I2C terminology more inclusive

2024-05-03 Thread Mauro Carvalho Chehab
Em Fri, 29 Mar 2024 17:00:28 + Easwar Hariharan escreveu: > I2C v7, SMBus 3.2, and I3C specifications have replaced "master/slave" > with more appropriate terms. Inspired by and following on to Wolfram's > series to fix drivers/i2c/[1], fix the terminology for users of > I2C_ALGOBIT

Re: [Intel-gfx] [PATCH i-g-t v3 04/11] lib/kunit: Fix misplaced igt_kunit() doc

2023-10-12 Thread Mauro Carvalho Chehab
On Wed, 11 Oct 2023 16:17:39 +0200 Janusz Krzysztofik wrote: > When igt_kunit() was converted to a helper and wrapped with a new function > promoted to take the name and role of the library API, related > documentation was left unchanged and still placed in front the demoted > function. Update

Re: [Intel-gfx] [PATCH i-g-t v3 02/11] lib/kunit: Fix handling of potential errors from F_GETFL

2023-10-12 Thread Mauro Carvalho Chehab
On Wed, 11 Oct 2023 16:17:37 +0200 Janusz Krzysztofik wrote: > Function fcntl(..., F_GETFL, ...) that returns file status flags may also > return a negative error code. Handle that error instead of blindly using > the returned value as flags. > > Signed-off-by: Janusz Krzysztofik >

Re: [Intel-gfx] [PATCH i-g-t v3 01/11] lib/ktap: Improve TODO workaround description

2023-10-12 Thread Mauro Carvalho Chehab
On Wed, 11 Oct 2023 16:17:36 +0200 Janusz Krzysztofik wrote: > A workaround was implemented in IGT KTAP parser so it could accepted KTAP > reports with missing top level KTAP version and test suite plan headers. > While the issue has been fixed by a kernel side commit c95e7c05c139 > ("kunit:

Re: [Intel-gfx] [PATCH i-g-t v2 04/11] lib/kunit: Parse KTAP report from the main process thread

2023-10-10 Thread Mauro Carvalho Chehab
ore debug statements, > - integrate common code around kunit_result_free() into it. > v2: Interrupt blocking read() on modprobe failure. > > Signed-off-by: Janusz Krzysztofik > Acked-by: Mauro Carvalho Chehab # v2 > --- > lib/igt_kmod.c | 261 +++ > lib/igt

Re: [Intel-gfx] [PATCH i-g-t v3 15/17] lib/kunit: Parse KTAP report from the main process thread

2023-09-20 Thread Mauro Carvalho Chehab
d and execute igt_dynamic() for each kunit > result obtained from igt_ktap_parse() called from the main thread. > > Also, drop no longer needed functions from igt_ktap soruces. > > v2: Interrupt blocking read() on modprobe failure. > > Signed-off-by: Janusz Krzysztofik L

Re: [Intel-gfx] [PATCH i-g-t v3 17/17] lib/kunit: Omit suite name prefix if the same as subtest name

2023-09-19 Thread Mauro Carvalho Chehab
btest names from module names, > there is a great chance that those two names match. Take this into > account when composing names for IGT dynamic sub-subtest names and drop > the leading test suite name component when it is the same as subtest name. > > Signed-off-by: Janusz Krzysztofik Revie

Re: [Intel-gfx] [PATCH i-g-t v3 07/17] lib/ktap: Drop checks for EINTR on read() failures

2023-09-19 Thread Mauro Carvalho Chehab
we use default SIGINT signal handler, read() should never fail with > errno set to EINTR on user interrupt, only the whole process should be > terminated. Drop checks for errno == EINTR as not applicable. This explanation makes sense to me. Acked-by: Mauro Carvalho Chehab > >

Re: [Intel-gfx] [PATCH i-g-t v3 05/17] lib/kunit: Fix illegal igt_fail() calls inside subtest body

2023-09-19 Thread Mauro Carvalho Chehab
On Tue, 19 Sep 2023 08:25:22 +0200 Mauro Carvalho Chehab wrote: > On Mon, 18 Sep 2023 15:42:55 +0200 > Janusz Krzysztofik wrote: > > > In a body of a subtest with dynamic sub-subtests, it is illegal to call > > igt_fail() and its variants from outside of a dyn

Re: [Intel-gfx] [PATCH i-g-t v3 05/17] lib/kunit: Fix illegal igt_fail() calls inside subtest body

2023-09-19 Thread Mauro Carvalho Chehab
gt; called when only listing subtests. > > Signed-off-by: Janusz Krzysztofik > Cc: Mauro Carvalho Chehab LGTM. Acked-by: Mauro Carvalho Chehab > --- > lib/igt_kmod.c | 76 +++--- > 1 file changed, 23 insertions(+), 53 deletions(-)

Re: [Intel-gfx] [PATCH i-g-t v3 10/17] lib/ktap: Read /dev/kmsg in blocking mode

2023-09-19 Thread Mauro Carvalho Chehab
; Signed-off-by: Janusz Krzysztofik > Acked-by: Mauro Carvalho Chehab # v1 LGTM. Reviewed-by: Mauro Carvalho Chehab > --- > lib/igt_kmod.c | 7 +- > lib/igt_ktap.c | 66 +- > 2 files changed, 28 insertions(+), 45 deletions(-) &g

Re: [Intel-gfx] [PATCH i-g-t v2 13/17] lib/ktap: Reimplement KTAP parser

2023-09-15 Thread Mauro Carvalho Chehab
On Fri, 8 Sep 2023 14:32:47 +0200 Janusz Krzysztofik wrote: Forgot to mention on my past review: > +, ) == 1 && len == strlen(buf))) { > + /* > + * TODO: drop the following workaround as soon as > + * kernel side issue

Re: [Intel-gfx] [PATCH i-g-t v2 07/17] lib/ktap: Don't ignore interrupt signals

2023-09-15 Thread Mauro Carvalho Chehab
On Wed, 13 Sep 2023 16:04:10 +0200 Janusz Krzysztofik wrote: > On Monday, 11 September 2023 11:01:42 CEST Mauro Carvalho Chehab wrote: > > On Fri, 8 Sep 2023 14:32:41 +0200 > > Janusz Krzysztofik wrote: > > > > > While reading KTAP data from /dev/kmsg w

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t v2 14/17] lib/kunit: Load test modules in background

2023-09-15 Thread Mauro Carvalho Chehab
unit test module from a separate thread > and process the intermediate results immediately, as soon as available > from the background parser, without waiting for completion of module > loading. LGTM. Acked-by: Mauro Carvalho Chehab > > Signed-of

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t v2 13/17] lib/ktap: Reimplement KTAP parser

2023-09-15 Thread Mauro Carvalho Chehab
nction with some > example data and verifies correctness of their parsing is also provided. > > v2: Fix incorrect and missing includes in the test source file, > - add license and copyright clauses to the test source file. > > Signed-off-by: Janusz Krzysztofik Acked-by: Mauro Carvalh

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t v2 16/17] lib/kunit: Strip "_test" or "_kunit" suffix from subtest names

2023-09-15 Thread Mauro Carvalho Chehab
_test" or "_kunit" suffix, those parts of the names don't carry any > useful information. Strip those suffixes from IGT subtest names. LGTM. Reviewed-by: Mauro Carvalho Chehab > > Signed-off-by: Janusz Krzysztofik > --- > lib/igt_kmod.c | 26 ++

Re: [Intel-gfx] [PATCH i-g-t v2 12/17] lib/ktap: Use IGT linked lists for storing KTAP results

2023-09-15 Thread Mauro Carvalho Chehab
ng > results. LGTM. Acked-by: Mauro Carvalho Chehab > > Signed-off-by: Janusz Krzysztofik > --- > lib/igt_kmod.c | 28 > lib/igt_ktap.c | 25 + > lib/igt_ktap.h | 6 -- > 3 files changed, 25 insertions(+), 3

Re: [Intel-gfx] [PATCH i-g-t v2 11/17] lib/kunit: Fail / skip on kernel taint

2023-09-15 Thread Mauro Carvalho Chehab
ysztofik Yeah, makes sense to me. Reviewed-by: Mauro Carvalho Chehab > --- > lib/igt_kmod.c | 12 +++- > 1 file changed, 11 insertions(+), 1 deletion(-) > > diff --git a/lib/igt_kmod.c b/lib/igt_kmod.c > index 020df286b8..988ac164cb 100644 > --- a/lib/igt_kmod.

Re: [Intel-gfx] [PATCH i-g-t v2 10/17] lib/ktap: Read /dev/kmsg in blocking mode

2023-09-15 Thread Mauro Carvalho Chehab
AGAIN responses, waiting for more KTAP data. Since we have no sleeps > inside those loops, extremely high CPU usage can be observed. > > Simplify reading KTAP reports by first switching the file descriptor back > to blocking mode. LGTM. Acked-by: Mauro Carvalho Chehab &g

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t v2 02/17] lib/kunit: Stop loading kunit module explicitly

2023-09-15 Thread Mauro Carvalho Chehab
> unload the "kunit" module explicitly on cleanup. Drop the unnecessary > operation. > > Signed-off-by: Janusz Krzysztofik LGTM. Acked-by: Mauro Carvalho Chehab > --- > lib/igt_kmod.c | 6 -- > 1 file changed, 6 deletions(-) > > diff --git a/lib/ig

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t v2 01/17] lib/kunit: Drop unused file stream

2023-09-15 Thread Mauro Carvalho Chehab
passed to > functions that actually read the data, there it is converted back to a > file descriptor with fileno() and the data is read with read(). > > Drop the unnecessary conversions and teach functions to accept and process > just the file descriptor of /dev/kmsg. LGTM. Acked-by

Re: [Intel-gfx] [PATCH i-g-t v2 05/17] lib/kunit: Fix illegal igt_fail() calls inside subtest body

2023-09-11 Thread Mauro Carvalho Chehab
On Mon, 11 Sep 2023 11:28:32 +0200 Janusz Krzysztofik wrote: > Hi Mauro, > > Thanks for review. > > On Monday, 11 September 2023 10:52:51 CEST Mauro Carvalho Chehab wrote: > > On Fri, 8 Sep 2023 14:32:39 +0200 > > Janusz Krzysztofik wrote: > > > > &g

Re: [Intel-gfx] [PATCH i-g-t v2 09/17] lib/ktap: Drop is_running flag

2023-09-11 Thread Mauro Carvalho Chehab
> whether we should continue parsing or return a failure. Drop that flag. > > Signed-off-by: Janusz Krzysztofik LGTM. Reviewed-by: Mauro Carvalho Chehab > --- > lib/igt_ktap.c | 32 > 1 file changed, 32 deletions(-) > > diff --git

Re: [Intel-gfx] [PATCH i-g-t v2 08/17] lib/kunit: Cancel KTP parser on module load failure

2023-09-11 Thread Mauro Carvalho Chehab
t > after that failure. If the KTAP thread sleeps for some reason then we > can fail to break the test immediately. > > Cancel the KTAP parser thread right after module load error and before > joining it. LGTM. Reviewed-by: Mauro Carvalho Chehab > > Signed-off-by: Janusz Krzysztofi

Re: [Intel-gfx] [PATCH i-g-t v2 07/17] lib/ktap: Don't ignore interrupt signals

2023-09-11 Thread Mauro Carvalho Chehab
On Fri, 8 Sep 2023 14:32:41 +0200 Janusz Krzysztofik wrote: > While reading KTAP data from /dev/kmsg we now ignore interrupt signals > that may occur during read() and we continue reading the data. No > explanation has been provided on what that could be needed for. The reason is that kunit

Re: [Intel-gfx] [PATCH i-g-t v2 06/17] lib/ktap: Make sure we fail on premature cancel

2023-09-11 Thread Mauro Carvalho Chehab
code on KTAP parser startup with a value that > indicates a failure, then change it to success when so indicated by result > of KTAP parsing. > > Signed-off-by: Janusz Krzysztofik Reviewed-by: Mauro Carvalho Chehab > --- > lib/igt_ktap.c | 5 ++--- > 1 file changed, 2 ins

Re: [Intel-gfx] [PATCH i-g-t v2 05/17] lib/kunit: Fix illegal igt_fail() calls inside subtest body

2023-09-11 Thread Mauro Carvalho Chehab
On Fri, 8 Sep 2023 14:32:39 +0200 Janusz Krzysztofik wrote: > In a body of a subtest with dynamic sub-subtests, it is illegal to call > igt_fail() and its variants from outside of a dynamic sub-subtest body. > On the other hand, it is perfectly legal to call either igt_skip() and > friends or

Re: [Intel-gfx] [PATCH i-g-t v2 04/17] lib/kunit: Optimize calls to igt_success/skip/fail()

2023-09-11 Thread Mauro Carvalho Chehab
Moreover, using more advanced variants of igt_skip() and igt_fail() where > applicable makes the code more compact. Go for it. Reviewed-by: Mauro Carvalho Chehab > > Signed-off-by: Janusz Krzysztofik > --- > lib/igt_kmod.c | 14 +++--- > 1 file changed, 3 inserti

Re: [Intel-gfx] [PATCH 0/4] Invalidate TLB cache for all GT's

2023-08-01 Thread Mauro Carvalho Chehab
invalidation in MMIO memory. The result is a leaner, more targeted proposal. Series look good to me. Feel free to add my R-B to the patches I didn't sign already. Reviewed-by: Mauro Carvalho Chehab Other patches from the original series might follow. Thanks, Andi [1] https

Re: [Intel-gfx] [PATCH] drm/i915/gt: Fix sphinx warnings for workarounds documentation

2023-02-07 Thread Mauro Carvalho Chehab
On 2/6/23 18:00, Rodrigo Vivi wrote: On Tue, Jan 31, 2023 at 02:03:01PM +0100, Mauro Carvalho Chehab wrote: On 1/24/23 20:39, Rodrigo Vivi wrote: On Sat, Jan 21, 2023 at 04:08:53PM -0300, Gustavo Sousa wrote: The wildchar ("*") used in the function name patterns in the doc

Re: [Intel-gfx] [PATCH] drm/i915/gt: Fix sphinx warnings for workarounds documentation

2023-01-31 Thread Mauro Carvalho Chehab
nline literal markup and, for consistency, do the same for the other function names mentioned. Fixes: 0c3064cf33fb ("drm/i915/doc: Document where to implement register workarounds") Reported-by: kernel test robot Signed-off-by: Gustavo Sousa Cc: Mauro Carvalho Chehab just in case he sees some bette

[Intel-gfx] [PATCH 0/3] Add KUnit support for i915 mock selftests

2022-12-01 Thread Mauro Carvalho Chehab
=== [13:23:42] [13:23:42] Testing complete. Ran 18 tests: passed: 18 [13:23:42] Elapsed time: 302.766s total, 0.003s configuring, 280.393s building, 22.341s running Mauro Carvalho Chehab (3): drm/i915: place selftest

[Intel-gfx] [PATCH 2/3] drm/i915: export all mock selftest functions

2022-12-01 Thread Mauro Carvalho Chehab
In order to prepare for a new KUnit module that will run selftests, export all mock selftest functions to I915_SELFTEST namespace. No functional changes. Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See

[Intel-gfx] [PATCH 1/3] drm/i915: place selftest preparation on a separate function

2022-12-01 Thread Mauro Carvalho Chehab
The selftest preparation logic should also be used by KUnit. So, place it on a separate function and export it. Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH 0/3] at: https://lore.kernel.org/all

[Intel-gfx] [PATCH 3/3] drm/i915: allow running mock selftests via Kunit

2022-12-01 Thread Mauro Carvalho Chehab
echo "[0.00] TAP version 14" >logs dmesg >>logs ./tools/testing/kunit/kunit.py parse logs Note: kunit.py is currently broken with modules, not producing any results if "TAP version xx" is not found. It also shows the results duplicated.

Re: [Intel-gfx] [PATCH v10 18/19] drm/vc4: vec: Add support for more analog TV standards

2022-11-17 Thread Mauro Carvalho Chehab
On Thu, 17 Nov 2022 10:29:01 +0100 Maxime Ripard wrote: > From: Mateusz Kwiatkowski > > Add support for the following composite output modes (all of them are > somewhat more obscure than the previously defined ones): > > - NTSC_443 - NTSC-style signal with the chroma subcarrier shifted to >

Re: [Intel-gfx] [PATCH v10 05/19] drm/connector: Add TV standard property

2022-11-17 Thread Mauro Carvalho Chehab
On Thu, 17 Nov 2022 10:28:48 +0100 Maxime Ripard wrote: > The TV mode property has been around for a while now to select and get the > current TV mode output on an analog TV connector. > > Despite that property name being generic, its content isn't and has been > driver-specific which makes it

Re: [Intel-gfx] KUnit issues - Was: [igt-dev] [PATCH RFC v2 8/8] drm/i915: check if current->mm is not NULL

2022-11-14 Thread Mauro Carvalho Chehab
On Mon, 7 Nov 2022 15:16:17 -0800 Daniel Latypov wrote: > On Mon, Nov 7, 2022 at 10:38 AM Michał Winiarski > wrote: > > > > On Thu, Nov 03, 2022 at 04:23:02PM +0100, Mauro Carvalho Chehab wrote: > > > Hi, > > > > > > I'm facing a couple of i

Re: [Intel-gfx] KUnit issues - Was: [igt-dev] [PATCH RFC v2 8/8] drm/i915: check if current->mm is not NULL

2022-11-04 Thread Mauro Carvalho Chehab
On Fri, 4 Nov 2022 08:49:55 +0100 Mauro Carvalho Chehab wrote: > On Thu, 3 Nov 2022 15:43:26 -0700 > Daniel Latypov wrote: > > > On Thu, Nov 3, 2022 at 8:23 AM Mauro Carvalho Chehab > > wrote: > > > > > > Hi, > > > > > > I'm facing a

Re: [Intel-gfx] KUnit issues - Was: [igt-dev] [PATCH RFC v2 8/8] drm/i915: check if current->mm is not NULL

2022-11-04 Thread Mauro Carvalho Chehab
On Thu, 3 Nov 2022 15:43:26 -0700 Daniel Latypov wrote: > On Thu, Nov 3, 2022 at 8:23 AM Mauro Carvalho Chehab > wrote: > > > > Hi, > > > > I'm facing a couple of issues when testing KUnit with the i915 driver. > > > > The DRM subsystem and the i915 dr

[Intel-gfx] KUnit issues - Was: [igt-dev] [PATCH RFC v2 8/8] drm/i915: check if current->mm is not NULL

2022-11-03 Thread Mauro Carvalho Chehab
have just two levels (test suite and tests). Are there a way to add test groups there? Regards, Mauro Forwarded message: Date: Thu, 3 Nov 2022 14:51:38 +0000 From: Mauro Carvalho Chehab To: Cc: Thomas Hellström , linux-kselft...@vger.kernel.org, Michał Winiarski , dri-de...@lists.freedeskt

[Intel-gfx] [PATCH RFC v2 0/8] Add KUnit support for i915 driver

2022-11-03 Thread Mauro Carvalho Chehab
some tests might fail on newer hardware. --- v2: - changes outside KUnit module moved to separate patches; - added support for running live and perf selftests on bare metal; - made the KUnit test logic identical to i915 selftest. Mauro Carvalho Chehab (8): drm/i915: export all selftest func

[Intel-gfx] [PATCH RFC v2 2/8] drm/i915: place selftest preparation on a separate function

2022-11-03 Thread Mauro Carvalho Chehab
The selftest preparation logic should also be used by KUnit. So, place it on a separate function and export it. Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH RFC v2 0/8] at: https

[Intel-gfx] [PATCH RFC v2 8/8] drm/i915: check if current->mm is not NULL

2022-11-03 Thread Mauro Carvalho Chehab
/0x1b9 [i915] [ 316.846119] __igt_mmap+0xfe/0x680 [i915] Unfortunately, when KUnit module runs, it doesn't create an user context, causing mmap tests to fail. Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See

[Intel-gfx] [PATCH RFC v2 4/8] drm/i915: add support to run KUnit tests on bare metal

2022-11-03 Thread Mauro Carvalho Chehab
Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH RFC v2 0/8] at: https://lore.kernel.org/all/cover.1667486144.git.mche...@kernel.org/ drivers/gpu/drm/i915/selftests/i915_kunit.c | 100 1 file changed, 100

[Intel-gfx] [PATCH RFC v2 1/8] drm/i915: export all selftest functions

2022-11-03 Thread Mauro Carvalho Chehab
In order to prepare for a new KUnit module that will run selftests, export all selftest functions to I915_SELFTEST namespace. No functional changes. Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH

[Intel-gfx] [PATCH RFC v2 7/8] drm/i915: now that all functions are used, remove __maybe_unused

2022-11-03 Thread Mauro Carvalho Chehab
The PCI-specific KUnit tests that run in bare metal got added, so we can remove the __maybe_unused from such functions. Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH RFC v2 0/8] at: https

[Intel-gfx] [PATCH RFC v2 3/8] drm/i915: allow running mock selftests via Kunit

2022-11-03 Thread Mauro Carvalho Chehab
echo "[0.00] TAP version 14" >logs dmesg >>logs ./tools/testing/kunit/kunit.py parse logs Note: kunit.py is currently broken with modules, not producing any results if "TAP version xx" is not found. It also shows the results duplicated.

[Intel-gfx] [PATCH RFC v2 5/8] drm/i915: add live selftests to KUnit

2022-11-03 Thread Mauro Carvalho Chehab
Now that i915 KUnit has PCI support, add live tests as well. NOTE: currently, some tests are failing when excecuting via KUnit. I'll do a further investigation to check why, and if this patch can be safely merged or not. Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large

[Intel-gfx] [PATCH RFC v2 6/8] drm/i915: add perf selftests to KUnit

2022-11-03 Thread Mauro Carvalho Chehab
Now that i915 KUnit has PCI support, add perf tests as well. Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH RFC v2 0/8] at: https://lore.kernel.org/all/cover.1667486144.git.mche...@kernel.org

[Intel-gfx] [PATCH RFC] drm/i915: allow running mock selftests via Kunit

2022-11-01 Thread Mauro Carvalho Chehab
echo "[0.00] TAP version 14" >logs dmesg >>logs ./tools/testing/kunit/kunit.py parse logs Note: kunit.py is currently broken with modules, not producing any results if "TAP version xx" is not found. It also shows the results duplicated. Signe

Re: [Intel-gfx] [PATCH v3 27/37] docs: gpu: i915.rst: gt: add more kernel-doc markups

2022-09-26 Thread Mauro Carvalho Chehab
Em Fri, 9 Sep 2022 05:06:46 -0400 Rodrigo Vivi escreveu: > On Fri, Sep 09, 2022 at 09:34:34AM +0200, Mauro Carvalho Chehab wrote: > > There are several documented GT kAPI that aren't currently part > > of the docs. Add them, as this allows identifying issues with > >

Re: [Intel-gfx] [PATCH v3 01/37] drm/i915: fix kernel-doc trivial warnings on i915/*.[ch] files

2022-09-26 Thread Mauro Carvalho Chehab
Em Fri, 16 Sep 2022 17:03:27 +0300 Gwan-gyeong Mun escreveu: > > /** > > - * Called when user space has done writes to this buffer > > + * i915_gem_sw_finish_ioctl - Called when user space has done writes to > > + * this buffer > As per this link[1], the brief description does not

Re: [Intel-gfx] [PATCH v3 19/37] drm/i915: stop using kernel-doc markups for something else

2022-09-26 Thread Mauro Carvalho Chehab
Em Mon, 12 Sep 2022 10:19:04 -0700 Matt Roper escreveu: > > Those *appear* to be kernel-doc markups, but they aren't, because > > the structs themselves are not properly marked. See, for instance > > struct intel_context. > > > > scripts/kerneldoc will *only* consider what's there as a proper >

Re: [Intel-gfx] [PATCH v6 0/4] Let userspace know when snd-hda-intel needs i915

2022-09-19 Thread Mauro Carvalho Chehab
Hi Luis, On Mon, 9 May 2022 13:38:28 -0700 Luis Chamberlain wrote: > On Mon, May 09, 2022 at 06:23:35PM +0200, Mauro Carvalho Chehab wrote: > > Currently, kernel/module annotates module dependencies when > > request_symbol is used, but it doesn't cover more complex inter-driver &

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t 3/4] tests/core_hotunplug: Don't apply i915 workarounds on other platforms

2022-09-19 Thread Mauro Carvalho Chehab
On Tue, 13 Sep 2022 14:04:40 +0200 Janusz Krzysztofik wrote: > Starting from commit 0edabd8a4a08 ("core_hotunplug: fix audio unbind > logic") audio modules are unloaded unconditionally before graphics driver > unbind. This is required for i915 to be unbound cleanly from a graphics > device.

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t 4/4] tests/core_hotunplug: Select health checks for initially detected chipset

2022-09-19 Thread Mauro Carvalho Chehab
> Signed-off-by: Janusz Krzysztofik Makes sense to me, once we have patch 3/4 applied. So, Reviewed-by: Mauro Carvalho Chehab > --- > tests/core_hotunplug.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/tests/core_hotunplug.c b/tests/core_

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t 2/4] tests/core_hotunplug: Also unload audio before device unplug

2022-09-19 Thread Mauro Carvalho Chehab
ned-off-by: Janusz Krzysztofik LGTM. Reviewed-by: Mauro Carvalho Chehab > --- > tests/core_hotunplug.c | 22 ++ > 1 file changed, 22 insertions(+) > > diff --git a/tests/core_hotunplug.c b/tests/core_hotunplug.c > index 733ea8efb0..c375688

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t 1/4] tests/core_hotunplug: Free mem allocated by igt_audio_driver_unload

2022-09-19 Thread Mauro Carvalho Chehab
-off-by: Janusz Krzysztofik Reviewed-by: Mauro Carvalho Chehab > --- > tests/core_hotunplug.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/tests/core_hotunplug.c b/tests/core_hotunplug.c > index a0d29b799a..733ea8efb0 100644 > --- a/tests/core_hotunplug.c > +

Re: [Intel-gfx] [PATCH v3 19/37] drm/i915: stop using kernel-doc markups for something else

2022-09-12 Thread Mauro Carvalho Chehab
Hi Matt, Em Mon, 12 Sep 2022 08:09:57 -0700 Matt Roper escreveu: > > --- a/drivers/gpu/drm/i915/gt/intel_context_types.h > > +++ b/drivers/gpu/drm/i915/gt/intel_context_types.h > > Several of the comments in this file do appear to be kerneldoc (in fact > kerneldoc that was specifically

[Intel-gfx] [PATCH v3 28/37] docs: gpu: i915.rst: GuC: add more kernel-doc markups

2022-09-09 Thread Mauro Carvalho Chehab
There are several documented GuC kAPI that aren't currently part of the docs. Add them, as this allows identifying issues with badly-formatted tags. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C

[Intel-gfx] [PATCH v3 18/37] drm/i915: fix i915_gem_ttm_move.c DOC: markup

2022-09-09 Thread Mauro Carvalho Chehab
The doc markup should not end with ":", as it would generate a warning on Sphinx while generating the cross-reference tag. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.

[Intel-gfx] [PATCH v3 36/37] drm/i915: add GuC functions to the documentation

2022-09-09 Thread Mauro Carvalho Chehab
Currently, functions inside GuC aren't presented as part of the GuC documentation. Add them. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH v3 00/37] at: https

[Intel-gfx] [PATCH v3 35/37] drm/i915: add descriptions for some RPM macros at intel_gt_pm.h

2022-09-09 Thread Mauro Carvalho Chehab
The intel_gt_pm.h file contains some convenient macros to be used in GT code in order to get/put runtime PM references and for checking them. Add descriptions based on the ones at intel_wakeref.h and intel_runtime_pm.c. Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large

[Intel-gfx] [PATCH v3 09/37] drm/i915: gem: add kernel-doc description for some function parameters

2022-09-09 Thread Mauro Carvalho Chehab
There are some parameters missing at the kernel-doc markups on some gem files. Some of those are trivial enough to be added. Document them. Reviewed-by: Nirmoy Das Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C

[Intel-gfx] [PATCH v3 37/37] drm/i915: be consistent with kernel-doc function declaration

2022-09-09 Thread Mauro Carvalho Chehab
Currently, 91% of kernel-doc function declarations don't have parenthesis on it. Let's be consistent inside the driver by removing the parenthesis from the other ones. Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C

[Intel-gfx] [PATCH v3 10/37] drm/i915: i915_gpu_error.c: document dump_flags

2022-09-09 Thread Mauro Carvalho Chehab
Kernel-doc dump_flags parameter is missing at i915_capture_error_state(). Document it. Fixes: a6f0f9cf330a ("drm/i915/guc: Plumb GuC-capture into gpu_coredump") Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, on

[Intel-gfx] [PATCH v3 31/37] docs: gpu: i915.rst: GEM/TTM: add more kernel-doc markups

2022-09-09 Thread Mauro Carvalho Chehab
There are several documented GEM/TTM kAPI that aren't currently part of the docs. Add them, as this allows identifying issues with badly-formatted tags. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were

[Intel-gfx] [PATCH v3 05/37] drm/i915: gem: fix some Kernel-doc issues

2022-09-09 Thread Mauro Carvalho Chehab
by: - lack of function name at the kernel-doc markup; - renamed parameters. Address them. Reviewed-by: Nirmoy Das Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH v3 00/37] at: https

[Intel-gfx] [PATCH v3 16/37] drm/i915: i915_gem_region.h: fix i915_gem_apply_to_region_ops doc

2022-09-09 Thread Mauro Carvalho Chehab
, using a list, in order for it to be properly parsed during documentation build time. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH v3 00/37] at: https://lore.kernel.org

[Intel-gfx] [PATCH v3 03/37] drm/i915: gt: fix some Kernel-doc issues

2022-09-09 Thread Mauro Carvalho Chehab
'flags' not described in 'guc_log_buffer_state' drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h:401: warning: Function parameter or member 'version' not described in 'guc_log_buffer_state' Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large

[Intel-gfx] [PATCH v3 32/37] docs: gpu: i915.rst: add the remaining kernel-doc markup files

2022-09-09 Thread Mauro Carvalho Chehab
fi; done >aaa Add them to i915.rst as well. Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH v3 00/37] at: https://lore.kernel.org/all/cover.1662708705.git.mche...

[Intel-gfx] [PATCH v3 11/37] drm/i915: document kernel-doc trivial issues

2022-09-09 Thread Mauro Carvalho Chehab
' drivers/gpu/drm/i915/gt/intel_engine_types.h:276: warning: Function parameter or member 'preempt_hang' not described in 'intel_engine_execlists' That are due undocumented parameters. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people

[Intel-gfx] [PATCH v3 22/37] drm/i915: i915_vma_resource.c: fix some kernel-doc markups

2022-09-09 Thread Mauro Carvalho Chehab
-string without end-string. That's because @foo evaluates into **foo**, and placing anything after it without spaces cause Sphinx to warn and do the wrong thing.. So, replace them by a different Sphinx-compatible tag. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid

[Intel-gfx] [PATCH v3 33/37] drm/i915 i915_gem_object_types.h: document struct i915_lut_handle

2022-09-09 Thread Mauro Carvalho Chehab
commit d1b48c1e7184 ("drm/i915: Replace execbuf vma ht with an idr") added a rbtree list to allow searching for obj/ctx. Document it. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on

[Intel-gfx] [PATCH v3 14/37] drm/i915: skl_scaler: fix return value kernel-doc markup

2022-09-09 Thread Mauro Carvalho Chehab
The way it is, it produces this warning: Documentation/gpu/i915:150: ./drivers/gpu/drm/i915/display/skl_scaler.c:213: WARNING: Block quote ends without a blank line; unexpected unindent. Use list markups to suppress the warning. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho

[Intel-gfx] [PATCH v3 15/37] drm/i915: intel_pm.c: fix some ascii artwork at kernel-doc

2022-09-09 Thread Mauro Carvalho Chehab
drigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH v3 00/37] at: https://lore.kernel.org/all/cover.1662708705.git.mche...@kernel.org/ drivers/gpu/drm/i915/intel

[Intel-gfx] [PATCH v3 23/37] drm/i915: i915_gem.c fix a kernel-doc issue

2022-09-09 Thread Mauro Carvalho Chehab
Prevent this Sphinx warning: Documentation/foo/i915:728: ./drivers/gpu/drm/i915/i915_gem.c:447: WARNING: Inline emphasis start-string without end-string. By using @data to identify the data field, as expected by kernel-doc. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho

[Intel-gfx] [PATCH v3 25/37] drm/i915: i915_deps: use a shorter title markup

2022-09-09 Thread Mauro Carvalho Chehab
The DOC: tag waits for a one-line short title for the doc section. Using multiple lines will produce a weird output. So, add a shorter description for the title, while keeping the current content below it. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing

[Intel-gfx] [PATCH v3 02/37] drm/i915: display: fix kernel-doc markup warnings

2022-09-09 Thread Mauro Carvalho Chehab
' Those are due to wrong parameter of function name. Address them. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH v3 00/37] at: https://lore.kernel.org/all/cover.1662708705

[Intel-gfx] [PATCH v3 34/37] drm/i915: document struct drm_i915_gem_object

2022-09-09 Thread Mauro Carvalho Chehab
This is a large struct used to describe gem objects. It is currently partially documented. Finish its documentation, filling the gaps from git logs. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C

[Intel-gfx] [PATCH v3 21/37] drm/i915: dvo_sil164.c: use SPDX header

2022-09-09 Thread Mauro Carvalho Chehab
This file is licensed with MIT license. Change its license text to use SPDX. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH v3 00/37] at: https://lore.kernel.org/all

[Intel-gfx] [PATCH v3 13/37] drm/i915: intel_fb: fix a kernel-doc issue with Sphinx

2022-09-09 Thread Mauro Carvalho Chehab
-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH v3 00/37] at: https://lore.kernel.org/all/cover.1662708705.git.mche...@kernel.org/ drivers/gpu/drm/i915/display/intel_fb.c | 2 +- 1 file changed, 1 insertion(+), 1

[Intel-gfx] [PATCH v3 29/37] docs: gpu: i915.rst: GVT: add more kernel-doc markups

2022-09-09 Thread Mauro Carvalho Chehab
There are several documented GVT kAPI that aren't currently part of the docs. Add them, as this allows identifying issues with badly-formatted tags. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C

[Intel-gfx] [PATCH v3 17/37] drm/i915: i915_gem_wait.c: fix a kernel-doc markup

2022-09-09 Thread Mauro Carvalho Chehab
The return codes for i915_gem_wait_ioctl() have identation issues, and will be displayed on a very confusing way. Use lists to improve its output. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C

[Intel-gfx] [PATCH v3 19/37] drm/i915: stop using kernel-doc markups for something else

2022-09-09 Thread Mauro Carvalho Chehab
There are some occurrences of "/**" that aren't actually part of a kernel-doc markup. Replace them by "/*", in order to make easier to identify what i915 files contain kernel-doc markups. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombi

[Intel-gfx] [PATCH v3 12/37] drm/i915: intel_dp_link_training.c: fix kernel-doc markup

2022-09-09 Thread Mauro Carvalho Chehab
: ./drivers/gpu/drm/i915/display/intel_dp_link_training.c:186: WARNING: Definition list ends without a blank line; unexpected unindent. Use table markups to fix it. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing

[Intel-gfx] [PATCH v3 24/37] drm/i915: i915_scatterlist.h: fix some kernel-doc markups

2022-09-09 Thread Mauro Carvalho Chehab
and do the wrong thing.. So, replace them by a different Sphinx-compatible tag. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH v3 00/37] at: https://lore.kernel.org/all

[Intel-gfx] [PATCH v3 30/37] docs: gpu: i915.rst: PM: add more kernel-doc markups

2022-09-09 Thread Mauro Carvalho Chehab
Both intel_runtime_pm.h and intel_pm.c contains kAPI for runtime PM. So, add them to the documentation. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH v3 00/37

[Intel-gfx] [PATCH v3 27/37] docs: gpu: i915.rst: gt: add more kernel-doc markups

2022-09-09 Thread Mauro Carvalho Chehab
There are several documented GT kAPI that aren't currently part of the docs. Add them, as this allows identifying issues with badly-formatted tags. Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH v3

[Intel-gfx] [PATCH v3 07/37] drm/i915: i915_gem_ttm: fix a kernel-doc markup

2022-09-09 Thread Mauro Carvalho Chehab
Two new fields were added to __i915_gem_ttm_object_init() without their corresponding documentation. Document them. Fixes: 9b78b5dade2d ("drm/i915: add i915_gem_object_create_region_at()") Reviewed-by: Nirmoy Das Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a la

[Intel-gfx] [PATCH v3 20/37] drm/i915: dvo_ch7xxx.c: use SPDX header

2022-09-09 Thread Mauro Carvalho Chehab
This file is licensed with MIT license. Change its license text to use SPDX. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH v3 00/37] at: https://lore.kernel.org/all

[Intel-gfx] [PATCH v3 26/37] docs: gpu: i915.rst: display: add kernel-doc markups

2022-09-09 Thread Mauro Carvalho Chehab
There are several documented kAPI at the display side that aren't currently part of the docs. Add them, as this allows identifying issues with badly-formatted tags. Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing

[Intel-gfx] [PATCH v3 04/37] drm/i915: gvt: fix kernel-doc trivial warnings

2022-09-09 Thread Mauro Carvalho Chehab
/gvt/vgpu.c:358: warning: expecting prototype for intel_gvt_destroy_vgpu(). Prototype was for intel_gvt_destroy_idle_vgpu() instead Reviewed-by: Rodrigo Vivi Acked-by: Zhenyu Wang Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C

[Intel-gfx] [PATCH v3 00/37] drm/i915: fix kernel-doc issues

2022-09-09 Thread Mauro Carvalho Chehab
nd, documenting some structs at i915_gem_object_types.h and intel_gt_pm.h, plus adding intel-guc.c internal functions to the generated documentation. Mauro Carvalho Chehab (37): drm/i915: fix kernel-doc trivial warnings on i915/*.[ch] files drm/i915: display: fix kernel-doc markup warnings

[Intel-gfx] [PATCH v3 08/37] drm/i915: i915_gem_ttm_pm.c: fix kernel-doc markups

2022-09-09 Thread Mauro Carvalho Chehab
in 'i915_ttm_restore_region' Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH v3 00/37] at: https://lore.kernel.org/all/cover.1662708705.git.mche...@kernel.org/ drivers/gpu/drm

[Intel-gfx] [PATCH v3 06/37] drm/i915: intel_wakeref.h: fix some kernel-doc markups

2022-09-09 Thread Mauro Carvalho Chehab
/intel_wakeref.h:149: warning: expecting prototype for intel_wakeref_put_flags(). Prototype was for __intel_wakeref_put() instead Fix them. Additionally, improve title for intel_wakeref_get_if_active(). Reviewed-by: Rodrigo Vivi Signed-off-by: Mauro Carvalho Chehab --- To avoid mailbombing on a large

[Intel-gfx] [PATCH v3 01/37] drm/i915: fix kernel-doc trivial warnings on i915/*.[ch] files

2022-09-09 Thread Mauro Carvalho Chehab
Carvalho Chehab --- To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. See [PATCH v3 00/37] at: https://lore.kernel.org/all/cover.1662708705.git.mche...@kernel.org/ drivers/gpu/drm/i915/i915_active.h | 14 +++--- drivers/gpu/drm/i915

Re: [Intel-gfx] [PATCH v2 35/39] docs: gpu: i915.rst: add the remaining kernel-doc markup files

2022-09-06 Thread Mauro Carvalho Chehab
On Tue, 9 Aug 2022 06:20:57 -0400 Rodrigo Vivi wrote: > On Wed, Jul 13, 2022 at 09:12:23AM +0100, Mauro Carvalho Chehab wrote: > > There are other files with kernel-doc markups: > > > > $ git grep -l "/\*\*" $(git ls-files|grep drivers/gpu/drm/i915/) > &

Re: [Intel-gfx] [PATCH v2 30/39] docs: gpu: i915.rst: gt: add more kernel-doc markups

2022-09-06 Thread Mauro Carvalho Chehab
On Tue, 9 Aug 2022 06:01:53 -0400 Rodrigo Vivi wrote: > On Wed, Jul 13, 2022 at 09:12:18AM +0100, Mauro Carvalho Chehab wrote: > > There are several documented GT kAPI that aren't currently part > > of the docs. Add them, as this allows identifying issues with > >

  1   2   3   4   >