Add usb otg support for bananapi-m64 board,
- USB-ID connected with PH9
- USB-DRVVBUS controlled by N_VBUSEN pin from PMIC
Signed-off-by: Jagan Teki
---
Changes for v3:
- Move the position of reg_drivevbus as per binding documentation.
Changes for v2:
- add drvvbus regulator
- add N_VBUSEN pin
Add reg_drivevbus regualtor for boards which are using
external regulator to drive the OTG VBus through N_VBUSEN
PMIC pin.
Signed-off-by: Jagan Teki
---
Changes for v3:
- none
arch/arm64/boot/dts/allwinner/axp803.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/
Wait for the syncronization of all clocks when resuming, not only the
UPLL clock. Do not use regmap_read_poll_timeout, as it will call BUG()
when interrupts are masked, which is the case in here.
Signed-off-by: Romain Izard
Acked-by: Ludovic Desroches
Acked-by: Nicolas Ferre
---
drivers/clk/at
From: Michal Kubecek
Date: Mon, 11 Dec 2017 17:13:50 +0100
> On Wed, Dec 06, 2017 at 03:57:14PM -0500, David Miller wrote:
>> From: Kevin Cernekee
>> Date: Wed, 6 Dec 2017 12:12:27 -0800
>>
>> > Currently, a nlmon link inside a child namespace can observe systemwide
>> > netlink activity. Fil
Den 10.12.2017 23.10, skrev David Lechner:
This adds a new device tree binding for Sitronix ST7735R display panels,
such as the Adafruit 1.8" TFT.
Signed-off-by: David Lechner
Acked-by: Rob Herring
---
v2: changes:
* None, but...
I'm wondering about my choice of compatible here. I chose the
On Mon, Dec 11, 2017 at 02:59:13PM +0200, Mathias Nyman wrote:
> On 11.12.2017 13:27, Arnd Bergmann wrote:
> > gcc-8 warnings about the new driver using a memset with a bogus length:
> >
> > drivers/usb/host/xhci-dbgcap.c: In function 'xhci_dbc_eps_exit':
> > drivers/usb/host/xhci-dbgcap.c:369:2:
From: Jiri Pirko
Date: Mon, 11 Dec 2017 17:32:46 +0100
> I think that it does not make sense to convert ethtool->netlink_ethtool
> 1:1 feature wise. Now we have devlink, ritch switch representation
> model, tc offload and many others. Lot of things that are in
> ethtool, should be done in devlink
On Mon, Dec 11, 2017 at 01:30:03PM +0800, Huang, Ying wrote:
> Andrew Morton writes:
>
> > On Fri, 08 Dec 2017 16:41:38 +0800 "Huang\, Ying"
> > wrote:
> >
> >> > Why do we need srcu here? Is it enough with rcu like below?
> >> >
> >> > It might have a bug/room to be optimized about performance
On Mon, Dec 11, 2017 at 6:01 PM, Greg Kroah-Hartman
wrote:
> On Mon, Dec 11, 2017 at 02:59:13PM +0200, Mathias Nyman wrote:
>> On 11.12.2017 13:27, Arnd Bergmann wrote:
>> > gcc-8 warnings about the new driver using a memset with a bogus length:
>> >
>> > drivers/usb/host/xhci-dbgcap.c: In functio
On Mon, 11 Dec 2017 18:00:22 +0100,
Vinod Koul wrote:
>
> On Mon, Dec 11, 2017 at 05:10:17PM +0100, Takashi Iwai wrote:
> > On Wed, 06 Dec 2017 16:47:00 +0100,
> > Vinod Koul wrote:
> > >
> > > + /* TODO: Read audio mode */
> > > +
> > > + i++;
> > > + }
> >
> > Don't we use coun
On 11/12/17 16:29, Sinan Kaya wrote:
> Hi Chris,
>
>>
>> I'm more than happy to provide additional diagnostics and test proposed
>> fixes. As a starter for ten, I've attached the
>> output from 'lspci -v'. If, however, you need to see the backtrace, I'll
>> need some advice on how to capture t
Em Mon, Dec 11, 2017 at 01:43:12PM -0200, Arnaldo de Melo escreveu:
> Em Fri, Dec 08, 2017 at 06:48:17PM +0100, Michael Petlan escreveu:
> > Hi Arnaldo, so I have tried what you've suggested and looks good.
> > Patch is attached. Sorry for not posting it in-text, but I need to
> > fix my mail clien
On Mon, Dec 11, 2017 at 10:56:33AM +0100, Vitaly Kuznetsov wrote:
> Roman Kagan writes:
> > On Fri, Dec 08, 2017 at 11:49:57AM +0100, Vitaly Kuznetsov wrote:
> >> +void register_hv_tsc_update(void (*cb)(void))
> >> +{
> >
> > The function name seems unfortunate. IMHO such a name suggests
> > regi
Adding linux-rt-users group to thread.
From: Jonathan Haws
Sent: Monday, December 11, 2017 08:37
To: mi...@kernel.org; v...@zeniv.linux.org.uk; a...@arndb.de;
a...@linux-foundation.org; deepa.ker...@gmail.com
Cc: linux-kernel@vger.kernel.org; t...@linutron
From: Branislav Radocaj
Date: Sat, 9 Dec 2017 12:51:33 +0100
> If clk_set_rate() fails, we should disable clk before return.
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Branislav Radocaj
> ---
>
> Changes since v2:
> * Improved inconsistent failure hand
On Mon, Dec 11, 2017 at 06:06:30PM +0100, Takashi Iwai wrote:
> On Mon, 11 Dec 2017 18:00:22 +0100,
> Vinod Koul wrote:
> >
> > On Mon, Dec 11, 2017 at 05:10:17PM +0100, Takashi Iwai wrote:
> > > On Wed, 06 Dec 2017 16:47:00 +0100,
> > > Vinod Koul wrote:
> > > >
> > > > + /* TODO:
On 11/12/17 07:58 AM, Allen Hubbe wrote:
!IS_ALIGNED(addr, BIT_ULL(xlate_pos))
Ok, yes, that's much better. I'll change it. Thanks.
+ /*
+* In certain circumstances we can get a buffer that is
+* not aligned to its size. (Most of the time
+
On Thursday, November 30, 2017 4:52 PM, Lukasz Majewski wrote:
>
> The BK3 board is a derivative of the ts72xx reference design.
Lukasz,
I was just reviewing the other TS-72xx boards and noticed this:
> +/* BK3 specific defines */
> +#define BK3_CPLDVER_PHYS_BASE0x2340
> +#
[+cc linux-pci]
On Mon, Dec 11, 2017 at 11:29:50AM -0500, Sinan Kaya wrote:
> Hi Chris,
>
> >
> > I'm more than happy to provide additional diagnostics and test proposed
> > fixes. As a starter for ten, I've attached the
> > output from 'lspci -v'. If, however, you need to see the backtrace, I'
This series moves the watchdog restart code from arch/arm/mach-davinci
to drivers/watchdog.
Tested working on LEGO MINDSTORMS EV3 (TI AM1808 processor).
David Lechner (2):
watchdog: davinci_wdt: add restart function
ARM: davinci: remove watchdog reset
arch/arm/mach-davinci/board-da830-evm.c
This adds a restart function to the davinci watchdog timer driver.
This is copied from arch/arm/mach-davinci/time.c and will allow us to
remove the code from there.
Signed-off-by: David Lechner
---
drivers/watchdog/davinci_wdt.c | 38 ++
1 file changed, 38 in
This removes the watchdog reset code. The reset has been moved to
drivers/watchdog/davinci_wdt.c. The watchdog driver registers the reset
with the kernel so defining a reset for each machine is no longer needed.
Signed-off-by: David Lechner
---
arch/arm/mach-davinci/board-da830-evm.c | 1 -
On Mon, Dec 11, 2017 at 11:58:37AM -0500, David Miller wrote:
> From: Michal Kubecek
> Date: Mon, 11 Dec 2017 17:13:50 +0100
>
> > On Wed, Dec 06, 2017 at 03:57:14PM -0500, David Miller wrote:
> >> From: Kevin Cernekee
> >> Date: Wed, 6 Dec 2017 12:12:27 -0800
> >>
> >> > Currently, a nlmon li
This is a clean-up patch which replaces DEVICE_ATTR() macro with file
permission specific DEVICE_ATTR_RO() macro for compaction and
readability.
Done using coccinelle:
@r@
identifier attr, show_fn;
declarer name DEVICE_ATTR;
@@
DEVICE_ATTR(attr, \(S_IRUGO\|0444\), show_fn, NULL);
@script: pytho
On 12/11/2017 12:06 PM, Chris Clayton wrote:
> Here's the output of dmesg for 4.15.0-rc3. I'll open a bugzilla later and add
> this and the lspci output that I sent with
> my original repoart.
This was helpful. I don't see any AER/DPC in your log. It looks like the only
PCIe
portdrv service you
On Wed, 6 Dec 2017, Maciej W. Rozycki wrote:
> > > 2. Actually assert what we rely on having been enforced by generic code,
> > >i.e.:
> > >
> > > BUG_ON(*count % sizeof(elf_fpreg_t));
> > > for (i = 0; i < NUM_FPU_REGS && *count > 0; i++) {
> > > err = user_regset_copyin(pos,
On 12/11/2017 05:49 AM, Ingo Molnar wrote:
>
> * Randy Dunlap wrote:
>
>> From: Randy Dunlap
>>
>> Update x86-opcode-map.txt based on the October 2017 Intel SDM publication.
>> Correct INVPID to INVVPID.
>> Add UD0, UD1, and UD2 instruction opcodes.
>>
>> Signed-off-by: Randy Dunlap
>> Cc: Mas
On 12/11/2017 02:19 AM, Daniel Borkmann wrote:
> Hi Randy, hi Richard, [ +Hendrik for c895f6f703ad7dd2f ]
>
> On 12/11/2017 09:32 AM, Richard Weinberger wrote:
>> Randy,
>>
>> Am Montag, 11. Dezember 2017, 03:42:12 CET schrieb Randy Dunlap:
>>> On 12/10/2017 06:08 PM, Linus Torvalds wrote:
An
Tomasz please add the wireless version in your next patch, a web search
shows it's called M-XT3DRBK and the USB ID is 0x00fc.
Thanks,
Alex
On Mon, Dec 11, 2017 at 11:28:37AM +0100, Jiri Kosina wrote:
> On Sat, 9 Dec 2017, Tomasz Kramkowski wrote:
>
> > Alright, that's fine. Anything else to chan
Op 11-12-17 om 12:06 schreef Thomas Gleixner:
> On Mon, 11 Dec 2017, Thomas Gleixner wrote:
>
>> On Mon, 11 Dec 2017, Daniel Vetter wrote:
>>> Anything else we can do to move this? I just had to resolve a small
>>> conflict when moving forward to -rc3. Carrying a revert for the entire
>>> apic pull
On 12/11/2017 06:27 PM, Randy Dunlap wrote:
> On 12/11/2017 02:19 AM, Daniel Borkmann wrote:
>> Hi Randy, hi Richard, [ +Hendrik for c895f6f703ad7dd2f ]
>>
>> On 12/11/2017 09:32 AM, Richard Weinberger wrote:
>>> Randy,
>>>
>>> Am Montag, 11. Dezember 2017, 03:42:12 CET schrieb Randy Dunlap:
O
On 12/10/2017 01:51 PM, Nicolas Iooss wrote:
In rtl_rx_ampdu_apply(), when rtlpriv->cfg->ops->get_btc_status()
returns false, RT_TRACE() is called with the values of variables
reject_agg and agg_size, which have not been initialized.
Always initialize these variables in order to prevent using
un
Document the bindings for the Synopsys DesignWare HDMI RX.
Signed-off-by: Jose Abreu
Acked-by: Rob Herring (v8)
Cc: Joao Pinto
Cc: Rob Herring
Cc: Mark Rutland
Cc: Mauro Carvalho Chehab
Cc: Hans Verkuil
Cc: Sylwester Nawrocki
Cc: devicet...@vger.kernel.org
---
Changes from v7:
- Re
The Synopsys DesignWare HDMI RX controller is an HDMI receiver controller that
is responsible to process digital data that comes from a phy. The final result
is a stream of RAW video data that can then be connected to a video DMA, for
example, and transfered into RAM so that it can be displayed.
T
This adds support for the Synopsys DesignWare HDMI RX PHY e405. This
phy receives and decodes HDMI video that is delivered to a controller.
Main features included in this driver are:
- Equalizer algorithm that chooses the phy best settings
according to the detected HDMI cable chara
Add an entry for Synopsys DesignWare HDMI Receivers drivers
and phys.
Signed-off-by: Jose Abreu
Cc: Joao Pinto
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7a52a66..a1675bc 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -13108,6 +1310
This is an initial submission for the Synopsys DesignWare HDMI RX
Controller Driver. This driver interacts with a phy driver so that
a communication between them is created and a video pipeline is
configured.
The controller + phy pipeline can then be integrated into a fully
featured system that ca
On Thu, Dec 07, 2017 at 08:00:50PM -0500, Martin K. Petersen wrote:
>
> > I'm perfectly OK with taking it through the SCSI tree. Probably the
> > path of least resistance.
>
> Applied to 4.16/scsi-queue and rebased so it sits before Bart's patch.
Thank you! I have removed this patch from -rcu.
On Mon, Dec 11, 2017 at 09:50:20PM +0900, Sergey Senozhatsky wrote:
> print_symbol() uses extra stack space to sprintf() symbol
> information and then to feed that buffer to printk()
>
> char buffer[KSYM_SYMBOL_LEN];
>
> sprint_symbol(buffer, address);
> printk(fmt, buffer);
>
> Replace pr
On Mon, Dec 11, 2017 at 03:16:29PM +, Mark Brown wrote:
> On Mon, Dec 11, 2017 at 06:21:58PM +0900, Katsuhiro Suzuki wrote:
>
> > But I can't find how to use/map this DAI in machine driver or Device-Tree or
> > something. I think that it's same as PCM DAI, am I correct?
>
> Yes, that probably
So, before this,
On 12/10/2017 10:47 PM, Andy Lutomirski wrote:
...> + if (unlikely(ldt)) {
> + if (static_cpu_has_bug(X86_BUG_CPU_SECURE_MODE_PTI)) {
> + if (WARN_ON_ONCE((unsigned long)ldt->slot > 1)) {
> + clear_LDT();
> +
Hi Namhyung,
On Tue, 2017-12-12 at 00:17 +0900, Namhyung Kim wrote:
> Hi Tom,
>
> On Wed, Dec 06, 2017 at 04:38:03PM -0600, Tom Zanussi wrote:
> > Add the necessary infrastructure to allow the variables defined on one
> > event to be referenced in another. This allows variables set by a
> > prev
On Wed, Dec 06, 2017 at 12:35:19PM +, Will Deacon wrote:
> Patches are also pushed here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git kpti
>
> Feedback and testing welcome. At this point, I'd like to start thinking
> about getting this merged for 4.16.
For the record, t
Mon, Dec 11, 2017 at 06:01:44PM CET, da...@davemloft.net wrote:
>From: Jiri Pirko
>Date: Mon, 11 Dec 2017 17:32:46 +0100
>
>> I think that it does not make sense to convert ethtool->netlink_ethtool
>> 1:1 feature wise. Now we have devlink, ritch switch representation
>> model, tc offload and many
On 12/8/17 1:16 AM, Andrey Ryabinin wrote:
On 12/08/2017 11:26 AM, Dmitry Vyukov wrote:
On Fri, Dec 8, 2017 at 12:40 AM, Matthew Wilcox wrote:
On Fri, Dec 08, 2017 at 07:30:07AM +0800, Yang Shi wrote:
When running stress test with KASAN enabled, the below softlockup may
happen occasionally:
Mon, Dec 11, 2017 at 05:56:51PM CET, da...@davemloft.net wrote:
>From: Jiri Pirko
>Date: Mon, 11 Dec 2017 17:02:21 +0100
>
>> Mon, Dec 11, 2017 at 02:53:31PM CET, mkube...@suse.cz wrote:
>>>No function implemented yet, only genetlink and module infrastructure.
>>>Register/unregister genetlink fami
Removing these two lines from the initialization of
field_to_offset_table[] means that vmcs_field_to_offset() will return
-ENOENT for IO_BITMAP_A or IO_BITMAP_B. Hence, handle_vmread and
handle_vmwrite will incorrectly report these fields as unsupported
VMCS components if an L1 hypervisor tries to
On Mon, 11 Dec 2017 14:22:30 +
"Wang, Liang-min" wrote:
> > -Original Message-
> > From: Alex Williamson [mailto:alex.william...@redhat.com]
> > Sent: Friday, December 08, 2017 6:35 PM
> > To: Alexander Duyck
> > Cc: Kirsher, Jeffrey T ; Wang, Liang-min
> > > min.w...@intel.com>; k
On Wed, 06 Dec 2017 18:31:10 PST (-0800), noner...@gmail.com wrote:
This patch contains basic ftrace support for RV64I platform.
Specifically, function tracer (HAVE_FUNCTION_TRACER), function graph
tracer (HAVE_FUNCTION_GRAPH_TRACER), and a frame pointer test
(HAVE_FUNCTION_GRAPH_FP_TEST) are imp
Am Montag, 11. Dezember 2017, 18:27:40 CET schrieb Randy Dunlap:
> On 12/11/2017 02:19 AM, Daniel Borkmann wrote:
> > Hi Randy, hi Richard, [ +Hendrik for c895f6f703ad7dd2f ]
> >
> > On 12/11/2017 09:32 AM, Richard Weinberger wrote:
> >> Randy,
> >>
> >> Am Montag, 11. Dezember 2017, 03:42:12 CET
Em Fri, Dec 08, 2017 at 08:49:46AM -0600, Paul Clarke escreveu:
>
>
> On 12/07/2017 09:01 PM, Masami Hiramatsu wrote:
> > On Thu, 7 Dec 2017 10:34:51 -0600
> > Paul Clarke wrote:
> >> On 12/07/2017 01:20 AM, Masami Hiramatsu wrote:
> >>> Cut off the version suffix (e.g. @GLIBC_2.2.5 etc.) from
>
This adds the devicetree bindings for the LM3692x
I2C LED string driver.
Acked-by: Pavel Machek
Signed-off-by: Dan Murphy
---
v9 - Moved 2 nodes to Optional Child and renamed node names to device type
https://patchwork.kernel.org/patch/10093757/
v8 - Added address-cells and size-cells as well
Introducing the LM3692x Dual-String white LED driver.
Data sheet is located
http://www.ti.com/lit/ds/snvsa29/snvsa29.pdf
Signed-off-by: Dan Murphy
---
v9 - Change the no DT label case to pull the device name from the i2c_id struct
so that the device name can be part of the sysfs node -
https:/
From: Gustavo Padovan
Hi,
One more iteration of the explicit fences patches, please refer
to the previous version[1] for more details about the general
mechanism
This version makes the patchset and the implementation much more
simple, to start we are not using a ordered capability anymore,
but
From: Gustavo Padovan
For explicit synchronization it important for userspace to know if the
format being used by the driver can deliver the buffers back to userspace
in the same order they were queued with QBUF.
Ordered streams fits nicely in a pipeline with DRM for example, where
ordered buffe
From: Gustavo Padovan
Receive in-fence from userspace and add support for waiting on them
before queueing the buffer to the driver. Buffers can't be queued to the
driver before its fences signal. And a buffer can't be queue to the driver
out of the order they were queued from userspace. That mean
From: Gustavo Padovan
Add section to VIDIOC_QBUF about it
v5:
- Remove V4L2_CAP_ORDERED
- Add doc about V4L2_FMT_FLAG_UNORDERED
v4:
- Document ordering behavior for in-fences
- Document V4L2_CAP_ORDERED capability
- Remove doc about OUT_FENCE event
From: Gustavo Padovan
If V4L2_BUF_FLAG_OUT_FENCE flag is present on the QBUF call we create
an out_fence and send its fd to userspace on the fence_fd field as a
return arg for the QBUF call.
The fence is signaled on buffer_done(), when the job on the buffer is
finished.
v7:
- merge patc
From: Gustavo Padovan
Turn the reserved2 field into fence_fd that we will use to send
an in-fence to the kernel and return an out-fence from the kernel to
userspace.
Two new flags were added, V4L2_BUF_FLAG_IN_FENCE, that should be used
when sending a fence to the kernel to be waited on, and
V4L2
From: Gustavo Padovan
Explicit synchronization benefits a lot from ordered queues, they fit
better in a pipeline with DRM for example so create a opt-in way for
drivers notify videobuf2 that the queue is unordered.
Drivers don't need implement it if the queue is ordered.
Signed-off-by: Gustavo
On 11/12/17 09:30, Rasmus Villemoes wrote:
> On 2017-12-08 17:02, Marc Zyngier wrote:
[...]
>> Overall, it is a bit annoying that you just copied the driver altogether
>> instead of trying to allow the common stuff to be shared between
>> drivers. Most of this is just boilerplate code...
>
> Yes
On Mon, Dec 11, 2017 at 6:22 AM, Rafael J. Wysocki wrote:
> On Sunday, December 10, 2017 10:58:23 PM CET Andy Lutomirski wrote:
>>
>> I'm guessing that the real issue is that 32-bit needs %fs restored early for
>> TLS.
>
> I *think* you are right.
>
> Anyway, that should be easy enough to verify.
From: Randy Dunlap
Update x86-opcode-map.txt based on the October 2017 Intel SDM publication.
Correct INVPID to INVVPID.
Add UD0 and UD1 instruction opcodes.
Signed-off-by: Randy Dunlap
Cc: Masami Hiramatsu
Cc: Masami Hiramatsu
Cc: Josh Poimboeuf
Cc: x86 maintainers
---
v2 changes:
. corre
On Mon, Dec 11, 2017 at 9:49 AM, Dave Hansen wrote:
> So, before this,
>
> On 12/10/2017 10:47 PM, Andy Lutomirski wrote:
> ...> + if (unlikely(ldt)) {
>> + if (static_cpu_has_bug(X86_BUG_CPU_SECURE_MODE_PTI)) {
>> + if (WARN_ON_ONCE((unsigned long)ldt->slot > 1))
On 12/08/2017 10:33 PM, Tobin C. Harding wrote:
[Adding Laura]
On Fri, Dec 08, 2017 at 06:18:45PM -0800, Joe Perches wrote:
On Sat, 2017-12-09 at 12:27 +1100, Tobin C. Harding wrote:
On Fri, Dec 08, 2017 at 01:22:37PM -0800, Joe Perches wrote:
Outside of the documentation, what could be use
Quoting Chris Wilson (2017-12-11 12:51:42)
> Quoting Arnd Bergmann (2017-12-11 12:46:22)
> > The varargs macro trick in _PIPE3/_PHY3/_PORT3 was meant as an optimization
> > to shrink the i915 kernel module by around 1000 bytes. However, the
> > downside is a size regression with CONFIG_KASAN, as I
On Mon, Dec 11, 2017 at 10:31 AM, Linus Torvalds
wrote:
> On Mon, Dec 11, 2017 at 6:22 AM, Rafael J. Wysocki wrote:
>> On Sunday, December 10, 2017 10:58:23 PM CET Andy Lutomirski wrote:
>>>
>>> I'm guessing that the real issue is that 32-bit needs %fs restored early
>>> for TLS.
>>
>> I *think*
From: Jiri Pirko
Date: Mon, 11 Dec 2017 19:02:19 +0100
> The discussion we had before was about flag bitfield that was there
> *always*. In this case, that is not true. It is either ifindex or
> ifname. Even rtnetlink has ifname as attribute.
>
> The flags and info_mask is just big mystery. If i
Am Montag, 11. Dezember 2017, 11:19:54 CET schrieb Daniel Borkmann:
> Hi Randy, hi Richard, [ +Hendrik for c895f6f703ad7dd2f ]
>
> On 12/11/2017 09:32 AM, Richard Weinberger wrote:
> > Randy,
> >
> > Am Montag, 11. Dezember 2017, 03:42:12 CET schrieb Randy Dunlap:
> >> On 12/10/2017 06:08 PM, Lin
On Mon, Dec 04, 2017 at 01:53:51PM +0100, Łukasz Stelmach wrote:
> Add nodes for the True Random Number Generator found in Samsung Exynos
> 5250+ SoCs.
>
> Signed-off-by: Łukasz Stelmach
> ---
> arch/arm/boot/dts/exynos5.dtsi| 5 +
> arch/arm/boot/dts/exynos5250.dtsi | 5 +
> arch/ar
Currently VDE clock rate is determined by clock config left from
bootloader, let's not rely on it and explicitly specify the clock
rate in the CCF driver.
Signed-off-by: Dmitry Osipenko
---
drivers/clk/tegra/clk-tegra114.c | 1 +
drivers/clk/tegra/clk-tegra124.c | 2 +-
drivers/clk/tegra/clk-teg
Machine dies if HCLK, SCLK or EMC is disabled, hence mark these clocks
as critical. Currently some of drivers do not manage clocks properly,
expecting those clocks to be 'always enabled', these clocks are MC and
PLL_P outputs. Let's mark MC or PLL_P outputs as critical for now and
revert this chang
801 - 872 of 872 matches
Mail list logo
