that it only happens
when not using rtcwake.
Fixes: 0b631ed3ce92 ("kselftest: cpufreq: Add RTC wakeup alarm")
Signed-off-by: Nícolas F. R. A. Prado
---
tools/testing/selftests/cpufreq/cpufreq.sh | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selft
Shen
Signed-off-by: Tinghan Shen
Co-developed-by: Jason Chen
Signed-off-by: Jason Chen
Signed-off-by: Nícolas F. R. A. Prado
---
arch/arm64/boot/dts/mediatek/mt8188-evb.dts| 6 +++-
arch/arm64/boot/dts/mediatek/mt8188.dtsi | 36 --
.../boot/dts/mediatek/mt8390-
Add the firmware-name property for SCP core0 so the firmware can be
loaded from its canonical location in the linux-firmware repository.
Reviewed-by: AngeloGioacchino Del Regno
Signed-off-by: Nícolas F. R. A. Prado
---
arch/arm64/boot/dts/mediatek/mt8390-genio-common.dtsi | 1 +
1 file
reg's maxItems is already defined as 3 in the base schema. Remove the
redundant assignment in the if branch for mt8192/mt8195.
Suggested-by: Krzysztof Kozlowski
Signed-off-by: Nícolas F. R. A. Prado
---
Documentation/devicetree/bindings/remoteproc/mtk,scp.yaml | 1 -
1 file changed, 1 del
the CFG memory region is present in the parent node.
Fixes: 91e0d560b9fd ("dt-bindings: remoteproc: mediatek: Support MT8188
dual-core SCP")
Reviewed-by: AngeloGioacchino Del Regno
Reviewed-by: Krzysztof Kozlowski
Signed-off-by: Nícolas F. R. A. Prado
---
.../devicetree/bindings/
. Fix reg minItems for MT8192 and MT8195 by setting it to 3.
Fixes: 6b55b1e2fd7f ("dt-bindings: remoteproc: mediatek: Support MT8195
dual-core SCP")
Signed-off-by: Nícolas F. R. A. Prado
---
Documentation/devicetree/bindings/remoteproc/mtk,scp.yaml | 1 +
1 file changed, 1 insertion(+
-by: Nícolas F. R. A. Prado
---
Changes in v2:
- Added patch 3 removing redundant reg maxItems
- Clarified commit message for patch 1
- Rebased now that MDP3 series dependency has been merged
- Link to v1:
https://lore.kernel.org/r/20250318-scp-dual-core-mt8390-v1-0-8733e192c...@collabora.com
On Wed, Mar 19, 2025 at 08:16:37AM +0100, Krzysztof Kozlowski wrote:
> On 18/03/2025 23:22, Nícolas F. R. A. Prado wrote:
> > Both MT8192 and MT8195 have an L1TCM memory, so it should be described
> > in reg, and therefore reg's minItems should be 3, as is already impli
"MediaTek MT8188 MDP3 Enablement" series [1].
[1]
https://lore.kernel.org/all/20241218105320.38980-1-angelogioacchino.delre...@collabora.com
Signed-off-by: Nícolas F. R. A. Prado
---
Nícolas F. R. A. Prado (4):
dt-bindings: remoteproc: mediatek: Add missing minItems for 8192/819
Add the firmware-name property for SCP core0 so the firmware can be
loaded from its canonical location in the linux-firmware repository.
Signed-off-by: Nícolas F. R. A. Prado
---
arch/arm64/boot/dts/mediatek/mt8390-genio-common.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64
l-core SCP")
Signed-off-by: Nícolas F. R. A. Prado
---
Documentation/devicetree/bindings/remoteproc/mtk,scp.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/remoteproc/mtk,scp.yaml
b/Documentation/devicetree/bindings/remoteproc/mtk
Shen
Signed-off-by: Tinghan Shen
Co-developed-by: Jason Chen
Signed-off-by: Jason Chen
Signed-off-by: Nícolas F. R. A. Prado
---
arch/arm64/boot/dts/mediatek/mt8188-evb.dts| 6 +++-
arch/arm64/boot/dts/mediatek/mt8188.dtsi | 36 --
.../boot/dts/mediatek/mt8390-
the CFG memory region is present in the parent node.
Fixes: 91e0d560b9fd ("dt-bindings: remoteproc: mediatek: Support MT8188
dual-core SCP")
Signed-off-by: Nícolas F. R. A. Prado
---
.../devicetree/bindings/remoteproc/mtk,scp.yaml | 19 ---
1 file changed, 16
On Fri, Nov 01, 2024 at 03:54:58PM +0800, Chen-Yu Tsai wrote:
> On Sat, Oct 26, 2024 at 5:16 AM Nícolas F. R. A. Prado
> wrote:
> >
> > Currently the set_config callback in the gpio_chip registered by the
> > pinctrl-mtk-common driver only supports configuring a single p
On Fri, Oct 25, 2024 at 03:45:35PM -0400, Nícolas F. R. A. Prado wrote:
> This series was motivated by the regression fixed by 166bf8af9122
> ("pinctrl: mediatek: common-v2: Fix broken bias-disable for
> PULL_PU_PD_RSEL_TYPE"). A bug was introduced in the pinctrl_paris drive
Currently the set_config callback in the gpio_chip registered by the
pinctrl-mtk-common driver only supports configuring a single parameter
on specific pins (the input debounce of the EINT controller, on pins
that support it), even though many other configurations are already
implemented and availa
through the pinctrl API for configuration of
pins by the Devicetree and other drivers.
Expose all configurations currently implemented through the GPIO API so
they can also be set from userspace, which is particularly useful to
allow testing them from userspace.
Signed-off-by: Nícolas F. R. A
retrieved from userspace.
The test reads the test plan from a YAML file, which includes the chips
and pin settings to set and validate.
Signed-off-by: Nícolas F. R. A. Prado
---
tools/testing/selftests/gpio/Makefile | 2 +-
.../gpio-set-get-config-example-test-plan.yaml | 15
in other tests.
Signed-off-by: Nícolas F. R. A. Prado
---
tools/testing/selftests/gpio/gpio-mockup-cdev.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/tools/testing/selftests/gpio/gpio-mockup-cdev.c
b/tools/testing/selftests/gpio/gpio-mockup-cdev.c
index
s-disable for
PULL_PU_PD_RSEL_TYPE")
- pin: 34
bias: "pull-up"
- pin: 34
bias: "pull-down"
- pin: 34
bias: "disabled"
[2] https://github.com/kernelci/platform-test-parameters
Signed-off-by: Nícolas F. R. A. Prado
---
Changes in v2:
- Added pat
through the pinctrl API for configuration of
pins by the Devicetree and other drivers.
Expose all configurations currently implemented through the GPIO API so
they can also be set from userspace, which is particularly useful to
allow testing them from userspace.
Signed-off-by: Nícolas F. R. A
On Thu, Oct 24, 2024 at 05:17:05PM +0200, AngeloGioacchino Del Regno wrote:
> Il 11/09/24 12:10, AngeloGioacchino Del Regno ha scritto:
> > Il 09/09/24 20:37, Nícolas F. R. A. Prado ha scritto:
> > > Currently the set_config callback in the gpio_chip registered by the
> >
if there are missing devices they are reported.
Signed-off-by: Nícolas F. R. A. Prado
---
Hi,
For details about the test, please see the README.rst included in the
patch.
This v2 contains changes addressing feedback received on the RFCv1
series, during the session at plumbers [1] and a few other
retrieved from userspace.
The test reads the test plan from a YAML file, which includes the chips
and pin settings to set and validate.
Signed-off-by: Nícolas F. R. A. Prado
---
tools/testing/selftests/gpio/Makefile | 2 +-
.../gpio-set-get-config-example-test-plan.yaml | 15
in other tests.
Signed-off-by: Nícolas F. R. A. Prado
---
tools/testing/selftests/gpio/gpio-mockup-cdev.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/tools/testing/selftests/gpio/gpio-mockup-cdev.c
b/tools/testing/selftests/gpio/gpio-mockup-cdev.c
index
.
Expose all configurations currently implemented through the GPIO API so
they can also be set from userspace, which is particularly useful to
allow testing them from userspace.
Signed-off-by: Nícolas F. R. A. Prado
---
drivers/pinctrl/mediatek/pinctrl-paris.c | 20 ++--
1 file changed
PE")
- pin: 34
bias: "pull-up"
- pin: 34
bias: "pull-down"
- pin: 34
bias: "disabled"
[2] https://github.com/kernelci/platform-test-parameters
Signed-off-by: Nícolas F. R. A. Prado
---
Nícolas F. R. A. Prado (3):
pinctrl: mediatek: paris: Expose
ck so that the remapping is only attempted if the memory region
exists. This also allows to simplify the logic handling failure to
remap, since a failure then is always a failure.
Fixes: ca23ecfdbd44 ("remoteproc/mediatek: support L1TCM")
Signed-off-by: Nícolas F. R. A. Prado
---
dri
On Thu, Jun 06, 2024 at 12:50:56PM +0200, AngeloGioacchino Del Regno wrote:
> Il 05/06/24 21:35, Nícolas F. R. A. Prado ha scritto:
> > The scp_get() helper has two users: the mtk-vcodec and the mtk-mdp3
> > drivers. mdp3 considers the mediatek,scp phandle optional, and when it
to:
mtk-mdp3 14001000.dma-controller: can't get SCP node
Signed-off-by: Nícolas F. R. A. Prado
---
drivers/remoteproc/mtk_scp.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/remoteproc/mtk_scp.c b/drivers/remoteproc/mtk_scp.c
index b885a9a041e4..f813117b6312
Em 2021-02-11 16:57, Mauro Carvalho Chehab escreveu:
>
> Em Thu, 11 Feb 2021 18:10:36 +0000
> Nícolas F. R. A. Prado escreveu:
>
> > Print warning when automarkup fails to cross-reference to another
> > document, so that it doesn't fail silently.
> >
> &
Print warning when automarkup fails to cross-reference to another
document, so that it doesn't fail silently.
Signed-off-by: Nícolas F. R. A. Prado
---
This patch is marked as RFC because it causes a lot of new warnings currently.
So the patch should only be applied after we reduce this to
Em Thu Feb 4, 2021 at 8:28 PM -03, Jonathan Corbet escreveu:
>
> Nícolas F. R. A. Prado writes:
>
> > As Jon previously noted [1], it would be nice if automarkup supported
> > relative
> > paths as well when cross-referencing to other documents. This adds the
e reverted without the link stopping to work.
[1] https://lore.kernel.org/linux-doc/20201130142404.6ef66...@lwn.net/
Nícolas F. R. A. Prado (2):
docs: Enable usage of relative paths to docs on automarkup
docs: Document cross-referencing using relative path
Documentation/doc-guide/sphin
Update the Cross-referencing section to explain how to create a
cross-reference to a document using relative paths and with no
additional syntax, by relying on automarkup.py.
Signed-off-by: Nícolas F. R. A. Prado
---
Documentation/doc-guide/sphinx.rst | 30 --
1 file
still needs to start from Documentation, like Documentation/filename.rst.
As part of this change, the .rst extension is now required for both
types of paths, since not requiring it would cause the regex to be too
generic.
Suggested-by: Jonathan Corbet
Signed-off-by: Nícolas F. R. A. Prado
Add the necessary devicetree nodes for the Qualcomm SPMI Flash LEDs
present in PM8941.
Signed-off-by: Nícolas F. R. A. Prado
---
Changes in v2:
- Moved from hammerhead dts to pm8941 dtsi, as it was this way downstream
- Now using values from leds-qcom-spmi-flash.h
arch/arm/boot/dts/qcom-pm8941
Add driver for the Qualcomm SPMI Flash LEDs. These are controlled
through an SPMI bus and are part of the PM8941 PMIC. There are two LEDs
present in the chip, and can be used independently as camera flash or
together in torch mode to act as a lantern.
Signed-off-by: Nícolas F. R. A. Prado
Enable module for the Qualcomm SPMI Flash LEDs present on the PM8941
PMIC.
Signed-off-by: Nícolas F. R. A. Prado
---
Changes in v2:
- Enabled CONFIG_LEDS_CLASS_FLASH since the driver now depends on it.
arch/arm/configs/qcom_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch
Add devicetree binding for QCOM SPMI Flash LEDs, which are part of
PM8941, and are used both as lantern and camera flash.
Signed-off-by: Nícolas F. R. A. Prado
---
Changes in v2:
- Add this commit
.../bindings/leds/leds-qcom-spmi-flash.yaml | 94 +++
.../dt-bindings/leds/leds
_lge_hammerhead/blob/n7.1/drivers/leds/leds-qpnp.c
Nícolas F. R. A. Prado (4):
dt-bindings: leds: Add binding for qcom-spmi-flash
leds: Add driver for QCOM SPMI Flash LEDs
ARM: qcom_defconfig: Enable QCOM SPMI Flash LEDs
ARM: dts: qcom: pm8941: Add nodes for QCOM SPMI Flash LEDs
..
On Fri, Dec 11, 2020 at 05:03:50PM -0700, Jonathan Corbet wrote:
> The right solution is probably something like this:
>
> try:
> import rst2pdf
> extensions.append('rst2pdf.pdfbuilder')
> except ModuleNotFoundError:
> pass # no rst2pdf for you
I tested i
t;)
Fixes: 7ddedebb03b7 ("ALSA: doc: ReSTize writing-an-alsa-driver document")
Signed-off-by: Nícolas F. R. A. Prado
Reviewed-by: Takashi Iwai
---
Changes in v2:
- Thanks to Mauro:
- Simplify the syntax of some links by taking advantage of docutils'
case-insensitivity when deal
On Sun Dec 27, 2020 at 6:59 AM -03, Mauro Carvalho Chehab wrote:
> Well, docutils define two types of references at:
>
> https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#reference-names
>
> The first one are "simple reference names", defined as:
>
> ``Simple reference names are si
cking to ReST")
Fixes: 7ddedebb03b7 ("ALSA: doc: ReSTize writing-an-alsa-driver document")
Signed-off-by: Nícolas F. R. A. Prado
---
.../Tree-RCU-Memory-Ordering.rst | 8
.../RCU/Design/Requirements/Requirements.rst | 20 +--
Documentation/k
On Fri, Oct 30, 2020 at 08:40:27AM +0100, Mauro Carvalho Chehab wrote:
> The same filename may exist on multiple directories within
> ABI. Create separate entries at the internal database for
> each of them.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> scripts/get_abi.pl | 15 ++-
Use full path to reference writing-schema.rst so that it becomes a
cross-reference.
Signed-off-by: Nícolas F. R. A. Prado
---
Hi Jon,
do you think this would be the way to go, or should we instead extend automarkup
to work on relative paths to doc pages, so that this reference would work as is
On Wed Nov 18, 2020 at 5:37 PM -03, Jonathan Corbet wrote:
>
> On Tue, 17 Nov 2020 02:12:01 +0000
> Nícolas F. R. A. Prado wrote:
>
> > Sphinx 3.1 introduced namespaces for C cross-references. With this,
> > each C domain type/function declaration is put inside the names
On Tue Nov 17, 2020 at 2:47 AM -03, Mauro Carvalho Chehab wrote:
>
> Em Tue, 17 Nov 2020 02:12:01 +0000
> Nícolas F. R. A. Prado escreveu:
>
> > Sphinx 3.1 introduced namespaces for C cross-references. With this,
> > each C domain type/function declaration is put inside th
had a C namespace Sphinx
directive, and if so, try cross-referencing inside of it before going to
the global scope.
This assumes there's only one namespace (if any) per rst file.
Signed-off-by: Nícolas F. R. A. Prado
---
To those following from v1:
I ended up doing the simplest sol
Add the necessary device tree nodes for the flash LED.
Signed-off-by: Nícolas F. R. A. Prado
---
.../qcom-msm8974-lge-nexus5-hammerhead.dts| 56 +++
1 file changed, 56 insertions(+)
diff --git a/arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dts
b/arch/arm/boot/dts
Add support for the flash LED on msm8974 devices, like the Nexus 5.
Signed-off-by: Nícolas F. R. A. Prado
---
arch/arm/configs/qcom_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/qcom_defconfig b/arch/arm/configs/qcom_defconfig
index e1c65a8dd2af..19934d92e3a7
/arm/boot/dts/msm-pm8941.dtsi
[4]
https://github.com/AICP/kernel_lge_hammerhead/blob/n7.1/arch/arm/boot/dts/msm8974-leds.dtsi
My tree: https://gitlab.com/nfraprado/linux/
Nícolas F. R. A. Prado (3):
leds: Add driver for QPNP flash led
ARM: qcom_defconfig: Add QPNP flash LED support
ARM: dts:
Add driver for the QPNP flash LED. It works over SPMI and is part of the
PM8941 PMIC.
Signed-off-by: Nícolas F. R. A. Prado
---
drivers/leds/Kconfig |9 +
drivers/leds/Makefile|1 +
drivers/leds/leds-qpnp.c | 1351 ++
3 files changed, 1361
On Wed Oct 14, 2020 at 4:19 PM -03, Jonathan Corbet wrote:
>
> On Wed, 14 Oct 2020 11:56:44 +0200
> Mauro Carvalho Chehab wrote:
>
> > > To make the first step possible, disable the parallel_read_safe option
> > > in Sphinx, since the dictionary that maps the files to the C namespaces
> > > can't
On Fri Oct 30, 2020 at 11:39 AM -03, Matthew Wilcox wrote:
>
> On Fri, Oct 30, 2020 at 08:14:40AM -0600, Jonathan Corbet wrote:
> > On Fri, 30 Oct 2020 15:10:26 +0100
> > Mauro Carvalho Chehab wrote:
> >
> > > I see a few alternatives:
> > >
> > > 1) fix automarkup.py for it to work again with pyt
On Wed Oct 14, 2020 at 4:11 PM -03, Jonathan Corbet wrote:
>
> On Tue, 13 Oct 2020 23:13:17 +0000
> Nícolas F. R. A. Prado wrote:
>
> > The warnings were caused by the expressions matching words in the
> > translated versions of the documentation, since any unicode c
for the missing functionalities
Nícolas F. R. A. Prado (5):
docs: automarkup.py: Use new C roles in Sphinx 3
docs: automarkup.py: Fix regexes to solve sphinx 3 warnings
docs: automarkup.py: Skip C reserved words when cross-referencing
docs: automarkup.py: Add cross-reference for parame
C regexes use ASCII and
ensuring the expressions only match the beginning of words.
Signed-off-by: Nícolas F. R. A. Prado
---
Documentation/sphinx/automarkup.py | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/sphinx/automarkup.py
b/Documentation/sphinx
: Nícolas F. R. A. Prado
---
Documentation/sphinx/automarkup.py | 49 +-
1 file changed, 42 insertions(+), 7 deletions(-)
diff --git a/Documentation/sphinx/automarkup.py
b/Documentation/sphinx/automarkup.py
index 1cc3a2cf2a88..409dbc4100de 100644
--- a/Documentation
While Sphinx 2 used a single c:type role for struct, union, enum and
typedef, Sphinx 3 uses a specific role for each one.
To keep backward compatibility, detect the Sphinx version and use the
correct roles for that version.
Signed-off-by: Nícolas F. R. A. Prado
---
Documentation/sphinx
parallel_read_safe option
in Sphinx, since the dictionary that maps the files to the C namespaces
can't be concurrently updated. This unfortunately increases the build
time of the documentation.
Signed-off-by: Nícolas F. R. A. Prado
---
Documentation/sphinx/automarkup.py | 130 ++-
Sphinx 3, generating a warning.
Add some C reserved words (only the ones that were causing warnings) to
a list and skip them while trying to cross-reference.
Signed-off-by: Nícolas F. R. A. Prado
---
Documentation/sphinx/automarkup.py | 9 -
1 file changed, 8 insertions(+), 1 delet
On Thu Oct 8, 2020 at 2:27 AM -03, Mauro Carvalho Chehab wrote:
>
> Hi Nícolas,
>
> Em Wed, 07 Oct 2020 23:12:25 +0000
> Nícolas F. R. A. Prado escreveu:
>
> > While Sphinx 2 used a single c:type role for struct, union, enum and
> > typedef, Sphinx 3 uses a specific
On Wed Oct 7, 2020 at 8:40 PM -03, Matthew Wilcox wrote:
>
> On Wed, Oct 07, 2020 at 11:12:25PM +, Nícolas F. R. A. Prado wrote:
> > While Sphinx 2 used a single c:type role for struct, union, enum and
> > typedef, Sphinx 3 uses a specific role for each one.
> > To kee
,
exposing issues in the parsing.
To fix the warnings, make the C regexes use ASCII, ensure the
expressions only match the beginning of words and skip trying to
cross-reference C reserved words.
Signed-off-by: Nícolas F. R. A. Prado
---
Hi,
after Mauro's series making everything ready for S
The syntax to cross-reference between documentation pages wasn't
documented anywhere.
Document the cross-referencing using the new automarkup for
Documentation/... and also Sphinx's doc directive for using relative
paths.
Signed-off-by: Nícolas F. R. A. Prado
---
Documentation
the way from the Documentation
folder, which can be longer than passing a relative path through the
:doc: directive, but avoids the markup, making the text cleaner when
read in plain text.
Signed-off-by: Nícolas F. R. A. Prado
---
Documentation/sphinx/automarkup.py | 39
functions to treat each of them.
Signed-off-by: Nícolas F. R. A. Prado
---
Documentation/sphinx/automarkup.py | 97 +-
1 file changed, 55 insertions(+), 42 deletions(-)
diff --git a/Documentation/sphinx/automarkup.py
b/Documentation/sphinx/automarkup.py
index
olas
[1]:
https://lore.kernel.org/linux-doc/20200903005747.3900333-1-nfrapr...@protonmail.com/
Nícolas F. R. A. Prado (3):
docs: Allow multiple automarkup functions
docs: Add automatic cross-reference for documentation pages
docs: Document cross-referencing between documentation pages
Documentation/d
-by: Jonathan Corbet
Signed-off-by: Nícolas F. R. A. Prado
---
Hi,
Is this documentation page still relevant or should it be removed? I'm asking
since it hasn't been updated in a while and there's mention of 2.6 kernel.
In case it is still relevant, would patches changing the emb
s merged I intend to start removing the occurrences of :c:type.
Thanks,
Nícolas
Nícolas F. R. A. Prado (2):
docs: Add automatic cross-reference for C types
kernel-doc: Update "cross-referencing from rST" section to use
automarkup
Documentation/doc-guid
truct|union|enum|typedef type_name" expression.
This makes the documentation's plain text cleaner and adds
cross-reference to types without any additional effort by the author.
Signed-off-by: Nícolas F. R. A. Prado
---
Documentation/sphinx/automarkup.py | 37 +++---
Update text and examples in the "Cross-referencing from
reStructuredText" section to reflect that no additional syntax is needed
anymore.
Signed-off-by: Nícolas F. R. A. Prado
---
Documentation/doc-guide/kernel-doc.rst | 33 +-
1 file changed, 17 inserti
A function definition argument should have an identifier name according
to checkpatch:
WARNING: function definition argument 'struct platform_device *' should
also have an identifier name
Name it pdev as that name is already used throughout the code.
Signed-off-by: Nícolas F. R
. R. A. Prado
---
Changes in v4:
None
Changes in v3:
- Use VIMC_PIX_FMT_MAX_CODES define instead of hardcoded value for the size of
code array in struct vimc_pix_map
Changes in v2:
- Fix array formatting
- Change commit message to reflect v2 changes
- Change code array size
- Add other BGR888
Add support for RGB888_*, BGR888_* and GBR888_* media bus formats on
the source pad of debayer subdevices.
Acked-by: Helen Koike
Co-developed-by: Vitor Massaru Iha
Signed-off-by: Vitor Massaru Iha
Signed-off-by: Nícolas F. R. A. Prado
---
Changes in v4:
- Rename
Change vimc_pix_map_list to allow multiple media bus codes to map to the
same pixelformat, making it possible to add media bus codes for which
there are no pixelformat.
Acked-by: Helen Koike
Signed-off-by: Nícolas F. R. A. Prado
---
Changes in v4:
None
Changes in v3:
- Make loop in
u can find v1 here: https://patchwork.linuxtv.org/cover/61391/
Nícolas F. R. A. Prado (3):
media: vimc: Support multiple media bus codes for each pixelformat
media: vimc: Add missing {RGB,BGR,GBR}888 media bus codes
media: vimc: deb: Add support for {RGB,BGR,GBR}888 bus formats on
On Tue, Apr 28, 2020 at 09:25:25AM -0300, Helen Koike wrote:
>
> Hello,
>
> On 4/28/20 4:46 AM, Dafna Hirschfeld wrote:
> > hi,
> > Thanks for the patches!
> >
> > On 28.04.20 01:03, Nícolas F. R. A. Prado wrote:
> >> Add support for RGB888_*, BGR888
mbus
codes for the same pixelformat in vimc_pix_map.
These changes were tested with
v4l2-compliance SHA: 3f806630e2ecbcebe31872b865c5c4b42f111a99, 64 bits
and passed all tests:
Grand Total for vimc device /dev/media0: 451, Succeeded: 451, Failed: 0,
Warnings: 0
Signed-off-by: Nícolas F. R. A
mbus
codes for the same pixelformat in vimc_pix_map.
These changes were tested with
v4l2-compliance SHA: 3f806630e2ecbcebe31872b865c5c4b42f111a99, 64 bits
and passed all tests:
Grand Total for vimc device /dev/media0: 451, Succeeded: 451, Failed: 0,
Warnings: 0
Signed-off-by: Nícolas F. R. A
82 matches
Mail list logo
