.
Now I would like to work on fixing this. Mauro suggested the firmware
might
be incorrect. Any tips on extracting the firmware? I can try and dump
usb traffic from Windows and see what firmware is being used there.
How did
you extract the firmware?
If the receiver has onboard firmware, isn&#
fixing this. Mauro suggested the firmware
might
be incorrect. Any tips on extracting the firmware? I can try and dump
usb traffic from Windows and see what firmware is being used there.
How did
you extract the firmware?
If the receiver has onboard firmware, isn't that the right one? The
Hello,
On 10/17/19 12:08 PM, Sean Young wrote:
Hi Antti,
I have a Logilink VG0022A device which is an af9035.c type device (with
ITE 9xxx frontned). The probe of the si2146 tuner fails and returns 0xffs.
Now I would like to work on fixing this. Mauro suggested the firmware might
be incorrect
Hi Antti,
I have a Logilink VG0022A device which is an af9035.c type device (with
ITE 9xxx frontned). The probe of the si2146 tuner fails and returns 0xffs.
Now I would like to work on fixing this. Mauro suggested the firmware might
be incorrect. Any tips on extracting the firmware? I can try
Use the newly introduced helper to parse properties from firmware and
register the associated v4l2 control.
Signed-off-by: Jacopo Mondi
---
drivers/media/i2c/ov5670.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/media/i2c/ov5670.c b/drivers/media/i2c/ov5670.c
index
Use the newly introduced helper to parse properties from firmware and
register the associated v4l2 control.
Signed-off-by: Jacopo Mondi
---
drivers/media/i2c/ov13858.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/media/i2c/ov13858.c b/drivers/media/i2c/ov13858.c
index
Instead of using the convenience function
v4l2_async_notifier_parse_fwnode_endpoints(), parse the endpoints and set
up the async sub-devices without using callbacks. While this adds a little
bit of code, it makes parsing the endpoints quite a bit more simple and
gives more control to the driver ove
Hi Jacopo,
On Fri, Jun 14, 2019 at 06:31:42PM +0200, Jacopo Mondi wrote:
> Hi Sakari,
>
> On Thu, Jun 06, 2019 at 04:02:25PM +0300, Sakari Ailus wrote:
> > Instead of using the convenience function
> > v4l2_async_notifier_parse_fwnode_endpoints(), parse the endpoints and set
> > up the async sub-
Instead of using the convenience function
v4l2_async_notifier_parse_fwnode_endpoints(), parse the endpoints and set
up the async sub-devices without using callbacks. While this adds a little
bit of code, it makes parsing the endpoints quite a bit more simple and
gives more control to the driver ove
Hi Sakari,
On Thu, Jun 06, 2019 at 04:02:25PM +0300, Sakari Ailus wrote:
> Instead of using the convenience function
> v4l2_async_notifier_parse_fwnode_endpoints(), parse the endpoints and set
> up the async sub-devices without using callbacks. While this adds a little
> bit of code, it makes pars
Instead of using the convenience function
v4l2_async_notifier_parse_fwnode_endpoints(), parse the endpoints and set
up the async sub-devices without using callbacks. While this adds a little
bit of code, it makes parsing the endpoints quite a bit more simple and
gives more control to the driver ove
_off: The driver supports its probe function being called
> > while
> > + *the device is powered off, independently of the expected
> > + *behaviour on combination of a given bus and firmware
> > + *interface etc. The driver is respo
On Friday, May 10, 2019 12:09:26 PM CEST Sakari Ailus wrote:
> Allow drivers and firmware tell ACPI that there's no need to power on a
> device for probe. This requires both a hint from the firmware as well as
> an indication from a driver to leave the device off.
>
> Signed-
Allow drivers and firmware tell ACPI that there's no need to power on a
device for probe. This requires both a hint from the firmware as well as
an indication from a driver to leave the device off.
Signed-off-by: Sakari Ailus
---
drivers/acpi/device_pm.c | 9 +++--
include/linux/dev
inx ZynqMP. The driver depends on a firmware for the
> > video codec [1], which is the same firmware that is used by the
> > downstream VCU driver.
> >
> > As the license allows to distribute the binary, it should be fine to
> > include the firmware in the linu
Hi Varunkumar,
On Thu, 28 Mar 2019 11:32:45 +0100, Michael Tretter wrote:
> Hi Varunkumar,
>
> I am working on a mainline driver [0] for the VCU/video-codec that is
> found on the Xilinx ZynqMP. The driver depends on a firmware for the
> video codec [1], which is the same firmwa
Instead of using the convenience function
v4l2_async_notifier_parse_fwnode_endpoints(), parse the endpoints and set
up the async sub-devices without using callbacks. While this adds a little
bit of code, it makes parsing the endpoints quite a bit more simple and
gives more control to the driver ove
On Mon, Apr 1, 2019 at 10:05 PM Yunfei Dong wrote:
>
> Hi linux-firmware maintainers,
>
> The following changes since commit 7bc246451318b3536d9bfd3c4e46d541a9831b33:
>
> Merge branch 'for-upstream' of git://git.chelsio.net/pub/git/linux-firmware
> (2019-03-14 08
Release Version: 1.1.2
Signed-off-by: Yunfei Dong
---
vpu_d.bin | Bin 2977008 -> 2977008 bytes
vpu_p.bin | Bin 131168 -> 131180 bytes
2 files changed, 0 insertions(+), 0 deletions(-)
diff --git a/vpu_d.bin b/vpu_d.bin
index
f1a552edfc168973acc1d219db19e60f354daae0..a04dd793a7cbc88e633bee80
Hi linux-firmware maintainers,
The following changes since commit 7bc246451318b3536d9bfd3c4e46d541a9831b33:
Merge branch 'for-upstream' of git://git.chelsio.net/pub/git/linux-firmware
(2019-03-14 08:22:39 -0400)
are available in the git repository at:
https://github.com/y
Hi linux-firmware maintainers,
The following changes since commit 7bc246451318b3536d9bfd3c4e46d541a9831b33:
Merge branch 'for-upstream' of git://git.chelsio.net/pub/git/linux-firmware
(2019-03-14 08:22:39 -0400)
are available in the git repository at:
https://github.com/y
Hi Varunkumar,
I am working on a mainline driver [0] for the VCU/video-codec that is
found on the Xilinx ZynqMP. The driver depends on a firmware for the
video codec [1], which is the same firmware that is used by the
downstream VCU driver.
As the license allows to distribute the binary, it
Instead of using the convenience function
v4l2_async_notifier_parse_fwnode_endpoints(), parse the endpoints and set
up the async sub-devices without using callbacks. While this adds a little
bit of code, it makes parsing the endpoints quite a bit more simple and
gives more control to the driver ove
The lack of defaults provided by the caller to
v4l2_fwnode_endpoint_parse() signals the use of the default lane mapping.
The default lane mapping must not be used however if the firmmare contains
the lane mapping. Disable the default lane mapping in that case, and
improve the debug messages telling
By historical reasons we defined firmware memory size to be 6MB even
that the firmware size for all supported Venus versions is 5MBs. Correct
that by compare the required firmware size returned from mdt loader and
the one provided by DT reserved memory region. We proceed further if the
required
Hi Alex,
Thanks for the review!
On 1/23/19 8:10 AM, Alexandre Courbot wrote:
> Sorry for the delayed review! >_<
>
> On Wed, Jan 9, 2019 at 5:46 PM Stanimir Varbanov
> wrote:
>>
>> By historical reasons we defined firmware memory size to be 6MB even
>> that
Sorry for the delayed review! >_<
On Wed, Jan 9, 2019 at 5:46 PM Stanimir Varbanov
wrote:
>
> By historical reasons we defined firmware memory size to be 6MB even
> that the firmware size for all supported Venus versions is 5MBs. Correct
> that by compare the required firmware
Hi Alex,
If you have time please review this patch, I'd like to send a pull
request for this series.
On 1/9/19 10:46 AM, Stanimir Varbanov wrote:
> By historical reasons we defined firmware memory size to be 6MB even
> that the firmware size for all supported Venus versions is 5M
By historical reasons we defined firmware memory size to be 6MB even
that the firmware size for all supported Venus versions is 5MBs. Correct
that by compare the required firmware size returned from mdt loader and
the one provided by DT reserved memory region. We proceed further if the
required
From: Sebastian Reichel
All TI WiLink firmware files are loaded from the ti-connectivity
subdirectory, so let's also move the FM firmware.
Signed-off-by: Sebastian Reichel
---
drivers/media/radio/wl128x/fmdrv_common.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --
-dmamap.h"
+
+static void ipu3_css_fw_show_binary(struct device *dev, struct imgu_fw_info
*bi,
+ const char *name)
+{
+ unsigned int i;
+
+ dev_dbg(dev, "found firmware binary type %i size %i name %s\n",
+ bi->type,
The firmware binary is located under "intel" directory in the
linux-firmware repository. Reflect this in the driver.
Signed-off-by: Sakari Ailus
---
drivers/staging/media/ipu3/ipu3-css-fw.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/media/ipu
The firmware binary is located under "intel" directory in the
linux-firmware repository. Reflect this in the driver.
Signed-off-by: Sakari Ailus
---
drivers/staging/media/ipu3/ipu3-css-fw.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/media/ipu
ary(struct device *dev, struct imgu_fw_info
*bi,
+ const char *name)
+{
+ unsigned int i;
+
+ dev_dbg(dev, "found firmware binary type %i size %i name %s\n",
+ bi->type, bi->blob.size, name);
+ if (bi->typ
ipu3/ipu3-css-fw.h
> @@ -0,0 +1,188 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +/* Copyright (C) 2018 Intel Corporation */
> +
> +#ifndef __IPU3_CSS_FW_H
> +#define __IPU3_CSS_FW_H
> +
> +/*** Firmware file definitions ***/
> +
> +#
ary(struct device *dev, struct imgu_fw_info
*bi,
+ const char *name)
+{
+ unsigned int i;
+
+ dev_dbg(dev, "found firmware binary type %i size %i name %s\n",
+ bi->type, bi->blob.size, name);
+ if (bi->typ
Hi Joe,
On 10/18/2018 04:42 AM, Joe Perches wrote:
> On Wed, 2018-10-17 at 11:49 +0300, Stanimir Varbanov wrote:
>> On 10/08/2018 04:32 PM, Vikash Garodia wrote:
>>> Add routine to reset the ARM9 and brings it out of reset. Also
>>> abstract the Venus CPU state handling with a new function. This
>
On Wed, 2018-10-17 at 11:49 +0300, Stanimir Varbanov wrote:
> On 10/08/2018 04:32 PM, Vikash Garodia wrote:
> > Add routine to reset the ARM9 and brings it out of reset. Also
> > abstract the Venus CPU state handling with a new function. This
> > is in preparation to add PIL functionality in venus
Video hardware is mainly comprised of vcodec subsystem and video
control subsystem. Video control has ARM9 which executes the video
firmware instructions whereas vcodec does the video frame processing.
This change adds support to load the video firmware and bring ARM9
out of reset for platforms
Add devicetree binding documentation for firmware loader for video
hardware running on qualcomm chip.
Signed-off-by: Vikash Garodia
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/media/qcom,venus.txt | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff
From: Stanimir Varbanov
This registers a firmware platform_device and associate it with
video-firmware DT subnode. Then calls dma configure to initialize
dma and iommu.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/core.c | 14 +--
drivers/media/platform/qcom
Separate firmware loading part into a new function.
Signed-off-by: Vikash Garodia
---
drivers/media/platform/qcom/venus/core.c | 4 +-
drivers/media/platform/qcom/venus/firmware.c | 55 ++--
drivers/media/platform/qcom/venus/firmware.h | 2 +-
3 files changed, 38
Add routine to reset the ARM9 and brings it out of reset. Also
abstract the Venus CPU state handling with a new function. This
is in preparation to add PIL functionality in venus driver.
Signed-off-by: Vikash Garodia
---
drivers/media/platform/qcom/venus/core.h | 2 ++
drivers/media/pla
Hi Vikash,
On 10/08/2018 04:32 PM, Vikash Garodia wrote:
> Add routine to reset the ARM9 and brings it out of reset. Also
> abstract the Venus CPU state handling with a new function. This
> is in preparation to add PIL functionality in venus driver.
>
> Signed-off-by: Vikash Garodia
> ---
> dri
The DMA API does its own zone decisions based on the coherent_dma_mask.
Signed-off-by: Christoph Hellwig
---
drivers/firmware/tegra/bpmp-debugfs.c | 11 +--
drivers/firmware/tegra/bpmp.c | 2 +-
2 files changed, 6 insertions(+), 7 deletions(-)
diff --git a/drivers/firmware
Add devicetree binding documentation for firmware loader for video
hardware running on qualcomm chip.
Signed-off-by: Vikash Garodia
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/media/qcom,venus.txt | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff
Video hardware is mainly comprised of vcodec subsystem and video
control subsystem. Video control has ARM9 which executes the video
firmware instructions whereas vcodec does the video frame processing.
This change adds support to load the video firmware and bring ARM9
out of reset for platforms
From: Stanimir Varbanov
This registers a firmware platform_device and associate it with
video-firmware DT subnode. Then calls dma configure to initialize
dma and iommu.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/core.c | 14 +--
drivers/media/platform/qcom
Separate firmware loading part into a new function.
Signed-off-by: Vikash Garodia
---
drivers/media/platform/qcom/venus/core.c | 4 +-
drivers/media/platform/qcom/venus/firmware.c | 55 ++--
drivers/media/platform/qcom/venus/firmware.h | 2 +-
3 files changed, 38
Add routine to reset the ARM9 and brings it out of reset. Also
abstract the Venus CPU state handling with a new function. This
is in preparation to add PIL functionality in venus driver.
Signed-off-by: Vikash Garodia
---
drivers/media/platform/qcom/venus/core.h | 2 ++
drivers/media/pla
From: Stanimir Varbanov
This registers a firmware platform_device and associate it with
video-firmware DT subnode. Then calls dma configure to initialize
dma and iommu.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/core.c | 14 +--
drivers/media/platform/qcom
Add devicetree binding documentation for firmware loader for video
hardware running on qualcomm chip.
Signed-off-by: Vikash Garodia
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/media/qcom,venus.txt | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff
Video hardware is mainly comprised of vcodec subsystem and video
control subsystem. Video control has ARM9 which executes the video
firmware instructions whereas vcodec does the video frame processing.
This change adds support to load the video firmware and bring ARM9
out of reset for platforms
Add routine to reset the ARM9 and brings it out of reset. Also
abstract the Venus CPU state handling with a new function. This
is in preparation to add PIL functionality in venus driver.
Signed-off-by: Vikash Garodia
---
drivers/media/platform/qcom/venus/core.h | 2 ++
drivers/media/pla
Separate firmware loading part into a new function.
Signed-off-by: Vikash Garodia
---
drivers/media/platform/qcom/venus/core.c | 4 +-
drivers/media/platform/qcom/venus/firmware.c | 55 ++--
drivers/media/platform/qcom/venus/firmware.h | 2 +-
3 files changed, 38
/hardkernel/linux/blob/odroidc2-3.14.y/drivers/amlogic/amports/arch/ucode/mpeg12/vmpeg12_mc.c
> >
> > The corresponding driver is currently being upstreamed:
> > https://lore.kernel.org/patchwork/cover/993093/
> >
> > Regards,
> > Maxime
> >
> > The followi
rresponding driver is currently being upstreamed:
> https://lore.kernel.org/patchwork/cover/993093/
>
> Regards,
> Maxime
>
> The following changes since commit 7c81f23ad903f72e87e2102d8f52408305c0f7a2:
>
> ti-connectivity: add firmware for CC2560(A) Bluetooth (2018-10-01 10:08:30
>
es since commit 7c81f23ad903f72e87e2102d8f52408305c0f7a2:
ti-connectivity: add firmware for CC2560(A) Bluetooth (2018-10-01 10:08:30
-0400)
are available in the Git repository at:
https://github.com/Elyotna/linux-firmware.git
for you to fetch changes up to b99cf8dcfb6e7a3dd00bdb6aa
rry W
> ; Zheng, Jian Xu
> Subject: Re: [PATCH v6 06/12] intel-ipu3: css: Add support for firmware
> management
>
> Hi Yong,
>
> On Wed, Sep 19, 2018 at 10:57:55PM +, Zhi, Yong wrote:
> ...
> > > > +struct imgu_abi_osys_frame_params {
>
Hi Yong,
On Wed, Sep 19, 2018 at 10:57:55PM +, Zhi, Yong wrote:
...
> > > +struct imgu_abi_osys_frame_params {
> > > + /* Output pins */
> > > + __u32 enable;
> > > + __u32 format; /* enum imgu_abi_osys_format */
> > > + __u32 flip;
> > > + __u32 mirror;
> ; Toivonen, Tuukka
> ; Hu, Jerry W ; Zheng,
> Jian Xu
> Subject: Re: [PATCH v6 06/12] intel-ipu3: css: Add support for firmware
> management
>
> Hi Yong,
>
> Continuing my review. Sorry for the delay.
>
> On Fri, Mar 30, 2018 at 11:15 AM Yong Zhi wrote:
> &g
Hi Stanimir,
On 2018-08-22 18:07, Stanimir Varbanov wrote:
Hi Vikash,
Could you give a try below patch on your environment? You should keep
your 1/4 to 3/4 patches and replace your 4/4 with the below one.
You have to drop the compatible string in firmware DT subnode (keep
only
iommus).
I
Hi Vikash,
Could you give a try below patch on your environment? You should keep
your 1/4 to 3/4 patches and replace your 4/4 with the below one.
You have to drop the compatible string in firmware DT subnode (keep only
iommus).
On 08/22/2018 03:34 PM, Stanimir Varbanov wrote:
> This register
This registers a firmware platform_device and associate it with
video-firmware DT subnode. Then calls dma configure to initialize
dma and iommu.
Signed-off-by: Stanimir Varbanov
---
.../devicetree/bindings/media/qcom,venus.txt | 13 +-
drivers/media/platform/qcom/venus/core.c
On Fri, Aug 10, 2018 at 5:44 AM Vikash Garodia wrote:
>
> hi,
>
> This pull request updates firmware files for Venus h/w codec found on the
> Qualcomm SDM845 chipset.
>
> The following changes since commit 7b5835fd37630d18ac0c755329172f6a17c1af29:
>
> linux-firmwar
hi,
This pull request updates firmware files for Venus h/w codec found on the
Qualcomm SDM845 chipset.
The following changes since commit 7b5835fd37630d18ac0c755329172f6a17c1af29:
linux-firmware: add firmware for mt76x2u (2018-07-30 07:20:31 -0400)
are available in the git repository at
Hi,
On 07/04/2018 10:06 PM, Vikash Garodia wrote:
> Add routine to reset the ARM9 and brings it out of reset. Also
> abstract the Venus CPU state handling with a new function. This
> is in preparation to add PIL functionality in venus driver.
>
> Signed-off-by: Vikash Garodia
> ---
> drivers/me
Hi Vikash,
On 07/04/2018 10:06 PM, Vikash Garodia wrote:
> Video hardware is mainly comprised of vcodec subsystem and video
> control subsystem. Video control has ARM9 which executes the video
> firmware instructions whereas vcodec does the video frame processing.
> This change add
Hi Vikash,
On 07/04/2018 10:06 PM, Vikash Garodia wrote:
> Separate firmware loading part into a new function.
I cannot apply this patch in order to test the series.
>
> Signed-off-by: Vikash Garodia
> ---
> drivers/media/platform/qcom/venus/core.c | 4 +-
> drivers/m
end as it is done in the function prototype in firmware.h.
> +{
> + void __iomem *base = core->base;
> +
> + if (!core->no_tz)
> + return qcom_scm_set_remote_state(resume, 0);
> +
> + if (resume)
> + venus_reset_cpu(core);
> +
When encoding h.264, if visible resolution is not aligned to macroblock
size, frame cropping has to be set in the SPS header to produce correct
streams. The CODA960 firmware can do this on its own if asked to.
Signed-off-by: Philipp Zabel
---
drivers/media/platform/coda/coda-bit.c | 19
input circuit can only be done at the
> +* start of a session. It is illegal to program it during execution
> +* The input circuit defines the connectivity
> +*/
> + u8 program_input_circuit;
> + u8 func;
> +#define IMGU_ABI_STAGE_FUNC_
This patch adds the i.MX6 CODA960 firmware versions 2.1.9
(revision 32515) to the list of supported firmware versions.
Signed-off-by: Philipp Zabel
---
drivers/media/platform/coda/coda-bit.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/platform/coda/coda-bit.c
b/drivers
On Sat, May 26, 2018 at 4:18 AM Vikash Garodia wrote:
>
> Hi Josh,
>
> On 2018-05-25 17:34, Josh Boyer wrote:
> > On Fri, May 25, 2018 at 7:03 AM Vikash Garodia
> >
> > wrote:
> >
> >> This pull request adds firmware files for Venus h/w c
Hi Josh,
On 2018-05-25 17:34, Josh Boyer wrote:
On Fri, May 25, 2018 at 7:03 AM Vikash Garodia
wrote:
This pull request adds firmware files for Venus h/w codec found on the
Qualcomm SDM845 chipset.
The following changes since commit
2a9b2cf50fb32e36e4fc1586c2f6f1421913b553:
Merge
On Fri, May 25, 2018 at 7:03 AM Vikash Garodia
wrote:
> This pull request adds firmware files for Venus h/w codec found on the
Qualcomm SDM845 chipset.
> The following changes since commit
2a9b2cf50fb32e36e4fc1586c2f6f1421913b553:
>Merge branch 'for-upstreaming-v1
This pull request adds firmware files for Venus h/w codec found on the Qualcomm
SDM845 chipset.
The following changes since commit 2a9b2cf50fb32e36e4fc1586c2f6f1421913b553:
Merge branch 'for-upstreaming-v1.7.2' of
https://github.com/felix-cavium/linux-firmware (2018-05-18 08:3
hi,
This pull request adds firmware files for Venus h/w codec found on the Qualcomm
SDM845 chipset.
The following changes since commit 2a9b2cf50fb32e36e4fc1586c2f6f1421913b553:
Merge branch 'for-upstreaming-v1.7.2' of
https://github.com/felix-cavium/linux-firmware (2018-05-18 08:3
u32 p2_x;
+ __u32 p2_y;
+ __u32 p3_x;
+ __u32 p3_y;
+ __u32 in_block_width_a;
+ __u32 in_block_width_b;
+ __u32 padding; /* struct size multiple of DDR word */
+} __packed;
+
+/*** Firmware ABI definitions **
irmware_checksum >> 0) & 0xff;
- ret = af9015_read_reg_i2c(d, state->af9013_i2c_addr[1],
- 0x98be, &val);
+ /* Check whether firmware is already running */
+ ret = af9015_read_reg_i2c(d, state->af9013_i2c_addr[1], 0x98be, &val);
if (ret)
-
,
- const struct firmware *fw)
+ const struct firmware *firmware)
{
struct af9015_state *state = d_to_priv(d);
struct usb_interface *intf = d->intf;
- int i, len, remaining, ret;
+ int ret, i, rem;
struct req_t
On Wed, Jan 17, 2018 at 8:35 AM, wrote:
> The following changes since commit 65b1c68c63f974d72610db38dfae49861117cae2:
>
> wl18xx: update firmware file 8.9.0.0.76 (2018-01-04 10:06:01 -0500)
>
> are available in the git repository at:
>
> https://github.com/pochun-lin/li
The following changes since commit 65b1c68c63f974d72610db38dfae49861117cae2:
wl18xx: update firmware file 8.9.0.0.76 (2018-01-04 10:06:01 -0500)
are available in the git repository at:
https://github.com/pochun-lin/linux_fw_vpu_v1.0.8.git v1.0.8
for you to fetch changes up to
truct imgu_abi_dpc_params {
+ struct imgu_abi_dpc_param0 enable_and_threshold;
+ struct imgu_abi_dpc_num_of_dp num_of_dp_set0;
+ struct imgu_abi_dpc_num_of_dp num_of_dp_set1;
+ struct imgu_abi_dpc_num_of_dp num_of_dp_first_line_pair;
+} __packed;
+
+/*** Firmware ABI defin
On Fri, 2017-11-03 at 13:33 -0700, Dean Anderson wrote:
> Updates the firmware for the s2255drv driver.
> Adds support for NTSC4.43, horizontal/vertical adjustments and
> Motion JPEG capture mode improvements.
>
> Signed-off-by: Dean Anderson
> ---
> f2255usb.bin | Bin 1
Firmware load on AS102 is using the stack which is not allowed any
longer. We currently fail with:
kernel: transfer buffer not dma capable
kernel: [ cut here ]
kernel: WARNING: CPU: 0 PID: 598 at drivers/usb/core/hcd.c:1595
usb_hcd_map_urb_for_dma+0x41d/0x620
kernel
/platform/s5p-mfc/s5p_mfc_ctrl.c
@@ -75,11 +75,6 @@ int s5p_mfc_load_firmware(struct s5p_mfc_dev *dev)
release_firmware(fw_blob);
return -ENOMEM;
}
- if (!dev->fw_buf.virt) {
- mfc_err("MFC firmware is not all
This patch series fixes inefficiencies and lock contention in the request
firmware paths.
Changes since v2:
- Addressed Andre's review comments. Removed fw_buf->virt null check
as it is not needed. Removed handling s5p_mfc_load_firmware() from
probe routine. Simply try loading in
fixes intermittent soft reboot issue with firmware load
increases wait time of reset, as required by HW
Signed-off-by: Dean Anderson
---
drivers/media/usb/s2255/s2255drv.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/drivers/media/usb/s2255
On 11/02/2017 02:12 AM, Andrzej Hajda wrote:
> Hi Shuah,
>
> On 06.10.2017 23:30, Shuah Khan wrote:
>> Check if firmware is allocated before requesting firmware instead of
>> requesting firmware only to release it if firmware is not allocated.
>>
>> Signed-off-b
Hi Shuah,
On 06.10.2017 23:30, Shuah Khan wrote:
> Check if firmware is allocated before requesting firmware instead of
> requesting firmware only to release it if firmware is not allocated.
>
> Signed-off-by: Shuah Khan
> ---
> drivers/media/platform/s5p-mfc/s5p_mfc_ctrl.c |
doesn't have the unused warn problem. I fixed the problem
in media: s5p-mfc: fix lockdep warning patch that has the warning and
sent v2.
> On Thu, Oct 26, 2017 at 7:54 AM, Shuah Khan wrote:
>> On 10/06/2017 03:30 PM, Shuah Khan wrote:
>>> This patch series fixes ineffi
On 09/30/2017 12:15 AM, d...@sensoray.com wrote:
> fixes intermittent soft reboot issue with firmware load
> increases wait time of reset, as required by HW
>
> Signed-off-by: Dean Anderson
>
> ---
> drivers/media/usb/s2255/s2255drv.c | 13 ++---
On 10/25/2017 04:28 PM, Marian Mihailescu wrote:
> Hi Shuah,
>
> For MFC patch, you can delete the "dev" variable since it's not being
> used anymore and results in a compile warning.
>
> - struct s5p_mfc_dev *dev = ctx->dev;
>
> Cheers,
> Marian
Oops. I thought I handled that. I will fix that
wrote:
>> This patch series fixes inefficiencies and lock contention in the request
>> firmware paths.
>>
>> Shuah Khan (2):
>> media: s5p-mfc: check for firmware allocation before requesting
>> firmware
>> media: s5p-mfc: fix lock confection - req
On 10/06/2017 03:30 PM, Shuah Khan wrote:
> This patch series fixes inefficiencies and lock contention in the request
> firmware paths.
>
> Shuah Khan (2):
> media: s5p-mfc: check for firmware allocation before requesting
> firmware
> media: s5p-mfc: fix lock confecti
um_of_dp num_of_dp_set1;
+ struct imgu_abi_dpc_num_of_dp num_of_dp_first_line_pair;
+} __packed;
+
+/*** Firmware ABI definitions ***/
+
+/* struct imgu_abi_sp_stage */
+
+#define IMGU_ABI_BINARY_MAX_OUTPUT_PORTS 2
+
+enum imgu_abi_queue_id {
+
Check if firmware is allocated before requesting firmware instead of
requesting firmware only to release it if firmware is not allocated.
Signed-off-by: Shuah Khan
---
drivers/media/platform/s5p-mfc/s5p_mfc_ctrl.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a
This patch series fixes inefficiencies and lock contention in the request
firmware paths.
Shuah Khan (2):
media: s5p-mfc: check for firmware allocation before requesting
firmware
media: s5p-mfc: fix lock confection - request_firmware() once and keep
state
drivers/media/platform/s5p
On 2017-10-05 17:45, Philipp Zabel wrote:
> On Wed, 2017-10-04 at 10:44 +0200, Martin Kepplinger wrote:
>> Hi,
>>
>> Commit
>>
>> be7f1ab26f42 media: coda: mark CODA960 firmware versions 2.3.10
>> and
>> 3.1.1 as supported
>>
>> s
1 - 100 of 952 matches
Mail list logo
