On 6/16/2020 1:34 AM, Álvaro Fernández Rojas wrote:
> Document BCM63xx USBH PHY bindings.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> .../bindings/phy/brcm,bcm63xx-usbh-phy.yaml | 72 +++
> 1 file changed, 72 insertions(+)
> create mode 100644
>
On 6/16/2020 10:07 AM, Mark Brown wrote:
> On Tue, Jun 16, 2020 at 09:02:21AM +0200, Álvaro Fernández Rojas wrote:
>> bcm63xx-spi controller is present on several BMIPS SoCs (BCM6358, BCM6362,
>> BCM6368 and BCM63268).
>
> Please do not submit new versions of already applied patches, please
>
On 6/16/2020 12:02 AM, Álvaro Fernández Rojas wrote:
> bcm63xx arch resets the HSSPI controller at early boot. However, bmips arch
> needs to perform a reset when probing the driver.
>
> Signed-off-by: Álvaro Fernández Rojas
> Reviewed-by: Philipp Zabel
> ---
Same comment as patch #1.
--
t for you already. You can only do:
if (IS_ERR(reset))
return PTR_ERR(reset);
and that's it. With that fixed in v4, you can add:
Reviewed-by: Florian Fainelli
--
Florian
On 6/15/2020 12:09 PM, Robin Murphy wrote:
> On 2020-06-08 12:41, Lukas Wunner wrote:
>> On Mon, Jun 08, 2020 at 12:11:11PM +0100, Robin Murphy wrote:
>>> And all in code that has at least one obvious inefficiency left on
>>> the table either way.
>>
>> Care to submit a patch to overcome that
On 6/15/2020 10:00 AM, Mark Brown wrote:
> On Mon, Jun 15, 2020 at 09:34:58AM -0700, Florian Fainelli wrote:
>
>> OK, so this has been dropped for spi/for-next right? How do we move from
>> there?
>
> Well, I actually have it queued up for applying so unless I pull it
On 6/8/2020 4:28 AM, Mark Brown wrote:
> On Mon, Jun 08, 2020 at 12:11:11PM +0100, Robin Murphy wrote:
>
>> Again, 2 cycles. The overhead of a static key alone is at least 50% of that.
>> And that's not even considering whether the change in code layout caused by
>> doubling up the IRQ handler
On 6/15/2020 2:17 AM, Álvaro Fernández Rojas wrote:
> Instead of trying to parse CFE version string, which is customized by some
> vendors, let's just check that "CFE1" was passed on argument 3.
>
> Signed-off-by: Álvaro Fernández Rojas
> Signed-off-by: Jonas Gors
Hi Alvaro,
On 6/15/2020 2:09 AM, Álvaro Fernández Rojas wrote:
> BCM63xx SPI and HSSPI controller are present on several BMIPS SoCs (BCM6318,
> BCM6328, BCM6358, BCM6362, BCM6368 and BCM63268).
>
> v2: use devm_reset_control_get_exclusive
We would also need to write a binding document for these
On 6/15/2020 2:09 AM, Álvaro Fernández Rojas wrote:
> bcm63xx-spi controller is present on several BMIPS SoCs (BCM6358, BCM6362,
> BCM6368 and BCM63268).
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
On 6/15/2020 2:09 AM, Álvaro Fernández Rojas wrote:
> bcm63xx-hsspi controller is present on several BMIPS SoCs (BCM6318, BCM6328,
> BCM6362 and BCM63268).
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
On 6/15/2020 2:09 AM, Álvaro Fernández Rojas wrote:
> bcm63xx arch resets the SPI controller at early boot. However, bmips arch
> needs to perform a reset when probing the driver.
>
> Signed-off-by: Álvaro Fernández Rojas
> Reviewed-by: Philipp Zabel
> ---
> v2: use
On 6/13/2020 1:38 AM, Álvaro Fernández Rojas wrote:
> Add support for resetting blocks through the Linux reset controller
> subsystem for BCM63xx SoCs.
>
> Signed-off-by: Álvaro Fernández Rojas
With the kbuild robot error fixed:
Reviewed-by: Florian Fainelli
Thanks!
--
Florian
On 6/13/2020 1:38 AM, Álvaro Fernández Rojas wrote:
> BCM6318 SoCs have a reset controller for certain components.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
On 6/13/2020 1:38 AM, Álvaro Fernández Rojas wrote:
> BCM63268 SoCs have a reset controller for certain components.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
On 6/13/2020 1:21 AM, Álvaro Fernández Rojas wrote:
> BCM63268 SoCs have a power domain controller to enable/disable certain
> components in order to save power.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
On 6/13/2020 1:21 AM, Álvaro Fernández Rojas wrote:
> BCM6318, BCM6328, BCM6362 and BCM63268 SoCs have a power domain controller
> to enable/disable certain components in order to save power.
>
> Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Florian Fainelli
--
Florian
On 6/13/2020 1:21 AM, Álvaro Fernández Rojas wrote:
> BCM6318 SoCs have a power domain controller to enable/disable certain
> components in order to save power.
>
> Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Florian Fainelli
--
Florian
On 6/13/2020 1:21 AM, Álvaro Fernández Rojas wrote:
> BCM63268 SoCs have a power domain controller to enable/disable certain
> components in order to save power.
>
> Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Florian Fainelli
--
Florian
On 6/13/2020 1:21 AM, Álvaro Fernández Rojas wrote:
> BCM6362 SoCs have a power domain controller to enable/disable certain
> components in order to save power.
>
> Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Florian Fainelli
--
Florian
On 6/13/2020 1:21 AM, Álvaro Fernández Rojas wrote:
> BCM6328 SoCs have a power domain controller to enable/disable certain
> components in order to save power.
>
> Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Florian Fainelli
--
Florian
On 6/12/2020 2:57 PM, Rob Herring wrote:
> On Wed, 10 Jun 2020 19:28:52 +0200, Álvaro Fernández Rojas wrote:
>> Add device tree binding documentation for BCM6345 reset controller.
>>
>> Signed-off-by: Álvaro Fernández Rojas
>> Reviewed-by: Florian Fainelli
>>
: Nicolas Saenz Julienne
Reviewed-by: Florian Fainelli
--
Florian
On 6/12/2020 2:49 AM, Marc Zyngier wrote:
> Hi Florian,
>
> On Tue, 19 May 2020 10:50:46 -0700
> Florian Fainelli wrote:
>
>> On 5/19/2020 9:17 AM, Marc Zyngier wrote:
>>> For as long as SMP ARM has existed, IPIs have been handled as
>>> something s
On 6/5/2020 9:24 AM, Florian Fainelli wrote:
> Hi all,
>
> This long patch series was motivated by backporting Jaedon's changes
> which add a proper ioctl compatibility layer for 32-bit applications
> running on 64-bit kernels. We have a number of Android TV-based products
>
at the point of an ERET, this could potentially be used as part of a
side-channel attack.
This patch emits an SB sequence after each ERET so that speculation is
held up on exception return.
Signed-off-by: Will Deacon
[florian: Adjust hyp-entry.S to account for the label]
Signed-off-by: Florian
On 6/11/2020 9:52 AM, Maxime Ripard wrote:
> Hi Stefan,
>
> On Thu, Jun 11, 2020 at 05:50:30PM +0200, Stefan Wahren wrote:
>>> diff --git a/drivers/clk/bcm/clk-bcm2711-dvp.c
>>> b/drivers/clk/bcm/clk-bcm2711-dvp.c
>>> new file mode 100644
>>> index ..84dbc886e303
>>> --- /dev/null
On 6/11/2020 8:16 AM, Álvaro Fernández Rojas wrote:
> Hi Miquel,
>
>> El 11 jun 2020, a las 9:55, Miquel Raynal
>> escribió:
>>
>> Hi Álvaro,
>>
>> Álvaro Fernández Rojas wrote on Mon, 8 Jun 2020
>> 18:06:49 +0200:
>>
>>> Instead of trying to parse CFE version string, which is customized
On 6/10/2020 12:15 PM, Jonathan McDowell wrote:
> This patch improves the handling of the SGMII interface on the QCA8K
> devices. Previously the driver did no configuration of the port, even if
> it was selected. We now configure it up in the appropriate
> PHY/MAC/Base-X mode depending on what
On 6/10/2020 12:14 PM, Jonathan McDowell wrote:
> Update the driver to use the new PHYLINK callbacks, removing the
> legacy adjust_link callback.
>
> Signed-off-by: Jonathan McDowell
This looks reasonable to me, Russell would be the person you want to get
an Acked-by/Reviewed-by tag from.
--
On 6/10/2020 9:32 AM, Álvaro Fernández Rojas wrote:
> BCM6318, BCM6328, BCM6362 and BCM63268 SoCs have a power domain controller
> to enable/disable certain components in order to save power.
>
> Signed-off-by: Álvaro Fernández Rojas
Thanks for addressing the previous comments, this looks
On 6/10/2020 9:32 AM, Álvaro Fernández Rojas wrote:
> BCM6318, BCM6328, BCM6362 and BCM63268 SoCs have a power domain controller
> to enable/disable certain components in order to save power.
>
> v2: Introduce changes suggested by Florian:
> - Add separate YAML file for dt-bindings.
> -
On 6/10/2020 9:32 AM, Álvaro Fernández Rojas wrote:
> BCM6318, BCM6328, BCM6362 and BCM63268 SoCs have a power domain controller
> to enable/disable certain components in order to save power.
>
> Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Florian Fainelli
--
Florian
On 6/9/2020 11:26 PM, Sascha Hauer wrote:
> Hi Andrew,
>
> +Cc Maxime Chevallier
>
> On Tue, Jun 09, 2020 at 03:28:48PM +0200, Andrew Lunn wrote:
>> On Tue, Jun 09, 2020 at 03:11:52PM +0200, Sascha Hauer wrote:
>>> The Marvell MVNETA Ethernet controller supports a 2.5Gbps SGMII mode
>>>
On 6/10/2020 1:29 AM, Philippe Mathieu-Daudé wrote:
> Hi,
>
> On Wed, Jun 10, 2020 at 8:13 AM Álvaro Fernández Rojas
> wrote:
>>
>> Hi Florian,
>>
>>> El 10 jun 2020, a las 4:27, Florian Fainelli
>>> escribió:
>>>
>>>
>&
{ .name = "mips", .bit = 13, .flags = CLK_IS_CRITICAL, },
> + { .name = "pcie", .bit = 14, },
> + { .name = "robosw250", .bit = 16, },
> + { .name = "robosw025", .bit = 17, },
> + { .name = "sdr", .bit = 19, .flags = CLK_IS_CRITICAL, },
> + { .name = "usb", .bit = 20, },
This should probably be "usbd" to indicate this is the USB device clock
(not host)
With that fixed:
Reviewed-by: Florian Fainelli
--
Florian
On 6/9/2020 3:52 AM, Álvaro Fernández Rojas wrote:
> BCM6362 SoCs have a power domain controller to enable/disable certain
> components in order to save power.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
On 6/9/2020 4:30 AM, Álvaro Fernández Rojas wrote:
> Add BCM6318 to the binding documentation for the gated clock controllers found
> on BCM63xx SoCs.
>
> Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Florian Fainelli
--
Florian
On 6/9/2020 4:08 AM, Álvaro Fernández Rojas wrote:
> In order to make the last clock available, maxbit has to be set to the
> highest bit value plus 1.
>
> Fixes: 1c099779c1e2 ("clk: add BCM63XX gated clock controller driver")
> Signed-off-by: Álvaro Fernández Roj
On 6/9/2020 3:52 AM, Álvaro Fernández Rojas wrote:
> BCM6362 SoCs have a power domain controller to enable/disable certain
> components in order to save power.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
On 6/9/2020 3:52 AM, Álvaro Fernández Rojas wrote:
> BCM6318, BCM6328, BCM6362 and BCM63268 SoCs have a power domain controller
> to enable/disable certain components in order to save power.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> drivers/soc/bcm/Kconfig | 8 +
>
On 6/9/2020 3:52 AM, Álvaro Fernández Rojas wrote:
> BCM6318, BCM6328, BCM6362 and BCM63268 SoCs have a power domain controller
> to enable/disable certain components in order to save power.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> .../devicetree/bindings/mips/brcm/soc.txt |
On 6/9/2020 3:52 AM, Álvaro Fernández Rojas wrote:
> BCM6328 SoCs have a power domain controller to enable/disable certain
> components in order to save power.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
to me though:
Reviewed-by: Florian Fainelli
--
Florian
On 6/9/2020 9:02 AM, Álvaro Fernández Rojas wrote:
> BCM6362 SoCs have a reset controller for certain components.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
On 6/9/2020 9:02 AM, Álvaro Fernández Rojas wrote:
> BCM6368 SoCs have a reset controller for certain components.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
On 6/9/2020 9:02 AM, Álvaro Fernández Rojas wrote:
> BCM6358 SoCs have a reset controller for certain components.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
On 6/9/2020 9:02 AM, Álvaro Fernández Rojas wrote:
> BCM6328 SoCs have a reset controller for certain components.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
You should probably create include files under include/dt-bindings/
which designate the vari
On 6/9/2020 9:02 AM, Álvaro Fernández Rojas wrote:
> Add support for resetting blocks through the Linux reset controller
> subsystem for BCM63xx SoCs.
>
> Signed-off-by: Álvaro Fernández Rojas
This looks good to me, however in v1 there was a need for sleeping after
the reset assertion, and
On 6/9/2020 9:02 AM, Álvaro Fernández Rojas wrote:
> This allows to add reset controllers support.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
On 6/9/2020 9:41 AM, Álvaro Fernández Rojas wrote:
If you can do without this, with I think this driver could be made to
use reset-simple.
>>>
>>> Yes, but only if I can add reset support with a configurable sleep range to
>>> reset-simple. Is this possible?
>>
>> I should have
On 6/9/2020 10:49 AM, Nicolas Saenz Julienne wrote:
> Now that the reset driver exposing Raspberry Pi 4's firmware based USB
> reset routine is available, let's add the device tree node exposing it.
>
> Signed-off-by: Nicolas Saenz Julienne
Reviewed-by: Florian Fainelli
--
Florian
the relevant PCI device.
>
> Signed-off-by: Nicolas Saenz Julienne
With the comment from patch #2 to move the reset identifiers to a shared
header that can be referenced by this file:
Reviewed-by: Florian Fainelli
--
Florian
On 6/9/2020 10:50 AM, Nicolas Saenz Julienne wrote:
> This reverts commit fbbc5ff3f7f9f4cad562e530ae2cf5d8964fe6d3.
>
> The vl805 init routine has moved into drivers/reset/reset-raspberrypi.c
>
> Signed-off-by: Nicolas Saenz Julienne
Reviewed-by: Florian Fainelli
--
Florian
do it manually here.
>
> Signed-off-by: Nicolas Saenz Julienne
Reviewed-by: Florian Fainelli
--
Florian
+ */
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +
> +struct rpi_reset {
> + struct reset_controller_dev rcdev;
> + struct rpi_firmware *fw;
> +};
> +
> +enum rpi_reset_ids {
> + RASPBERRYPI_FIRMWARE_RESET_ID_USB,
You should probably move this to a header file under
include/dt-bindings/reset/ in order to ensure that what gets referenced
by the DTS is in sync with what the driver knows about.
With that:
Reviewed-by: Florian Fainelli
--
Florian
rk.
>
> Signed-off-by: Nicolas Saenz Julienne
Reviewed-by: Florian Fainelli
--
Florian
On 6/9/2020 10:49 AM, Nicolas Saenz Julienne wrote:
> Some atypical users of xhci-pci might need to manually reset their xHCI
> controller before starting the HCD setup. Check if a reset controller
> device is available to the PCI bus and trigger a reset.
>
> Signed-off-by: Nicolas Saenz
lls":
> +const: 1
> +description: >
Is this a stray '>' character? If so, with that fixed:
Reviewed-by: Florian Fainelli
--
Florian
On 6/8/2020 12:26 PM, Nicolas Saenz Julienne wrote:
> The Raspberry Pi 4 gets its USB functionality from VL805, a PCIe chip
> that implements the xHCI. After a PCI fundamental reset, VL805's
> firmware may either be loaded directly from an EEPROM or, if not
> present, by the SoC's co-processor,
On 6/8/2020 12:26 PM, Nicolas Saenz Julienne wrote:
> The firmware running on the RPi VideoCore can be used to reset and
> initialize the board's xHCI controller. The reset controller is passed
> to the PCI device through the DT, hence this binding.
>
> Signed-off-by: Nicolas Saenz Julienne
>
pci_dev
> *pdev)
>*/
> if (pdev->vendor == 0x184e) /* vendor Netlogic */
> return;
> +
> + /*
> + * Bypass the Raspberry Pi 4 controller xHCI controller, things are
> + * taken care by the board's co-processor.
taken care of by.
W
On 6/8/2020 12:26 PM, Nicolas Saenz Julienne wrote:
> Some atypical users of xhci-pci might need to manually reset their xHCI
> controller before starting the HCD setup. Check if a reset controller
> device is available to the PCI bus and trigger a reset.
>
> Signed-off-by: Nicolas Saenz
On 6/7/2020 7:59 AM, Amit Cohen wrote:
> Add spectrum_ethtool.c file for ethtool code.
> Move ethtool_ops and the relevant code from spectrum.c to
> spectrum_ethtool.c.
>
> Signed-off-by: Amit Cohen
> Reviewed-by: Petr Machata
> Reviewed-by: Jiri Pirko
Reviewed
On 6/7/2020 7:59 AM, Amit Cohen wrote:
> Move mlxsw_sp1_port_type_speed_ops and mlxsw_sp2_port_type_speed_ops
> with the relevant code from spectrum.c to spectrum_ethtool.c.
>
> Signed-off-by: Amit Cohen
> Reviewed-by: Petr Machata
> Reviewed-by: Jiri Pirko
Reviewed-by
et()
> in order to allow using the second function in several files, and not
> only as static function in spectrum.c.
>
> Signed-off-by: Amit Cohen
> Reviewed-by: Petr Machata
> Reviewed-by: Jiri Pirko
Reviewed-by: Florian Fainelli
--
Florian
On 6/7/2020 7:59 AM, Amit Cohen wrote:
> Add link extended state attributes.
>
> Signed-off-by: Amit Cohen
> Reviewed-by: Petr Machata
> Reviewed-by: Jiri Pirko
If you need to resubmit, I would swap the order of patches #4 and #5
such that the documentation comes first.
[snip]
>
>
On 6/7/2020 7:59 AM, Amit Cohen wrote:
> Implement .get_down_ext_state() as part of ethtool_ops.
> Query link down reason from PDDR register and convert it to ethtool
> ext_state.
>
> In case that more information than common ext_state is provided,
> fill ext_substate also with the appropriate
hout
> substate (No cable).
>
> Signed-off-by: Amit Cohen
> Reviewed-by: Petr Machata
The delays you have chosen make sense, and if we need to change them
later on, we could always do that.
Reviewed-by: Florian Fainelli
--
Florian
l_extended_state test.
>
> Signed-off-by: Amit Cohen
> Reviewed-by: Petr Machata
Reviewed-by: Florian Fainelli
--
Florian
t.
>
> Signed-off-by: Amit Cohen
> Reviewed-by: Petr Machata
Reviewed-by: Florian Fainelli
--
Florian
On 6/7/2020 7:59 AM, Amit Cohen wrote:
> Currently, drivers can only tell whether the link is up/down using
> LINKSTATE_GET, but no additional information is given.
>
> Add attributes to LINKSTATE_GET command in order to allow drivers
> to expose the user more information in addition to link
On 6/5/2020 7:41 AM, Robin Murphy wrote:
> On 2020-06-05 14:46, Robin Murphy wrote:
>> On 2020-06-05 14:20, Mark Brown wrote:
>>> On Fri, Jun 05, 2020 at 12:34:36PM +0100, Robin Murphy wrote:
>>>> On 2020-06-04 22:28, Florian Fainelli wrote:
>>>
>
On 6/5/2020 2:26 PM, Jim Quinlan wrote:
> From: Jim Quinlan
>
> Broadcom Set-top (BrcmSTB) boards typically support S2, S3, and S5 suspend
> and resume. Now the PCIe driver may do so as well.
>
> Signed-off-by: Jim Quinlan
Acked-by: Florian Fainelli
--
Florian
)
> Signed-off-by: Dan Murphy
Reviewed-by: Florian Fainelli
--
Florian
PHYs inside the package, which leads to the Serdes still
> being enabled on those ports. This patch fixes it.
>
> Fixes: deb04e9c0ff2 ("net: phy: mscc: use phy_package_shared")
> Signed-off-by: Antoine Tenart
Reviewed-by: Florian Fainelli
--
Florian
lize
> Marvell PHYs.")
> Signed-off-by: Dan Murphy
Reviewed-by: Florian Fainelli
--
Florian
> PHYs.")
> Signed-off-by: Dan Murphy
Reviewed-by: Florian Fainelli
--
Florian
t; Signed-off-by: Dan Murphy
Reviewed-by: Florian Fainelli
--
Florian
. So, remove it from the header.
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
---
drivers/media/dvb-core/dvb_frontend.c | 11 +++
include/uapi/linux/dvb/frontend.h | 11 ---
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/media
t; Signed-off-by: Dan Murphy
Reviewed-by: Florian Fainelli
--
Florian
From: Mauro Carvalho Chehab
commit 473e4b4c1cf3046fc6b3437be9a9f3c89c2e61ef upstream
This driver doesn't implement support for set_property(). Yet,
it implements a boilerplate for it. Get rid of it.
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
---
drivers/media/dvb
.
Reviewed-by: Shuah Khan
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
---
drivers/media/dvb-core/dvb_frontend.c | 83 ---
1 file changed, 51 insertions(+), 32 deletions(-)
diff --git a/drivers/media/dvb-core/dvb_frontend.c
b/drivers/media/dvb-core
t make any sense.
Thankfully, it seems that someone else discovered the issue in
the past, as "srate" is currently not used anywhere!
So, get rid of that really weird dead code logic.
Reported-by: Honza Petrous
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
--
-by: Shuah Khan
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
---
drivers/media/dvb-core/dvb_frontend.c | 328 +-
1 file changed, 158 insertions(+), 170 deletions(-)
diff --git a/drivers/media/dvb-core/dvb_frontend.c
b/drivers/media/dvb-core
applications.
Signed-off-by: Jaedon Shin
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
---
drivers/media/dvb-core/dvb_frontend.c | 131 ++
1 file changed, 131 insertions(+)
diff --git a/drivers/media/dvb-core/dvb_frontend.c
b/drivers/media/dvb-core
to the entire struct dtv_property *tvp.
Instead of having a generic dtv_property_dump(), added its own
properties debug logic in the dtv_property_process_set().
Signed-off-by: Satendra Singh Thakur
Reviewed-by: Shuah Khan
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
From: Mauro Carvalho Chehab
commit da5516b5e81d45a96291823620f6c820178dc055 upstream
Two readonly ioctls can't be allowed if the frontend device
is opened in read only mode. Explain why.
Reviewed by: Shuah Khan
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
-to: Arnd Bergmann
To make me revisit this code.
Fixes: a9cb97c3e628 ("media: dvb_frontend: be sure to init
dvb_frontend_handle_ioctl() return code")
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
---
drivers/media/dvb-core/dvb_frontend.c | 2 +-
1 file changed, 1
, instead, at set_frontend() callback.
So, get rid of it.
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
---
drivers/media/usb/dvb-usb/friio-fe.c | 24
1 file changed, 24 deletions(-)
diff --git a/drivers/media/usb/dvb-usb/friio-fe.c
b/drivers/media
From: Jaedon Shin
commit c2dfd2276cec63a0c6f6ce18ed83800d96fde542 upstream
Adds compat_ioctl for 32-bit user space applications on a 64-bit system.
[m.che...@osg.samsung.com: add missing include compat.h]
Signed-off-by: Jaedon Shin
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian
dating
the documentation accordingly and removing the logic that
would update the discarded tvp->result.
Reviewed-by: Shuah Khan
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
---
Documentation/media/uapi/dvb/fe-get-property.rst | 7 +--
drivers/media/dvb-core/dvb_f
From: Mauro Carvalho Chehab
commit 6680e73b5226114992acfc11f9cf5730f706fb01 upstream
Now that all clients of set_property() were removed, get rid
of this callback.
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
---
drivers/media/dvb-core/dvb_frontend.c | 7
a...@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab
Tested-by: Daniel Scheller
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
---
drivers/media/dvb-core/dvb_frontend.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/media/dvb-core/dvb_f
to indicate when the properties
got flushed.
So, just get rid of it for good.
Reviewed-by: Shuah Khan
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
---
drivers/media/dvb-core/dvb_frontend.c | 20 ++--
drivers/media/dvb-core/dvb_frontend.h | 5 -
2
of it.
Signed-off-by: Mauro Carvalho Chehab
Reviewed-by: Michael Ira Krufky
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
---
drivers/media/dvb-core/dvb_frontend.c | 9 +
drivers/media/dvb-core/dvb_frontend.h | 3 ---
drivers/media/dvb-frontends/lg2160.c | 14
a
pointer of 2nd or after item of 'struct compat_dtv_property' array.
Signed-off-by: Katsuhiro Suzuki
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
---
drivers/media/dvb-core/dvb_frontend.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/dvb
comments.
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
---
include/uapi/linux/dvb/frontend.h | 580 +-
1 file changed, 498 insertions(+), 82 deletions(-)
diff --git a/include/uapi/linux/dvb/frontend.h
b/include/uapi/linux/dvb/frontend.h
index
From: Jaedon Shin
commit a2282fd1fe2ebcda480426dbfaaa7c4e87e27399 upstream
Adds unlocked ioctl function directly in dvb_frontend.c instead of using
dvb_generic_ioctl().
Signed-off-by: Jaedon Shin
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Florian Fainelli
---
drivers/media/dvb
Hi all,
This long patch series was motivated by backporting Jaedon's changes
which add a proper ioctl compatibility layer for 32-bit applications
running on 64-bit kernels. We have a number of Android TV-based products
currently running on the 4.9 kernel and this was broken for them.
Thanks to
1101 - 1200 of 8558 matches
Mail list logo
