Ben
On 2/28/2018 10:20 AM, Ben Hutchings wrote:
> 3.16.55-rc1 review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Adam Wallis
>
> commit 6f6a23a213be51728502b88741ba6a10cda2441d upstream.
>
> Commit adfa54
typec: tcpm: Add support for sink PPS related
> messages")
> Signed-off-by: Gustavo A. R. Silva
> ---
Good spot. :(
Acked-by: Adam Thomson
> drivers/usb/typec/tcpm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/typec/tcpm.c
From: Adam Manzanares
When the IOCB_IOPRIO flag is set because the user supplied iocb
has the RWF_IOPRIO flag is set then we set the priority value of
the kiocb from the iocb.
When a bio is created for an aio request by the block dev we set the
priority value of the bio to the user supplied
From: Adam Manzanares
This patchset interprets the aio_reqprio field of an iocb as a
per-command value iff the RWF_IOPRIO flag is set on the iocb.
This feature is implemented for a block device, but could also be
leveraged by any consumers of the iocb.
See the following link for performance
From: Adam Manzanares
This is the per-I/O equivalent of the ioprio_set system call.
When the RWF_IOPRIO flag is set then the aio_reqprio field of the iocb
is interpreted as an I/O scheduling class and priority.
Signed-off-by: Adam Manzanares
---
include/linux/fs.h | 4
include/uapi
On 30 April 2018 10:23, Akshu Agrawal wrote:
> Non-dts based systems can use ACPI DSDT to pass on the mclk
> to da7219.
> This enables da7219 mclk to be linked to system clock.
> Enable/Disable of the mclk is already handled in the codec so
> platform drivers don't have to explicitly do handling o
On 01 May 2018 21:50, Mark Brown wrote:
> On Mon, Apr 30, 2018 at 07:05:19PM +0000, Adam Thomson wrote:
>
> > There is already a means via DT to specify the MCLK for a device using the
> > generic clock DT bindings, and this driver already uses that. Should ACPI
> >
On 5/2/18 10:32 AM, Christoph Hellwig wrote:
> On Mon, Apr 30, 2018 at 09:57:39AM -0700, adam.manzana...@wdc.com wrote:
>> From: Adam Manzanares
>>
>> This is the per-I/O equivalent of the ioprio_set system call.
>>
>> When the RWF_IOPRIO flag is set then the ai
only other thing I am a bit worried about is bloating struct kiocb
> with a field for a relatively uncommon feature, but I can't really
> see any much better way to pass it.
>
I'll look more closely at reusing existing fields for the next patch
submission. I am hoping that the feature will be used more often given
that WRR for NVME should be coming soon.
Thanks,
Adam
On 03 May 2018 02:39, Mark Brown wrote:
> On Wed, May 02, 2018 at 10:13:55AM +0000, Adam Thomson wrote:
> > On 01 May 2018 21:50, Mark Brown wrote:
>
> > > There's a lot of things that ACPI *should* do but doesn't - it's a bit
> > > of a shambles ho
On Tue, May 15, 2018 at 4:25 AM, Bartosz Golaszewski wrote:
> 2018-05-14 2:40 GMT+02:00 Adam Ford :
>> On Wed, May 9, 2018 at 12:25 PM, David Lechner wrote:
>>> This series converts mach-davinci to use the common clock framework.
>>>
>>> The series works lik
On 07 May 2018 05:50, Agrawal, Akshu wrote:
Apologies for the delay in response. Please see comments below.
> On 5/4/2018 2:45 PM, Adam Thomson wrote:
> > On 03 May 2018 08:59, Akshu Agrawal wrote:
> >
> >> Non-dts based systems can use ACPI DSDT to pass on the mclk
&
For supply registration, provide of_node pointer of the port device,
via the power_supply_config structure, to allow other psy drivers
to add us as a supplier using the 'power-supplies' DT property.
Signed-off-by: Adam Thomson
---
drivers/usb/typec/tcpm.c | 1 +
1 file changed, 1
he one SoC that
> supports it.
>
> This series has been tested on TI OMAP-L138 LCDK (both device tree and legacy
> board file).
>
I am find. I don't know what I did wrong, but it's working fine. If
you want to add my 'tested-by' go ahead.
Tested-by: Adam Ford #
On Tue, Apr 24, 2018 at 11:08:34AM +0200, Paul Menzel wrote:
> On 04/24/18 04:08, Adam Borowski wrote:
> > On Mon, Apr 23, 2018 at 07:02:30PM +0200, Pavel Machek wrote:
> > > > > > > I try to decrease boot time, and my system has an SSD and enough
> > > >
>From 30886e965e7aeae8d3729c4bacf614a19e103cea Mon Sep 17 00:00:00 2001
From: Adam Borowski
Date: Wed, 25 Apr 2018 02:29:18 +0200
Subject: [PATCH] scripts: teach extract-vmlinux about LZ4 and ZSTD
Note that the LZ4 signature is different than that of modern LZ4 as we
use the "legacy"
On 25 April 2018 13:31, Greg Kroah-Hartman wrote:
> On Wed, Apr 25, 2018 at 01:26:33AM +0200, Sebastian Reichel wrote:
> > Hi Greg,
> >
> > On Tue, Apr 24, 2018 at 03:57:49PM +0200, Greg Kroah-Hartman wrote:
> > > On Mon, Apr 23, 2018 at 03:10:55PM +0100, Adam Tho
before
> the transition, resetting the controller or playing with the clock
> during transitions but it always results in the same kind of error:
>
> ohci-da8xx 1e25000.usb: frame counter not updating; disabled
> ohci-da8xx 1e25000.usb: HC died; cleaning up
> usb 1-1: USB disconnect
igate it. I can certainly live without ondemand. Using
userspace as the default governor is fine for me for now.
adam
>
> Signed-off-by: Bartosz Golaszewski
> Reviewed-by: Adam Ford
> ---
> arch/arm/boot/dts/da850-evm.dts | 13 +
> 1 file changed, 13 insertions(+)
&
On Thu, Apr 25, 2019 at 11:32:38AM +0200, Nico Schottelius wrote:
> running some IPv6 only
> networks. The systems in the IPv6 only networks do not need any IPv4
> support anymore and thus for switches/routers we turned the support off.
> Today we tried to turn off IPv4 in the Linux kernel at comp
On Thu, Apr 25, 2019 at 01:38:06AM +1000, Aleksa Sarai wrote:
> * openat(2) ignores unknown flags, meaning that old kernels will ignore
>new programs trying to use O_THISROOT and might end up causing
>security issues. Yes, it'd be trivial to check whether the new O_*
>flags are support
This driver supports the ILI2117A touch controller. This is
different than the ILI210x and it uses different register and
algorithm so it's a separate driver rather than integrating with
the other.
Signed-off-by: Adam Ford
diff --git a/drivers/input/touchscreen/Kconfig
b/drivers/
since initial get_frequency returns an error:
>
> What is the status of this series?
>
> Based on some of the replies (from Adam Ford in particular) it appears that
> this isn't ready to be merged, so is a v2 planned?
If you can leave the Logic PD Torpedo board alone and don'
f this field should provide me with the result. Is that correct?
I'm not a regular Linux kernel developer so any help on implementing
this would be appreciated.
Best regards,
Adam Romanek
ion of the
silicon is available. Maybe Sekhar can confirm.
adam
>
> Signed-off-by: Bartosz Golaszewski
> ---
> arch/arm/mach-davinci/board-da850-evm.c | 12 +---
> 1 file changed, 1 insertion(+), 11 deletions(-)
>
> diff --git a/arch/arm/mach-davinci/board-da850-evm.c
status = "okay";
> +};
I pulled part number for the processor used in the da850evm that Logic
PD produces, and it shows a imit of 375MHz. I cross-referenced the
processor part number with the description from a distributor, and the
part
where the sourcing power supply
cannot source enough current and overloads and the kit fails to
start.
Fixes: 1c207f911fe9 ("ARM: dts: imx: Add support for Logic PD
i.MX6QD EVM")
Signed-off-by: Adam Ford
diff --git a/arch/arm/boot/dts/imx6-logicpd-baseboard.dtsi
b/arch/arm/boot/dts/im
which allows the
analog microphone to capture audio.
Signed-off-by: Adam Ford
---
V2: Remove 'fixes' note reference Shawn's request.
diff --git a/arch/arm/boot/dts/imx6-logicpd-baseboard.dtsi
b/arch/arm/boot/dts/imx6-logicpd-baseboard.dtsi
index e31b6923cb72..db6b5b900826 100644
---
backlight from being
used again until the sequencer is ready. This reduces
standby power consumption by ~100mW.
Signed-off-by: Adam Ford
---
V2: Remove 'fixes' reference per Shawn's request
diff --git a/arch/arm/boot/dts/imx6q-logicpd.dts
b/arch/arm/boot/dts/imx6q-logic
t;ARM: dts: imx: Add support for Logic PD
i.MX6QD EVM")
Signed-off-by: Adam Ford
diff --git a/arch/arm/boot/dts/imx6-logicpd-baseboard.dtsi
b/arch/arm/boot/dts/imx6-logicpd-baseboard.dtsi
index db6b5b900826..7731db493cb0 100644
--- a/arch/arm/boot/dts/imx6-logicpd-baseboard.dtsi
+++ b/ar
On Wed, Apr 3, 2019 at 7:50 AM Bartosz Golaszewski wrote:
>
> śr., 27 mar 2019 o 12:14 Sekhar Nori napisał(a):
> >
> > Hi Bart,
> >
> > On 26/03/19 11:21 PM, Bartosz Golaszewski wrote:
> > > wt., 26 mar 2019 o 15:00 Adam Ford napisał(a):
> > >
; >>> capabilities of the port through the HOST_CUR control bits. If the
> >>> HOST_CUR bits are changed prior to attach, the FUSB302 automatically
> >>> indicates the programmed current capability when a device is attached.
> >>> If the current capabiliti
t; Fixes: 25aaa75df1e6 ("dmaengine: imx-sdma: add clock ratio 1:1 check")
> Signed-off-by: Andrey Smirnov
> Reviewed-by: Lucas Stach
Tested-by: Adam Ford #imx6q-logicpd
> Cc: Angus Ainslie (Purism)
> Cc: Chris Healy
> Cc: Lucas Stach
> Cc: Fabio Estevam
>
On 10 April 2019 17:39, Hans de Goede wrote:
> On 10-04-19 18:14, Adam Thomson wrote:
> > On 10 April 2019 16:45, Hans de Goede wrote:
> >
> >> Hi Kyle,
> >>
> >> On 10-04-19 14:49, Kyle Tso wrote:
> >>> On Wed, Apr 10, 2019 at 6:32 PM Adam T
On Wed, Feb 3, 2021 at 3:22 PM Adam Ford wrote:
>
> On Thu, Jan 21, 2021 at 4:24 AM Abel Vesa wrote:
> >
> > On 21-01-21 10:56:17, Sascha Hauer wrote:
> > > On Wed, Jan 20, 2021 at 06:14:21PM +0200, Abel Vesa wrote:
> > > > On 21-01-20 16:50:01, Sascha Haue
add the additional optional clock, and explicitly
name both of them.
Signed-off-by: Adam Ford
Reviewed-by: Geert Uytterhoeven
Acked-by: Rob Herring
---
V3: No Change
V2: No Change
diff --git a/Documentation/devicetree/bindings/net/renesas,etheravb.yaml
b/Documentation/devicetree/bindings/net
The bindings have been updated to support two clocks, but the
original clock now requires the name fck. Add a clock-names
list in the device tree with fck in it.
Signed-off-by: Adam Ford
Reviewed-by: Geert Uytterhoeven
---
V3: No Change
V2: No Change
diff --git a/arch/arm64/boot/dts/renesas
For devices that use a programmable clock for the AVB reference clock,
the driver may need to enable them. Add code to find the optional clock
and enable it when available.
Signed-off-by: Adam Ford
---
V3: Change 'avb' to 'AVB'
Remove unnessary else statement and p
The AVB refererence clock assumes an external clock that runs
automatically. Because the Versaclock is wired to provide the
AVB refclock, the device tree needs to reference it in order for the
driver to start the clock.
Signed-off-by: Adam Ford
---
V3: New to series
diff --git a/arch/arm64
The bindings have been updated to support two clocks, but the
original clock now requires the name fck. Add a clock-names
list in the device tree with fck in it.
Signed-off-by: Adam Ford
Reviewed-by: Geert Uytterhoeven
---
V3: No Change
V2: No Change
diff --git a/arch/arm/boot/dts/r8a7742
On Wed, Feb 10, 2021 at 2:18 PM Rob Herring wrote:
>
> On Sun, Feb 07, 2021 at 12:51:38PM -0600, Adam Ford wrote:
> > There are two registers which can set the load capacitance for
> > XTAL1 and XTAL2. These are optional registers when using an
> > external crystal. Si
a wrote:
> > > > > On 21-01-20 16:13:05, Sascha Hauer wrote:
> > > > > > Hi Abel,
> > > > > >
> > > > > > On Wed, Jan 20, 2021 at 04:44:54PM +0200, Abel Vesa wrote:
> > > > > > &g
atency issue described above.
>
> This patch enables the I2C bus mode if I2C_FUNC_I2C is set or
> otherwise enables the SMBus mode for a native SMBus controller
> which doesn't have I2C_FUNC_I2C set.
>
> Signed-off-by: Hubert Streidl
> Signed-off-by: Mark Jonas
> ---
>
On Mon, Feb 08, 2021 at 07:08:05AM +, Wadepohl, Wolfram wrote:
> I'm sad to hear that 5.10 has still an EOL of Dec, 2022. We are in
> development of our 1st GNU/Linux based System, 50k devices for IoT.
[...]
> In general a 2 year support for embedded systems in automation is not a
> reasonable
atency issue described above.
>
> This patch enables the I2C bus mode if I2C_FUNC_I2C is set or
> otherwise enables the SMBus mode for a native SMBus controller
> which doesn't have I2C_FUNC_I2C set.
>
> Signed-off-by: Hubert Streidl
> Signed-off-by: Mark Jonas
Thanks for your efforts. Looks sensible to me, so:
Reviewed-by: Adam Thomson
other hardware driver 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
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
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
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
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
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
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
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 alert
d slg51000-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/d
o increase the temperatures for extended
temperature ratings, these can be changed on their respective
device trees with something like:
&cpu_alert0 {
temperature = <9>; /* millicelsius */
};
&cpu_crit {
temperature = <105000>; /* millicelsius */
};
Signed-o
eeded.
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 @@
#in
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
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
> > w
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
eeded.
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..9404631be
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
On Mon, Jan 4, 2021 at 1:12 AM Sascha Hauer wrote:
>
> Hi Adam,
>
> On Tue, Dec 29, 2020 at 08:51:28AM -0600, Adam Ford wrote:
> > Remove the earlycon uart clocks that are hard cord in platforms
> > clock driver, instead of parsing the earlycon uart port from dt
>
&g
MODULE_STATE_LIVE, mod);
- /* Delay uevent until module has finished its init routine */
- kobject_uevent(&mod->mkobj.kobj, KOBJ_ADD);
-
/*
* We need to finish all async code before the module init sequence
* is done. This has potential to deadlock. For example, a newly
Thanks,
Adam
--
pi3 (pi3ki31ny) - pi3 (at) itsec pl
http://pi3.com.pl
On Sat, Jan 9, 2021 at 12:02 PM Luca Ceresoli wrote:
>
> Hi Adam,
>
> On 09/01/21 04:00, Adam Ford wrote:
> > On Fri, Jan 8, 2021 at 4:49 PM Luca Ceresoli wrote:
> >>
> >> Hi Adam,
> >>
> >> On 06/01/21 18:39, Adam Ford wrote:
> >>&
Hello,
On Mon, Jan 11, 2021 at 03:20:48PM +0100, Jessica Yu wrote:
> +++ Adam Zabrocki [10/01/21 18:54 +0100]:
> > Hello,
> >
> > I believe that the following commit does introduce a gentle "functionality
> > bug":
> >
> > "module: delay k
onfuse them.
Right. The same can happen when text section is being actively modified.
However, this case could be covered by running the optimizer logic under
text_mutex.
> But if the gcc uses int3 to pad the room between functions, it should be
> reconsidered.
>
Looks like it's a de
le which implies to me that the SPBA needs to
start at the same place as the AIPS1, but AIPS1 goes from 3000_ to
303F_, so the spba-bus is a subset of the AIPS1.
NXP/Freescale has a variety of SoC's that use the SPBA and in every
instance, they do it this way. Having the spba-bus
050e0 r ftrace_enable_sysctl+0x0[OPTIMIZED]
root@pi3:~/off-debug/git/lkrg#
gef➤ x/2i ftrace_enable_sysctl
0x813050e0 : jmp0xc062807a
0x813050e5 : push r14
Thanks,
Adam
On Fri, Dec 11, 2020 at 11:39:15AM -0800, Kees Cook wrote:
> On Fri, Dec 11, 20
The SoC expects the txv_refclk is provided, but if it is provided
by a programmable clock, there needs to be a way to get and enable
this clock to operate. It needs to be optional since it's only
necessary for those with programmable clocks.
Signed-off-by: Adam Ford
diff --git a/driver
On Sat, Dec 12, 2020 at 11:55 AM Sergei Shtylyov
wrote:
>
> Hello!
>
> On 12.12.2020 19:56, Adam Ford wrote:
>
> > The SoC expects the txv_refclk is provided, but if it is provided
> > by a programmable clock, there needs to be a way to get and enable
> > this
On Fri, Dec 18, 2020 at 7:16 AM Geert Uytterhoeven wrote:
>
> Hi Adam,
>
> CC Shimoda-san
>
> On Thu, Dec 17, 2020 at 12:52 PM Adam Ford wrote:
> > On Thu, Dec 17, 2020 at 2:16 AM Geert Uytterhoeven
> > wrote:
> > > On Wed, Dec 16, 2020 at 6:03 PM Adam Fo
On Thu, Dec 17, 2020 at 5:49 AM Geert Uytterhoeven wrote:
>
> Hi Adam,
>
> On Sun, Dec 13, 2020 at 7:38 PM Adam Ford wrote:
> > Beacon EmebeddedWorks is introducing a new kit based on the
> > RZ/G2N SoC from Renesas.
> >
> > The SOM supports eMMC, WiF
On Fri, Dec 04, 2020 at 10:10:16AM +0100, Greg Kroah-Hartman wrote:
> On Fri, Dec 04, 2020 at 09:51:07AM +0100, Jiri Slaby wrote:
> > > > > On Fri, Dec 04, 2020 at 08:22:41AM +0100, Jiri Slaby wrote:
> > > > > > On 03. 12. 20, 3:03, Jann Horn wrote:
> > > > > > > Delete this dead code; but leave th
On Sun, Dec 6, 2020 at 11:24 PM Sascha Hauer wrote:
>
> Hi Adam,
>
> On Fri, Dec 04, 2020 at 12:31:54PM -0600, Adam Ford wrote:
> > The default clock source on i.MX8M Mini and Nano boards use a 24MHz clock,
> > but users who need to re-parent the clock source run into is
This patch fixes a couple of bugs in the DA9121 driver.
One in an uninialised string I forgot to remove when changing to of_parse_cb()
The other is an index for an optional DT property which overflows
Adam Ward (2):
regulator: da9121: Remove uninitialised string variable
regulator: da9121
Signed-off-by: Adam Ward
---
drivers/regulator/da9121-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/da9121-regulator.c
b/drivers/regulator/da9121-regulator.c
index ed68259..9d5b02f 100644
--- a/drivers/regulator/da9121-regulator.c
+++ b
Erroneously left in when switched to using of_parse_cb()
Signed-off-by: Adam Ward
---
drivers/regulator/da9121-regulator.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/regulator/da9121-regulator.c
b/drivers/regulator/da9121-regulator.c
index db1c2cc..ed68259
Acked-by: Adam Ward
> -Original Message-
> From: Dan Carpenter
> Sent: 07 December 2020 17:56
> To: Support Opensource ; Adam Ward
>
> Cc: Liam Girdwood ; Mark Brown
> ; linux-kernel@vger.kernel.org; kernel-
> janit...@vger.kernel.org
> Subject: [PATCH] r
On Mon, Dec 07, 2020 at 17:58PM, Rob Herring wrote:
> > +properties:
> > + regulator-mode:
> > +maxItems: 1
> > +description: Defined in
> > include/dt-bindings/regulator/dlg,da9121-
> regulator.h
>
> 'regulator-mode' is defined as a property of a
> 'regul
The RZ/G2 Series has the optional CLK_RCAR_USB2_CLOCK_SEL.
Enable it by default. It's disabled by default in the
the device tree, so it should be safe to enable it here.
Signed-off-by: Adam Ford
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 8383016
On Tue, Jan 12, 2021 at 10:45 AM Luca Ceresoli wrote:
>
> Hi Adam,
>
> On 11/01/21 17:40, Adam Ford wrote:
> > On Sat, Jan 9, 2021 at 12:02 PM Luca Ceresoli wrote:
> >>
> >> Hi Adam,
> >>
> >> On 09/01/21 04:00, Adam Ford wrote:
> >&
nt and can be integrity-checked as soon as the module is LIVE.
To make all of these projects happy at once, move the kobject KOBJ_ADD
uevent to just before sending the MODULE_STATE_LIVE notification.
Fixes: 38dc717e9715 ("module: delay kobject uevent until after module init
call")
On Tue, Jan 12, 2021 at 9:16 PM Rob Herring wrote:
>
> On Wed, Jan 06, 2021 at 11:38:59AM -0600, Adam Ford wrote:
> > There are two registers which can set the load capacitance for
> > XTAL1 and XTAL2. These are optional registers when using an
> > external crystal.
On Mon, Jan 18, 2021 at 6:52 AM Abel Vesa wrote:
>
> On 21-01-15 12:29:08, Adam Ford wrote:
>
> ...
>
> > diff --git a/drivers/clk/imx/clk-imx25.c b/drivers/clk/imx/clk-imx25.c
> > index a66cabfbf94f..66192fe0a898 100644
> > --- a/drivers/clk/imx/clk-imx25.c
>
On Sat, Jan 16, 2021 at 3:55 PM Adam Ford wrote:
>
> There are two registers which can set the load capacitance for
> XTAL1 and XTAL2. These are optional registers when using an
> external crystal. Parse the device tree and set the
> corresponding registers accordingly.
>
>
There are two registers which can set the load capacitance for
XTAL1 and XTAL2. These are optional registers when using an
external crystal. Parse the device tree and set the
corresponding registers accordingly.
Signed-off-by: Adam Ford
---
V2: Make the math subtract 9000 since we have a
There are two registers which can set the load capacitance for
XTAL1 and XTAL2. These are optional registers when using an
external crystal. Since XTAL1 and XTAL2 will set to the same value,
update the binding to support a single property called
xtal-load-femtofarads.
Signed-off-by: Adam Ford
There is a QSPI chip connected to the FlexSPI bus. Enable it.
Signed-off-by: Adam Ford
diff --git a/arch/arm64/boot/dts/freescale/imx8mn-beacon-som.dtsi
b/arch/arm64/boot/dts/freescale/imx8mn-beacon-som.dtsi
index 2120e6485393..9f575184d899 100644
--- a/arch/arm64/boot/dts/freescale/imx8mn
The i.MX8M Nano has the same Flexspi controller used in the i.MX8M
Mini. Add the node and disable it by default.
Signed-off-by: Adam Ford
diff --git a/arch/arm64/boot/dts/freescale/imx8mn.dtsi
b/arch/arm64/boot/dts/freescale/imx8mn.dtsi
index 3fac73779fdd..16ea50089567 100644
--- a/arch/arm64
On 08 January 2021 08:53, Xu Wang wrote:
> Because clk_prepare_enable() and clk_disable_unprepare() already checked
> NULL clock parameter, so the additional checks are unnecessary, just
> remove them.
>
> Signed-off-by: Xu Wang
> ---
> sound/soc/codecs/da7218.c | 13 +
> sound/
On Fri, Jan 8, 2021 at 1:22 AM Tony Lindgren wrote:
>
> * H. Nikolaus Schaller [201230 13:29]:
> > > Am 30.12.2020 um 13:55 schrieb Adam Ford :
> > > On Wed, Dec 30, 2020 at 2:43 AM Tony Lindgren wrote:
> > >>
> > >> At least for 4430, try
On Fri, Jan 8, 2021 at 7:45 AM Adam Ford wrote:
>
> On Fri, Jan 8, 2021 at 1:22 AM Tony Lindgren wrote:
> >
> > * H. Nikolaus Schaller [201230 13:29]:
> > > > Am 30.12.2020 um 13:55 schrieb Adam Ford :
> > > > On Wed, Dec 30, 2020 at 2:43 AM Tony Lindg
random issues where nobody took care to debug them.
> > >
> > > That would be since v4.11.
> >
> > I guess maybe best is to include both. Then if someone is debugging
> > why their async probe is failing they will notice this commit, but
> > they also might decide to pick it earlier just to be safe...
>
> OK I'll add the above fixes tag too and apply this into fixes.
>
It might be too late, but...
Tested-by: Adam Ford #logicpd-torpedo-37xx-devkit
> Thanks,
>
> Tony
On Fri, Jan 8, 2021 at 12:31 PM Adam Ford wrote:
>
> On Fri, Jan 8, 2021 at 7:45 AM Adam Ford wrote:
> >
> > On Fri, Jan 8, 2021 at 1:22 AM Tony Lindgren wrote:
> > >
> > > * H. Nikolaus Schaller [201230 13:29]:
> > > > > Am 30.12.2020 um
On Fri, Jan 8, 2021 at 4:49 PM Luca Ceresoli wrote:
>
> Hi Adam,
>
> On 06/01/21 18:38, Adam Ford wrote:
> > There are two registers which can set the load capacitance for
> > XTAL1 and XTAL2. These are optional registers when using an
> > external crystal. Updat
On Fri, Jan 8, 2021 at 4:49 PM Luca Ceresoli wrote:
>
> Hi Adam,
>
> On 06/01/21 18:39, Adam Ford wrote:
> > There are two registers which can set the load capacitance for
> > XTAL1 and XTAL2. These are optional registers when using an
> > external crystal. Par
On Fri, Jan 8, 2021 at 1:37 PM Andreas Kemnade wrote:
>
> Hi,
>
> On Fri, 8 Jan 2021 13:17:06 -0600
> Adam Ford wrote:
>
> > On Mon, Dec 7, 2020 at 8:01 AM Tony Lindgren wrote:
> > >
> > > * Doug Anderson [201204 16:43]:
> > > > Hi,
.
Signed-off-by: Adam Ford
diff --git a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
index 3a5228562b0d..3451f9be104e 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
+++ b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
@@ -70,6 +70,7 @@ nand@0,0
On Sat, Jan 9, 2021 at 10:39 AM Adam Ford wrote:
>
> Previously, the 1GHz variants were marked as a turbo,
> because that variant has reduced thermal operating range.
>
> Now that the thermal throttling is in place, it should be
> safe to remove the turbo-mode from the 1GHz
701 - 800 of 2101 matches
Mail list logo
