- May 15, 2024
-
-
Robert Nelson authored
6.1.80-ti-rt-arm64-r48 bb.org_defconfig TI SDK: 09.02.00.009 6.1 TI Delta: https://github.com/RobertCNelson/ti-linux-kernel/compare/1c154b1fe4c462d8b383515bb388e289816e4b01...2e423244f8c09173a344e7069f0fe2bdf26cccee BBDTBS: BeagleBoard-DeviceTrees@935ca119 RT: patch-6.1.80-rt26.patch.xz WIRELESS_REGDB: https://git.kernel.org/pub/scm/linux/kernel/git/wens/wireless-regdb.git/commit/?id=73529a882f83afa26402b18680025334b0215d92 WPANUSB: beagleconnect/linux/wpanusb@6aa9bf65 Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
-
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Nishanth Menon authored
Signed-off-by:Nishanth Menon <nm@ti.com>
-
Nishanth Menon authored
When frequency is not exact, the debug information is informative, but not necessarily informational to the end user. Lower the severity down. Fixes: 3e9bee11 ("ASoC: davinci-mcasp: Restructure the davinci_mcasp_calc_clk_div()") Signed-off-by:
-
Robert Nelson authored
Signed-off-by: -
Takuma Fujiwara authored
-
Nishanth Menon authored
Commit 85e6b8d4 ("HACK: drm/bridge: ite-it66121: Add drm_connector support") and related patches seem to have broken HPD. hack the same in. NOTE: This hack is not perfect, if the HDMI is not plugged in at the very start of the boot, we seem to manually need to trigger the following (path to display depends on platform and configuration) echo connected|sudo tee /sys/class/drm/card0-HDMI-A-1/status Signed-off-by:
Jared McArthur <j-mcarthur@ti.com> Signed-off-by:
-
Nishanth Menon authored
The it66121 and replaced with it66122. The part is register compatible with what we have for it66121. pid 0x0612 on the 66121 device to 0x0622 on the 66122 device, but I guess it makes sense to someone. Signed-off-by: -
Nishanth Menon authored
Add a new ite,it66122 compatible string to the IT66121 binding documentation, since the two chips are practically same except for id register difference. Signed-off-by: -
Biju Das authored
commit c11c1a50 upstream The driver has OF match table, still it uses ID lookup table for retrieving match data. Currently the driver is working on the assumption that a I2C device registered via OF will always match a legacy I2C device ID. The correct approach is to have an OF device ID table using of_device_match_data() if the devices are registered via OF. Signed-off-by:
Biju Das <biju.das.jz@bp.renesas.com> Reviewed-by:
Andy Shevchenko <andriy.shevchenko@linux.intel.com> Reviewed-by:
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> Signed-off-by:
Robert Foss <rfoss@kernel.org> Link: https://patchwork.freedesktop.org/patch/msgid/20230818191817.340360-2-biju.das.jz@bp.renesas.com [nm@ti.com: Backport from upstream next-20240502] Signed-off-by:
-
Sui Jingfeng authored
commit ba2d3e67 upstream If a specific design doesn't wire IT66121's interrupt signal output pin up to the display controller side, then we should not register the interrupt handler. Such a decision is valid usage, as we can fall back to polling mode. So, don't make the assumption that a specific board always supports HPD. Carry out a sanity check on 'client->irq' before using it, fall back to polling mode if client->irq < 0 is true. Such a design increases the overall flexibility. Signed-off-by:
Sui Jingfeng <sui.jingfeng@linux.dev> Reviewed-by:
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Link: https://lore.kernel.org/r/20240316160536.1051513-1-sui.jingfeng@linux.dev Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org> Link: https://patchwork.freedesktop.org/patch/msgid/20240316160536.1051513-1-sui.jingfeng@linux.dev [nm@ti.com: Backport from upstream next-20240502] Signed-off-by:
-
Paul Cercueil authored
commit 9a9f4a01 upstream This will make it easier later to introduce support for new chips in this driver. Signed-off-by:
Paul Cercueil <paul@crapouillou.net> Reviewed-by:
Robert Foss <robert.foss@linaro.org> Link: https://patchwork.freedesktop.org/patch/msgid/20221214130122.12911-1-paul@crapouillou.net Signed-off-by:
-
Paul Cercueil authored
commit e6685650 upstream The DDC preamble and target address only need to be set once before reading the EDID, even if multiple segments have to be read. Signed-off-by:
-
Paul Cercueil authored
commit d7f139da upstream The DDC FIFO was cleared before the loop in it66121_get_edid_block(), and at the beginning of each iteration; which means that it did not have to be cleared before the loop. Signed-off-by:
-
Paul Cercueil authored
commit 12530ae4 upstream The DDC error IRQs will fire on the IT6610 every time the FIFO is empty, which is not very helpful. To resolve this, we can simply disable them, and handle DDC errors in it66121_wait_ddc_ready(). Signed-off-by:
-
Paul Cercueil authored
commit 66bb0a7c upstream The function it66121_wait_ddc_ready() would previously read the status register until "true", which means it never actually polled anything and would just read the register once. Now, it will properly wait until the DDC hardware is ready or until it reported an error. The 'busy' variable was also renamed to 'error' since these bits are set on error and not when the DDC hardware is busy. Since the DDC ready function is now working properly, the msleep(20) can be removed. Signed-off-by:
-
Paul Cercueil authored
commit 6ba98fd6 upstream Since all AVI infoframe registers are contiguous in the address space, the AVI infoframe can be written in one go with regmap_bulk_write(). Signed-off-by:
-
Paul Cercueil authored
commit 315c9fb7 upstream Use regmap_noinc_read() instead of reading the data from the DDC FIFO one byte at a time. Signed-off-by:
-
Paul Cercueil authored
commit 334c8c1d upstream Simplify the code of the driver by using devm_regulator_bulk_get_enable(), which will handle powering up the regulators, and disabling them on probe error or module removal. Signed-off-by:
-
Uwe Kleine-König authored
commit c4150e13 upstream The probe function doesn't make use of the i2c_device_id * parameter so it can be trivially converted. Signed-off-by:
Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Reviewed-by:
-
Angel Iglesias authored
commit 66223373 upstream Introduces new helper function to aid in .probe_new() refactors. In order to use existing i2c_get_device_id() on the probe callback, the device match table needs to be accessible in that function, which would require bigger refactors in some drivers using the deprecated .probe callback. This issue was discussed in more detail in the IIO mailing list. Link: https://lore.kernel.org/all/20221023132302.911644-11-u.kleine-koenig@pengutronix.de/ Suggested-by:
Nuno Sá <noname.nuno@gmail.com> Suggested-by:
Jonathan Cameron <jic23@kernel.org> Signed-off-by:
Angel Iglesias <ang.iglesiasg@gmail.com> Reviewed-by:
Jonathan Cameron <Jonathan.Cameron@huawei.com> Signed-off-by:
Wolfram Sang <wsa@kernel.org> [nm@ti.com: Backport from upstream next-20240502] Signed-off-by:
-
Nishanth Menon authored
This is not aligned with the solution in upstream kernel so far. This reverts commit 303a8d99 . Signed-off-by:
-
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Jared McArthur authored
-
Ben Hutchings authored
We want to enable use of the Android ashmem and binder drivers to support Anbox, but they should not be built-in as that would waste resources and increase security attack surface on systems that don't need them. Export the currently un-exported symbols they depend on.
-
Ben Hutchings authored
We want to enable use of the Android ashmem and binder drivers to support Anbox, but they should not be built-in as that would waste resources and increase security attack surface on systems that don't need them. - Add a MODULE_LICENSE declaration to ashmem - Change the Makefiles to build each driver as an object with the "_linux" suffix (which is what Anbox expects) - Change config symbol types to tristate Update: In upstream commit 721412ed titled "staging: remove ashmem" the ashmem driver was removed entirely. Secondary commit message: "The mainline replacement for ashmem is memfd, so remove the legacy code from drivers/staging/" Consequently, the ashmem part of this patch has been removed.
-
Ayush Singh authoredSigned-off-by:Ayush Singh <ayushdevel1325@gmail.com>
-
Vaishnav Achath authored
add of_find_serdev_controller_by_node to obtain a serdev_controller from the device_node, which can help if the serdev_device is not described over device tree and instantiation of the device happens from a different driver, for the same purpose an option to not delete an empty serdev controller is added. Signed-off-by:
Vaishnav M A <vaishnav@beagleboard.org> Signed-off-by:
-
Ayush Singh authored
This externalizes and exports the symbol of_find_spi_controller_by_node() from the SPI core akin to how of_find_i2c_adapter_by_node() is already available. As we will need this also for non-dynamic OF setups, we move it under a CONFIG_OF check. Signed-off-by: -
Ayush Singh authored
Signed-off-by: -
Ayush Singh authored
Signed-off-by: -
Kishon Vijay Abraham I authored
Lets drive Sierra clock output and workaround a TIFS/DM bug for now. Signed-off-by:Kishon Vijay Abraham I <kishon@ti.com>
-
Romain Naour authored
"PM runtime functions" has been added in sdhci-omap driver in 5.16 f433e8aa ("mmc: sdhci-omap: Implement PM runtime functions") along with "card power off and enable aggressive PM" 3edf588e ("mmc: sdhci-omap: Allow SDIO card power off and enable aggressive PM"). Since then, the sdhci-omap driver doesn't work using mmc-hs200 mode due to the tuning values being lost during a pm transition. See the report on the linux-omap mailing list [1]. As for the sdhci_am654 driver, request a new tuning sequence before suspend (sdhci_omap_runtime_suspend()), othwerwise the device will thigger cache flush errors: mmc1: cache flush error -110 (ETIMEDOUT) mmc1: error -110 doing aggressive suspend followed by I/O errors produced by fdisk -l /dev/mmcblk1boot1: I/O error, dev mmcblk1boot0, sector 64384 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 I/O error, dev mmcblk1boot1, sector 64384 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 I/O error, dev mmcblk1boot1, sector 64384 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Buffer I/O error on dev mmcblk1boot1, logical block 8048, async page read I/O error, dev mmcblk1boot0, sector 64384 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Buffer I/O error on dev mmcblk1boot0, logical block 8048, async page read Don't re-tune if auto retuning is supported in HW (when SDHCI_TUNING_MODE_3 is available). [1] https://lore.kernel.org/all/2e5f1997-564c-44e4-b357-6343e0dae7ab@smile.fr Fixes: f433e8aa ("mmc: sdhci-omap: Implement PM runtime functions") Signed-off-by:
Romain Naour <romain.naour@skf.com>
-
Jason Kridner authored
-
