On Fri, Aug 21, 2020 at 10:13:25PM +0200, Thomas Gleixner wrote:
> On Thu, Aug 20 2020 at 14:53, Adam Borowski wrote:
> > Found by randconfig builds.
> >
> > arch/x86/pci/intel_mid_pci.c | 2 ++
> > arch/x86/pci/xen.c | 2 ++
> > --- a/arch/x86/pci/intel
in that case. This
commit restores the default value to avoid this happening.
Fixes: aa5b18d1c290 ("ASoC: da7219: Move soft reset handling to codec level
probe")
Reported-by: Pierre-Louis Bossart
Signed-off-by: Adam Thomson
---
sound/soc/codecs/da7219.c | 5 +++--
1 file changed, 3 insert
d da9210_dt_ids[] = {
> | ^
>
> Signed-off-by: Jisheng Zhang
Acked-by: Adam Thomson
The DTC doesn't like the default PWM settings, because it's expecting
three cells. This patch reduces adds the extra entry of 0 to the PWM
reference.
Fixes: fa28d8212ede ("ARM: dts: imx: default to #pwm-cells = <3> in the SoC
dtsi files")
Reviewed-by: Fabio Estevam
Signed-o
The DTC doesn't like the default PWM settings, because it's expecting
three cells. This patch reduces adds the extra entry of 0 to the PWM
reference.
Fixes: fa28d8212ede ("ARM: dts: imx: default to #pwm-cells = <3> in the SoC
dtsi files")
---
V2: Don't change HDMI
Signed-o
The DTC doesn't like the default PWM settings, because it's expecting
three cells. This patch reduces adds the extra entry of 0 to the PWM
reference.
Fixes: fa28d8212ede ("ARM: dts: imx: default to #pwm-cells = <3> in the SoC
dtsi files")
Signed-off-by: Adam Ford
diff --git
With the additional power management options enabled,
this patch enables OMAP3_THERMAL by default.
Signed-off-by: Adam Ford
---
V2: No change
diff --git a/arch/arm/configs/omap2plus_defconfig
b/arch/arm/configs/omap2plus_defconfig
index fe383f5a92fb..efcc46305a47 100644
--- a/arch/arm/configs
.
Signed-off-by: Adam Ford
Reported-by: kernel test robot
---
V2: Fix issue where variable stating the suspend mode isn't being
properly set and cleared.
diff --git a/drivers/thermal/ti-soc-thermal/ti-bandgap.c
b/drivers/thermal/ti-soc-thermal/ti-bandgap.c
index ab19ceff6e2a..9404631bea4d 100644
On Tue, Aug 18, 2020 at 11:58 PM Tony Lindgren wrote:
>
> * Adam Ford [200818 15:46]:
> > @@ -1153,6 +1166,38 @@ static int ti_bandgap_suspend(struct device *dev)
> > return err;
> > }
> >
> > +static int bandgap_omap_cp
On 18 August 2020 17:39, Zhi, Yong wrote:
> > This patch set reorganises and fixes device and codec level probe/remove
> > handling within the driver, to allow clean probe and remove at the codec
> > level.
> >
> > This set relates to an issue raised by Yong Zhi where a codec level re-probe
> >
With the additional power management options enabled,
this patch enables OMAP3_THERMAL by default.
Signed-off-by: Adam Ford
diff --git a/arch/arm/configs/omap2plus_defconfig
b/arch/arm/configs/omap2plus_defconfig
index fe383f5a92fb..efcc46305a47 100644
--- a/arch/arm/configs
.
Signed-off-by: Adam Ford
diff --git a/drivers/thermal/ti-soc-thermal/ti-bandgap.c
b/drivers/thermal/ti-soc-thermal/ti-bandgap.c
index ab19ceff6e2a..923ef3abb867 100644
--- a/drivers/thermal/ti-soc-thermal/ti-bandgap.c
+++ b/drivers/thermal/ti-soc-thermal/ti-bandgap.c
@@ -25,10 +25,18 @@
#include
the temperatures for extended
temperature ratings, these can be changed on their respective
device trees with something like:
_alert0 {
temperature = <9>; /* millicelsius */
};
_crit {
temperature = <105000>; /* millicelsius */
};
Signed-off-by: Adam Ford
On Mon, Aug 17, 2020 at 2:59 PM Andreas Kemnade wrote:
>
> On Mon, 17 Aug 2020 08:39:31 -0500
> Adam Ford wrote:
>
> > The OMAP3530, OMAP3630, and DM3730 all show thresholds of 90C and 105C
> > depending on commercial or industrial temperature ratings.
> >
>
millicelsius */
};
OMAP3_THERMAL will need to be enabled. It is off by default.
Signed-off-by: Adam Ford
Tested-by: H. Nikolaus Schaller # on GTA04A5 with
dm3730cbp100
---
V2: Rebase on Linux 5.9-rc1
diff --git a/arch/arm/boot/dts/omap3-cpu-thermal.dtsi
b/arch/arm/boot/dts/omap3-cpu-thermal.dtsi
index
t.dts to
logicpd-som-lv-baseboard.dtsi")
Signed-off-by: Adam Ford
diff --git a/arch/arm/boot/dts/logicpd-som-lv-baseboard.dtsi
b/arch/arm/boot/dts/logicpd-som-lv-baseboard.dtsi
index 79e9e24328b9..395e05f10d36 100644
--- a/arch/arm/boot/dts/logicpd-som-lv-baseboard.dtsi
+++ b/arch/arm/boot/dts/l
timing requirements.
A similar patch was already done and applied to the Torpedo family.
Fixes: 8bf4b1621178 ("drm/omap: Remove panel-dpi driver")
Signed-off-by: Adam Ford
diff --git a/arch/arm/boot/dts/logicpd-som-lv-baseboard.dtsi
b/arch/arm/boot/dts/logicpd-som-lv-baseboard.
On 12 August 2020 14:31, Hsin-Yi Wang wrote:
> Add regmap_cache to reduce wakeups events of interrupt if regulator is
> accessed frequently. This results in saving more power.
>
> Suggested-by: Daniel Kurtz
> Signed-off-by: Hsin-Yi Wang
Acked-by: Adam Thomson
freed up so the clocks were still registered from the previous
codec level probe().
This commit updates the clock handling for MCLK usage and DAI
clock provision to fix this discrepancy and allow the codec level
probe/remove functionality to operate as intended.
Signed-off-by: Adam Thomson
* functions being called for
regulator instantiation at the codec level.
Signed-off-by: Adam Thomson
---
sound/soc/codecs/da7219.c | 371 +++---
1 file changed, 188 insertions(+), 183 deletions(-)
diff --git a/sound/soc/codecs/da7219.c b/sound/soc/codecs/da7219.c
In preparation for cleanup of device level and codec level probe
funcitonality, all necessary devm_* allocations and fw retrieval
functions are moved to the I2C probe level code.
Signed-off-by: Adam Thomson
---
sound/soc/codecs/da7219-aad.c | 85
instantiation.
In addition some improvements around regulator handling and soft reset have
also been included.
Adam Thomson (3):
ASoC: da7219: Move required devm_* allocations to device level code
ASoC: da7219: Move soft reset handling to codec level probe
ASoC: da7219: Fix clock handling around
-regulator.c:
Acked-by: Adam Thomson
> ---
> drivers/regulator/da9055-regulator.c | 2 --
> drivers/regulator/da9062-regulator.c | 2 --
> drivers/regulator/da9063-regulator.c | 2 --
> drivers/regulator/da9210-regulator.c | 4
> drivers/regulator/da9211-regu
On Mon, Oct 7, 2019 at 5:06 PM Adam Ford wrote:
>
> The OMAP3530, OMAP3630, and DM3730 all show thresholds of 90C and 105C
> depending on commercial or industrial temperature ratings.
>
> This patch expands the thermal information to include the limits of 90
> and 105C for
This driver requests, memory twice and requests a threaded irq, but
it doesn't free any of them if something fails.
This patch attempts to identify areas where a return was issued
without freeing allocated memory or IRQ's.
Signed-off-by: Adam Ford
diff --git a/drivers/input/touchscreen
On Tue, Aug 04, 2020 at 09:25:23AM +0200, Sedat Dilek wrote:
> On Tue, Aug 4, 2020 at 8:52 AM Geert Uytterhoeven
> wrote:
> > On Thu, Jul 30, 2020 at 9:13 PM Nick Terrell wrote:
> > > From: Nick Terrell
> > > * Add support for a zstd compressed initramfs.
> > > * Add compression for
On Fri, Jul 24, 2020 at 02:26:40PM +0200, Ingo Molnar wrote:
> > -#ifdef CONFIG_KERNEL_BZIP2
> > +#if defined(CONFIG_KERNEL_BZIP2)
> > # define BOOT_HEAP_SIZE0x40
> > -#else /* !CONFIG_KERNEL_BZIP2 */
> > +#elif defined(CONFIG_KERNEL_ZSTD)
> > +# define BOOT_HEAP_SIZE
On 19 July 2020 01:29, Randy Dunlap wrote:
> Drop the repeated word "that" in a comment.
>
> Signed-off-by: Randy Dunlap
> Cc: Support Opensource
> Cc: Lee Jones
Acked-by: Adam Thomson
> ---
> include/linux/mfd/da9055/pdata.h |2 +-
> 1 file c
if the memory allocation fails, and returns
and -ENOMEM error instead of blindly moving on.
Fixes: 260249f929e8 ("clk: vc5: Enable addition output configurations of the
Versaclock")
Suggested-by: Dan Carpenter
Signed-off-by: Adam Ford
Reviewed-by: Luca Ceresoli
---
V3: Fix spel
On Thu, Jul 16, 2020 at 2:39 AM Geert Uytterhoeven wrote:
>
> Hi Stephen,
>
> On Thu, Jul 16, 2020 at 2:38 AM Stephen Boyd wrote:
> > Quoting Geert Uytterhoeven (2020-07-13 05:45:00)
> > > On Thu, Jul 9, 2020 at 12:00 AM Adam Ford wrote:
> > > > On Wed,
buttons and LED's, and support for
a parallel RGB and an LVDS display.
Signed-off-by: Adam Ford
---
V3: Updated makefile so the beacon dtb reference is alphabetically in
order, made 'vsync-active' in lvds node a valid number, added
power-supply for the RGB node, and changed
On Wed, Jul 15, 2020 at 3:58 AM Geert Uytterhoeven wrote:
>
> On Tue, Jul 14, 2020 at 2:34 PM Adam Ford wrote:
> > Beacon EmbeddedWorks in introducing a development kit based on the
> > Renesas RZ/G2M platform. This patch adds the entry to the bindings
> > list.
> >
buttons and LED's, and support for
a parallel RGB and an LVDS display.
Signed-off-by: Adam Ford
---
V2: Add support for RGB display, second backlight, fix clock references,
fix Makefile, remove unsupported versaclock features, and fix typos.
diff --git a/arch/arm64/boot/dts/renesas/Makefile
Beacon EmbeddedWorks in introducing a development kit based on the
Renesas RZ/G2M platform. This patch adds the entry to the bindings
list.
Signed-off-by: Adam Ford
---
V2: New to series
diff --git a/Documentation/devicetree/bindings/arm/renesas.yaml
b/Documentation/devicetree/bindings
This update adds new regmap tables to support the latest DA silicon
which will automatically be selected based on the chip and variant
information read from the device.
Signed-off-by: Adam Thomson
Acked-for-MFD-by: Lee Jones
---
v3:
- No change
v2:
- No change
drivers/mfd/da9063-i2c.c
the proper regmap tables for
real initialisation.
Signed-off-by: Adam Thomson
---
v3:
- Replaced magic numbers around I2C paged access code with enums and defines
- Small style tidy ups as requested by Lee Jones
v2:
- Use raw I2C read access instead of a temporary regmap to interrogate chip
:
- Use raw I2C read access instead of a temporary regmap to interrogate chip and
variant id registers
Adam Thomson (2):
mfd: da9063: Fix revision handling to correctly select reg tables
mfd: da9063: Add support for latest DA silicon revision
drivers/mfd/da9063-core.c| 31
t; If doesn't contain `\bxmlns\b`:
> For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
> If both the HTTP and HTTPS versions
> return 200 OK and serve the same content:
> Replace HTTP with HTTPS.
>
> Signed-off-by: Alexander A. Klimov
Acked-b
On Mon, Jul 6, 2020 at 6:18 AM Adam Ford wrote:
>
> On Mon, Jul 6, 2020 at 1:02 AM Tomi Valkeinen wrote:
> >
> > Hi,
> >
> > On 03/07/2020 22:36, Sam Ravnborg wrote:
> > > Hi Tomi.
> > >
> > > On Fri, Jul 03, 2020 at 10:17:29AM +0300, To
On Wed, Jul 8, 2020 at 4:53 PM Adam Ford wrote:
>
> On Mon, Jun 22, 2020 at 8:20 AM Geert Uytterhoeven
> wrote:
> >
> > Hi Adam,
> >
> > Thanks for your patch!
>
> Thanks for the review. :-)
>
> >
> > On Wed, Jun 17, 2020 at 2:05 PM Adam F
On Mon, Jun 22, 2020 at 8:20 AM Geert Uytterhoeven wrote:
>
> Hi Adam,
>
> Thanks for your patch!
Thanks for the review. :-)
>
> On Wed, Jun 17, 2020 at 2:05 PM Adam Ford wrote:
> > Beacon EmebddedWorks, formerly Logic PD is introducing a new
>
> EmbeddedWo
if the memory allocation fails, and returns
and -NOMEM error instead of blindly moving on.
Fixes: 260249f929e8 ("clk: vc5: Enable addition output configurations of the
Versaclock")
Suggested-by: Dan Carpenter
Signed-off-by: Adam Ford
diff --git a/drivers/clk/clk-versaclock5.c b/drive
On Thu, Jul 2, 2020 at 5:40 PM Luca Ceresoli wrote:
>
> The Versaclock chips can drive the output pins in several modes: LVDS,
> CMOS, LVPECL etc. Allow configuring the output mode from device tree.
>
> The configuration is optional. If not specified, the mode will not be
> configured and the
On Fri, Apr 24, 2020 at 1:37 AM Adam Goode wrote:
>
> bFrameIndex and bFormatIndex can be negotiated by the camera during
> probing, resulting in the camera choosing a different format than
> expected. v4l2 can already accommodate such changes, but the code was
> not updating th
On Mon, Jul 6, 2020 at 1:02 AM Tomi Valkeinen wrote:
>
> Hi,
>
> On 03/07/2020 22:36, Sam Ravnborg wrote:
> > Hi Tomi.
> >
> > On Fri, Jul 03, 2020 at 10:17:29AM +0300, Tomi Valkeinen wrote:
> >> On 30/06/2020 21:26, Adam Ford wrote:
> >>> The
On 03 July 2020 10:33, Adam Thomson wrote
> On 01 July 2020 19:24, Pierre-Louis Bossart wrote:
>
> > fix W=1 warning
> >
> > sound/soc/codecs/da7219.c:1711:36: warning: 'da7219_acpi_match'
> > defined but not used [-Wunused-const-variable=]
> > 1711
On 26 June 2020 17:46, Sebastian Reichel wrote:
> This adds default clock/PLL configuration to the driver
> for usage with generic drivers like simple-card for usage
> with a fixed rate clock.
>
> Signed-off-by: Sebastian Reichel
Looks good. Thanks for the work here.
Reviewed-b
On 01 July 2020 19:24, Pierre-Louis Bossart wrote:
> fix W=1 warning
>
> sound/soc/codecs/da7219.c:1711:36: warning: 'da7219_acpi_match'
> defined but not used [-Wunused-const-variable=]
> 1711 | static const struct acpi_device_id da7219_acpi_match[] = {
> |
On 01 July 2020 19:24, Pierre-Louis Bossart wrote:
> Fix W=1 warning, the kernel-doc syntax was probably from Doxygen?
>
> Signed-off-by: Pierre-Louis Bossart
So is the issue that the Kernel warning mechanism doesn't like Doxygen syntax?
If so then:
Acked-by: Adam Thomson
> ---
if the memory allocation fails, and returns
and -NOMEM error instead of blindly moving on.
Suggested-by: Dan Carpenter
Signed-off-by: Adam Ford
diff --git a/drivers/clk/clk-versaclock5.c b/drivers/clk/clk-versaclock5.c
index 1d8ee4b8b1f5..29cdb38dc40b 100644
--- a/drivers/clk/clk-versaclock5.c
driver instead of the drm.
Fixes: f76ee892a99e ("omapfb: copy omapdss & displays for omapfb")
Cc: #4.9+
Signed-off-by: Adam Ford
---
Linux 4.4 will need a similar patch, but it doesn't apply cleanly.
The DRM version of this same fix is:
e2c4ed148cf3 ("drm/omap: fix max fclk d
On 25 June 2020 20:17, Lee Jones wrote:
> Looks as though 99f75ce666199 ("regulator: da9063: fix suspend") failed
> to clean-up all of the existing .suspend variable initialisations.
> This has led to some 'initilized field overwritten' issues now present
> in W=1 builds.
You probably were not
ch works.
> > > >
> > > > This update adds raw I2C read access functionality to read the chip
> > > > and variant/revision information (common to all revisions) so that
> > > > it can subsequently correctly choose the proper regmap tables for
> &g
unctionality to read the chip
> > and variant/revision information (common to all revisions) so that
> > it can subsequently correctly choose the proper regmap tables for
> > real initialisation.
> >
> > Signed-off-by: Adam Thomson
> > ---
> > d
buttons and LED's.
Signed-off-by: Adam Ford
diff --git a/arch/arm64/boot/dts/renesas/beacon-renesom-baseboard.dtsi
b/arch/arm64/boot/dts/renesas/beacon-renesom-baseboard.dtsi
new file mode 100644
index ..750d14b35053
--- /dev/null
+++ b/arch/arm64/boot/dts/renesas/beacon-renesom
accel rev: 2.6
omap-aes 480a6000.aes1: will run requests pump with realtime priority
omap-aes 480c5000.aes2: OMAP AES hw accel rev: 2.6
omap-aes 480c5000.aes2: will run requests pump with realtime priority
Signed-off-by: Adam Ford
---
V2: Fix DMA for AES1, and remove from AM3517.
diff --git
On Mon, Jun 15, 2020 at 9:46 AM Fabio Estevam wrote:
>
> On Mon, Jun 15, 2020 at 10:19 AM Adam Ford wrote:
> >
> > The LogicPD Type28 display used by several Logic PD products has not
> > worked since v5.5.
>
> Maybe you could tell which commit exactly and then put
The LogicPD Type28 display used by several Logic PD products has not
worked since v5.5.
The connector type for the LogicPD Type 28 display is missing and
drm_panel_bridge_add() requires connector type to be set.
Signed-off-by: Adam Ford
CC: sta...@vger.kernel.org #v5.5+
diff --git a/drivers
On 17 April 2020 11:56, Adam Thomson wrote:
> This patch set fixes the currently broken revision handling in the driver's
> i2c_probe() function and then adds DA support to existing permitted revisions.
Do I need to resend this patch, or will you still pick up the original mail
submissio
On Tue, May 5, 2020 at 6:34 PM Tony Lindgren wrote:
>
> * Adam Ford [200505 21:18]:
> > On Tue, May 5, 2020 at 1:42 PM Tony Lindgren wrote:
> > >
> > > * Adam Ford [200504 16:02]:
> > > > Various OMAP3 boards have two AES blocks, but only one is curre
On Mon, Jun 08, 2020 at 12:59:44PM +0300, Denis Efremov wrote:
> Redefine GZIP, BZIP2, LZOP variables as KGZIP, KBZIP2, KLZOP resp.
> GZIP, BZIP2, LZOP env variables are reserved by the tools. The original
> attempt to redefine them internally doesn't work in makefiles/scripts
> intercall
The VersaClock driver now supports some additional bindings to support
child nodes which can configure optional settings like mode, voltage
and slew.
This patch updates the binding document to describe what is available
in the driver.
Signed-off-by: Adam Ford
Reviewed-by: Rob Herring
---
V3
versaclock_som.fod2
versaclock_som.out3
versaclock_som.fod1
versaclock_som.out2
versaclock_som.fod0
versaclock_som.out1
Signed-off-by: Adam Ford
---
V3: Remove 'probed' message
V2: No change
diff --git a/drivers
:
- Programmable voltage: 1.8V, 2.5V, or 3.3V
- Slew Percentage of normal: 85%, 90%, or 100%
- Output Type: LVPECL, CMOS, HCSL, or LVDS
Signed-off-by: Adam Ford
---
V3: Make source code change following the binding changes since there
is a dependency and move changes to binding header file
;)
Signed-off-by: Adam Ford
diff --git a/arch/arm64/boot/dts/freescale/imx8mm-beacon-som.dtsi
b/arch/arm64/boot/dts/freescale/imx8mm-beacon-som.dtsi
index fb0137a8611c..94911b1707ef 100644
--- a/arch/arm64/boot/dts/freescale/imx8mm-beacon-som.dtsi
+++ b/arch/arm64/boot/dts/freescale/imx8mm-beaco
r in
> > Linux. Drivers are the abstraction around the hardware, there is no
> > need to invent another one if there are no clear benefits.
> >
>
> Jacky / Abel,
>
> Any movement on this? As I see it the lack of imx8mm power-domain
> support in the kernel is holding up USB, PCIe, VPU, and perhaps
> GPU/CSI as well. I would tend to agree that hiding this functionality
> in the TF-A is probably not the best approach especially as that
> requires a NXP version of the TF-A. I really don't see the issue with
> the gpc driver getting a little more complicated if it needs to. There
> is bound to be some complication as there is such a large variation of
> IMX8 products out there! (talk about confusing!).
NXP -
Please don't let perfect be the enemy of the good. We have some
patches floating around which enable much of the functionality. It
may not be perfect, but it's an improvement from what we currently
have - which is nothing. Please let the patches in, and when the
alternative methods become available, we can remove these.
If TF_A is arguing about how to push the patches upstream, then maybe
Tim is wright and it's not a good idea, and we should consider
something else.
adam
>
> Best Regards,
>
> Tim
On 11 May 2020 14:26, Sebastian Reichel wrote:
> This adds default clock/PLL configuration to the driver
> for usage with generic drivers like simple-card for usage
> with a fixed rate clock.
>
> Signed-off-by: Sebastian Reichel
> ---
> sound/soc/codecs/da7213.c | 76
>
On Tue, May 12, 2020 at 5:05 PM Rob Herring wrote:
>
> On Sat, May 02, 2020 at 07:21:25AM -0500, Adam Ford wrote:
> > The existing driver is expecting the Versaclock to be pre-programmed,
> > and only sets the output frequency. Unfortunately, not all devices
>
On Tue, May 5, 2020 at 1:42 PM Tony Lindgren wrote:
>
> * Adam Ford [200504 16:02]:
> > Various OMAP3 boards have two AES blocks, but only one is currently
> > available, because the hwmods are only configured for one.
> >
> > This patch migrates the hwmods fo
accel rev: 2.6
omap-aes 480a6000.aes1: will run requests pump with realtime priority
omap-aes 480c5000.aes2: OMAP AES hw accel rev: 2.6
omap-aes 480c5000.aes2: will run requests pump with realtime priority
Signed-off-by: Adam Ford
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts
ses the 3D or 2D, would it make sense to mark them
as disabled by default and let people who need the 3D and 2D enable
them at their respective board files?
adam
> 2.17.1
et's also configure the SoC specific default values. The
> board specific dts files can reconfigure these with assigned-clocks
> and assigned-clock-parents as needed.
>
> Let's also update the dts file to use #include while at it.
>
> Cc: devicet...@vger.kernel.org
> Cc: Adam
The i.MX8M Mini can support SPIDF which is very similar to the
IP used on the i.MX35.
This patch adds the SPIF node.
Signed-off-by: Adam Ford
diff --git a/arch/arm64/boot/dts/freescale/imx8mm.dtsi
b/arch/arm64/boot/dts/freescale/imx8mm.dtsi
index d46e727fc362..00aad55ece65 100644
--- a/arch
The i.MX8M Mini has supports the MICFIL digital interface.
It's a 16-bit audio signal from a PDM microphone bitstream.
The driver is already in the kernel, but the node is missing.
This patch adds the micfil node.
Signed-off-by: Adam Ford
diff --git a/arch/arm64/boot/dts/freescale/imx8mm.dtsi
The i.MX8M Mini has SAI and micfil support but the drivers
are not being loaded.
This patch updates the defconfig to add support
CONFIG_SND_SOC_FSL_SAI and CONFIG_SND_SOC_FSL_MICFIL to support
these drivers.
Signed-off-by: Adam Ford
diff --git a/arch/arm64/configs/defconfig b/arch/arm64
On Fri, Mar 6, 2020 at 4:38 AM Adam Ford wrote:
>
> The Beacon EmbeddedWorks i.MX8M Mini kit has a WM8962 audio codec.
> This patch enables the required drivers as modules to enable sound.
>
> Signed-off-by: Adam Ford
>
Gentle ping. I don't know who the right person is to a
On Fri, Mar 6, 2020 at 4:59 AM Adam Ford wrote:
>
> The Beacon EmbeddedWorks Kit based on i.MX8M Mini uses an AT24
> EEPROM on one of its I2C buses.
>
> This patch enables the AT24 as a module.
>
> Signed-off-by: Adam Ford
>
Gentle ping. I don't know who th
On Fri, Mar 6, 2020 at 4:38 AM Adam Ford wrote:
>
> The i.MX8M Mini and others use the i.MX27 PWM controller.
> This patch enables it as a module so various boards can use it.
>
> Signed-off-by: Adam Ford
I don't know who the right person is to ping for this, but it's still
aw
The VersaClock driver now supports some additional bindings to support
child nodes which can configure optional settings like mode, voltage
and slew.
This patch updates the binding document to describe what is available
in the driver.
Signed-off-by: Adam Ford
Reviewed-by: Rob Herring
diff
versaclock_som.fod2
versaclock_som.out3
versaclock_som.fod1
versaclock_som.out2
versaclock_som.fod0
versaclock_som.out1
Signed-off-by: Adam Ford
---
V2: No Changes
diff --git a/drivers/clk/clk-versaclock5.c b
:
- Programmable voltage: 1.8V, 2.5V, or 3.3V
- Slew Percentage of normal: 85%, 90%, or 100%
- Output Type: LVPECL, CMOS, HCSL, or LVDS
Signed-off-by: Adam Ford
diff --git a/drivers/clk/clk-versaclock5.c b/drivers/clk/clk-versaclock5.c
index 81255d923f00..ad99d50b7b16 100644
--- a/drivers/clk/clk
On Sat, Apr 4, 2020 at 11:15 AM Adam Ford wrote:
>
> Update IDT VersaClock 5 driver to support 5P49V6965.
>
> Signed-off-by: Adam Ford
>
Gentle ping. Rob H has given the 2nd which adds the bindings his
'signed-of-by'
Once this has been approved, I'll be issuing an update to a
at this is probably not reasonable at all.
> So I will keep on hoping that NXP comes up with an upstreamable solution
> for the power domain handling.
There was a patch for upstream power-domain control from NXP a few days ago:
https://patchwork.kernel.org/cover/10904511/
Can these be somehow
U-Boot, so I had to use a custom version from
NXP's repo. Ideally, it would be nice to have everything play nicely
together so we don't have to depend on external repos like the NXP
repo on Code Auroroa. I am not complaining, but when I attempted to
push U-Boot, I mentioned that I needed
On Tue, Apr 28, 2020 at 09:45:27AM +0200, Borislav Petkov wrote:
> On Tue, Apr 21, 2020 at 03:32:34AM +0200, Adam Borowski wrote:
> > Hi!
> > With kernels compiled with gcc-10, on two different machines (AMD Phenom2,
> > AMD 2990WX) I get the following panic during boot:
>
On Thu, Oct 17, 2019 at 12:57 PM Adam Ford wrote:
>
> On Wed, Oct 16, 2019 at 1:36 PM Marcel Holtmann wrote:
> >
> > Hi Adam,
> >
> > > As nice as it would be to update firmware faster, that patch broke
> > > at least two different boards, an
On Tue, Oct 22, 2019 at 11:22 AM Tony Lindgren wrote:
>
> Hi,
>
> * Adam Ford [191007 15:06]:
> > The some in the OMAP3 family have a bandgap thermal sensor, but
> > omap2plus has it disabled.
> >
> > This patch enables the OMAP3_THERMAL by default like the re
On Mon, Sep 9, 2019 at 11:35 AM Tony Lindgren wrote:
>
> * Pali Rohár [190909 13:41]:
> > On Monday 09 September 2019 08:37:09 Adam Ford wrote:
> > > I applied this on 5.3 and it is working. I assume the same is true in
> > > for-next.
>
> Hmm I noticed I st
On Mon, Sep 23, 2019 at 8:59 AM Adam Ford wrote:
>
> The OMAP DEVICE TREE SUPPORT lists a bunch of device tree files
> with wildcard names using am3*, am4*, am5*, dra7*, and *omap*.
> Unfortunately, the LogicPD boards do not follow this convention
> so changes to these b
On Mon, Oct 21, 2019 at 3:44 AM Tomi Valkeinen wrote:
>
> On 18/10/2019 16:05, Adam Ford wrote:
> > The OMAP36xx and AM/DM37x TRMs say that the maximum divider for DSS fclk
> > (in CM_CLKSEL_DSS) is 32. Experimentation shows that this is not
> > correct, and using
files to limit the divider correctly,
but as the DSS driver also needs to know the maximum divider to be able
to iteratively find good rates, we also need to do the fix in the DSS
driver.
Signed-off-by: Adam Ford
Cc: Tomi Valkeinen
Cc: sta...@vger.kernel.org # linux-4.4.y only
diff --git a/drivers
files to limit the divider correctly,
but as the DSS driver also needs to know the maximum divider to be able
to iteratively find good rates, we also need to do the fix in the DSS
driver.
Signed-off-by: Adam Ford
Cc: Tomi Valkeinen
Cc: sta...@vger.kernel.org #linux-4.9.y+
diff --git a/drivers
On Wed, Oct 16, 2019 at 1:36 PM Marcel Holtmann wrote:
>
> Hi Adam,
>
> > As nice as it would be to update firmware faster, that patch broke
> > at least two different boards, an OMAP4+WL1285 based Motorola Droid
> > 4, as reported by Sebasian Reichel and the Logi
n be found.
thank you,
adam
On Wed, Oct 16, 2019 at 1:36 PM Marcel Holtmann wrote:
>
> Hi Adam,
>
> > As nice as it would be to update firmware faster, that patch broke
> > at least two different boards, an OMAP4+WL1285 based Motorola Droid
> > 4, as reported by Sebasian Reichel and the Logi
On Wed, Oct 2, 2019 at 3:31 PM Sebastian Reichel wrote:
>
> Hi,
>
> On Wed, Oct 02, 2019 at 06:46:26AM -0500, Adam Ford wrote:
> > As nice as it would be to update firmware faster, that patch broke
> > at least two different boards, an OMAP4+WL1285 based Motorola
.
This patch enables the snvs power key again.
Fixes: 770856f0da5d ("ARM: dts: imx6qdl: Enable SNVS power key according to
board design")
Cc: stable #5.3+
Signed-off-by: Adam Ford
diff --git a/arch/arm/boot/dts/imx6-logicpd-baseboard.dtsi
b/arch/arm/boot/dts/imx6-logicpd-baseboard.
With the removal of the panel-dpi from the omap drivers, the
LCD no longer works. This patch points the device tree to
a newly created panel named "logicpd,type28"
Fixes: 8bf4b1621178 ("drm/omap: Remove panel-dpi driver")
Signed-off-by: Adam Ford
Acked-by: Sam Ravnborg
-
This patch adds documentation of device tree bindings for the WVGA panel
Logic PD Type 28 display.
Signed-off-by: Adam Ford
---
V5: Replace GPIO_ACTIVE_HIGH with 0 to fix make dt_binding_check -k
V4: Update per Rob H's suggestions and copy other panel yaml example from
5.4-rc1
V3: Correct
On Wed, Oct 9, 2019 at 3:16 PM Tony Lindgren wrote:
>
> * Adam Ford [191009 19:28]:
> > On Wed, Oct 9, 2019 at 12:34 PM Tony Lindgren wrote:
> > > From what I recall I tested that DMA on omap3 worked fine with runtime
> > > PM for console. Certainly there are
401 - 500 of 3527 matches
Mail list logo
