Hello Kevin.
but there is no path which would force the project to do so.
This is incorrect.
If the contributions were legitimately provided under an OSI-approved
(or similar) license, the license cannot be terminated for convenience.
This is also incorrect. Free non-exclusive licenses can be
Move PCIe config space capability search API to common DesignWare file
as this can be used by both host and ep mode codes.
Signed-off-by: Vidya Sagar
Acked-by: Gustavo Pimentel
---
Changes since [v5]:
* None
Changes since [v4]:
* Removed redundant APIs in pcie-designware-ep.c file after moving
Add PCIe host controller driver for DesignWare core based
PCIe controller IP present in Tegra194.
Signed-off-by: Vidya Sagar
---
Changes since [v5]:
* None
Changes since [v4]:
* None
Changes since [v3]:
* None
Changes since [v2]:
* None
Changes since [v1]:
* Changed CONFIG_PCIE_TEGRA194 from
Add P2U (PIPE to UPHY) and PCIe controller nodes to device tree.
The Tegra194 SoC contains six PCIe controllers and twenty P2U instances
grouped into two different PHY bricks namely High-Speed IO (HSIO-12 P2Us)
and NVIDIA High Speed (NVHS-8 P2Us) respectively.
Signed-off-by: Vidya Sagar
---
Export pcie_pme_disable_msi() & pcie_pme_no_msi() APIs to enable drivers
using these APIs be able to build as loadable modules.
Signed-off-by: Vidya Sagar
---
Changes since [v5]:
* Corrected inline implementation of pcie_pme_no_msi() API
Changes since [v4]:
* None
Changes since [v3]:
* None
Tegra194 has six PCIe controllers based on Synopsys DesignWare core.
There are two Universal PHY (UPHY) blocks with each supporting 12(HSIO:
Hisg Speed IO) and 8(NVHS: NVIDIA High Speed) lanes respectively.
Controllers:0~4 use UPHY lanes from HSIO brick whereas Controller:5 uses
UPHY lanes from
Add support for Synopsys DesignWare core IP based PCIe host controller
present in Tegra194 SoC.
Signed-off-by: Vidya Sagar
---
Changes since [v5]:
* Addressed review comments from Thierry
Changes since [v4]:
* None
Changes since [v3]:
* None
Changes since [v2]:
* Changed 'nvidia,init-speed'
Synopsys DesignWare core based PCIe controllers in Tegra 194 SoC interface
with Universal PHY (UPHY) module through a PIPE2UPHY (P2U) module.
For each PCIe lane of a controller, there is a P2U unit instantiated at
hardware level. This driver provides support for the programming required
for each
Add support to enable CDM (Configuration Dependent Module) register check
for any data corruption based on the device-tree flag 'enable-cdm-check'.
Signed-off-by: Vidya Sagar
Acked-by: Gustavo Pimentel
---
Changes since [v5]:
* None
Changes since [v4]:
* None
Changes since [v3]:
* None
Add support for Tegra194 PCIe controllers. These controllers are based
on Synopsys DesignWare core IP.
Signed-off-by: Vidya Sagar
---
Changes since [v5]:
* Removed 'max-link-speed' as it is going to be a common sub-system property
* Removed 'nvidia,init-link-speed' as there isn't much value
Add support for Tegra194 P2U (PIPE to UPHY) module block which is a glue
module instantiated one for each PCIe lane between Synopsys DesignWare core
based PCIe IP and Universal PHY block.
Signed-off-by: Vidya Sagar
---
Changes since [v5]:
* Added Sob
* Changed node name from "p2u@" to
Add extended configuration space capability search API using struct dw_pcie *
pointer
Signed-off-by: Vidya Sagar
Acked-by: Gustavo Pimentel
---
Changes since [v5]:
* None
Changes since [v4]:
* None
Changes since [v3]:
* None
Changes since [v2]:
* None
Changes since [v1]:
* This is a new
Remove multiple write enable and disable sequences of dbi registers as
Tegra194 implements writes to BAR-0 register (offset: 0x10) controlled by
DBI write-lock enable bit thereby not allowing any further writes to BAR-0
register in config space to take place. Hence enabling write permission at
the
Enable PCIe controller nodes to enable respective PCIe slots on
P2972- board. Following is the ownership of slots by different
PCIe controllers.
Controller-0 : M.2 Key-M slot
Controller-1 : On-board Marvell eSATA controller
Controller-3 : M.2 Key-E slot
Signed-off-by: Vidya Sagar
---
Changes
Some host controllers need to know the existence of clkreq signal routing to
downstream devices to be able to advertise low power features like ASPM L1
substates. Without clkreq signal routing being present, enabling ASPM L1 sub
states might lead to downstream devices falling off the bus. Hence a
Add support to enable CDM (Configuration Dependent Module) registers check
for any data corruption. CDM registers include standard PCIe configuration
space registers, Port Logic registers and iATU and DMA registers.
Refer Section S.4 of Synopsys DesignWare Cores PCI Express Controller Databook
Add #defines only for the Data Link Feature and Physical Layer 16.0 GT/s
features.
Signed-off-by: Vidya Sagar
Reviewed-by: Thierry Reding
---
Changes since [v5]:
* None
Changes since [v4]:
* None
Changes since [v3]:
* None
Changes since [v2]:
* Updated commit message and description to
On 09-05-19, 21:34, Bjorn Andersson wrote:
> The APPS IOMMU provides contexts for FastRPC, MDP and WLAN, among other
> things. Define these. We use the qcom_iommu binding because the
^^^
Double spaces crept in..
> firmware restrictions in incompatible with the arm-smmu.
>
>
> > Guest reads the persistent memory range information from
> > Qemu over VIRTIO and registers it on nvdimm_bus. It also
> > creates a nd_region object with the persistent memory
> > range information so that existing 'nvdimm/pmem' driver
> > can reserve this into system memory map. This way
>
On Thu, May 09, 2019 at 04:35:55PM +0900, Masahiro Yamada wrote:
> If the compiler specified by $(CC) is not present, the Kconfig stage
> sprinkles 'not found' messages, then succeeds.
>
> $ make CROSS_COMPILE=foo defconfig
> /bin/sh: 1: foogcc: not found
> /bin/sh: 1: foogcc: not found
>
Hi all,
Please do not add any v5.3 material to your linux-next included
trees/branches until after v5.2-rc1 has been released.
Changes since 20190510:
The mips tree gained a conflict against Linus' tree.
The thermal-soc tree gained a conflict against Linus' tree and a build
failure for which I
As per ARM IHI 0069D, GICD_CTLR's RWP field tracks updates to:
GICD_CTLR's Group Enable bits, for transitions from 1 to 0 only
GICD_CTLR's ARE bits, E1NWF bit and DS bit (if we have)
GICD_ICENABLER
We seemed use this field in an inappropriate way, somewhere in the
GIC-v3
On Mon, 13 May 2019 at 02:50, Masahiro Yamada
wrote:
> > $ CROSS_COMPILE=foo make
> > make: foogcc: Command not found
> > scripts/kconfig/conf --syncconfig Kconfig
> > scripts/Kconfig.include:34: compiler 'foogcc' not found
> > make[2]: *** [scripts/kconfig/Makefile:69: syncconfig] Error 1
> >
Both rev C and rev B of the board come with two QSPI-NOR chips
attached to the SoC. Add DT code describing all of this.
Signed-off-by: Andrey Smirnov
Cc: Shawn Guo
Cc: Chris Healy
Cc: Andrew Lunn
Cc: Fabio Estevam
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
---
UART2 is connected to PTD22/23, not PTD0/1. Fix corresponding pinmux
node.
Signed-off-by: Andrey Smirnov
Cc: Shawn Guo
Cc: Chris Healy
Cc: Andrew Lunn
Cc: Fabio Estevam
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
---
arch/arm/boot/dts/vf610-zii-dev.dtsi | 4
Hello Stephen,
On 5/10/2019 11:24 PM, Stephen Boyd wrote:
Quoting Taniya Das (2019-05-09 19:58:39)
Hello Stephen,
Thanks for the review.
On 5/9/2019 10:57 PM, Stephen Boyd wrote:
Quoting Taniya Das (2019-05-08 11:24:55)
Update the init data name for each of the dynamic frequency switch
If a call to kobject_init_and_add() fails we should call kobject_put()
otherwise we leak memory.
Add call to kobject_put() in the error path of call to
kobject_init_and_add(). Please note, this has the side effect that
the release method is called if kobject_init_and_add() fails.
Signed-off-by:
Add an entry for Micron MT25QL02 which is a 3V variant of already
supported MT25QU02.
Testing was done on a ZII VF610 Dev Board (rev. B).
Signed-off-by: Cory Tusar
Signed-off-by: Andrey Smirnov
Cc: Chris Healy
Cc: Marek Vasut
Cc: Tudor Ambarus
Cc: linux-...@lists.infradead.org
Cc:
On Sun, May 12, 2019 at 11:59 PM Anson Huang wrote:
> + soc_dev = soc_device_register(soc_dev_attr);
> + if (IS_ERR(soc_dev)) {
> + kfree(soc_dev_attr->revision);
> + return -ENODEV;
This should return PTR_ERR(soc_dev) instead.
Add i.MX SCU SoC info driver to support i.MX8QXP SoC, introduce
driver dependency into Kconfig as CONFIG_IMX_SCU must be
selected to support i.MX SCU SoC driver, also need to use
platform driver model to make sure IMX_SCU driver is probed
before i.MX SCU SoC driver.
With this patch, SoC info can
This patch selects CONFIG_IMX_SCU_SOC by default to support
i.MX system controller unit SoC info driver.
Signed-off-by: Anson Huang
---
This patch is a resend version of patch
https://patchwork.kernel.org/patch/10895149/, the change is
just using correct encoding.
---
On Mon, May 13, 2019 at 11:35 AM Joel Stanley wrote:
>
> On Mon, 13 May 2019 at 02:28, Masahiro Yamada
> wrote:
> >
> > On Thu, May 9, 2019 at 4:36 PM Masahiro Yamada
> > wrote:
> > >
> > > If the compiler specified by $(CC) is not present, the Kconfig stage
> > > sprinkles 'not found'
On Mon, 13 May 2019 at 02:28, Masahiro Yamada
wrote:
>
> On Thu, May 9, 2019 at 4:36 PM Masahiro Yamada
> wrote:
> >
> > If the compiler specified by $(CC) is not present, the Kconfig stage
> > sprinkles 'not found' messages, then succeeds.
> >
> > $ make CROSS_COMPILE=foo defconfig
> >
On Sat, May 11, 2019 at 1:56 AM Masahiro Yamada
wrote:
>
> With menuconfig / nconfig, users can input any file path from the
> "Save" menu, but it fails if the parent directory does not exist.
>
> Why not create the parent directory automatically. I think this is
> a user-friendly behavior.
>
> I
On Fri, May 10, 2019 at 02:47:49PM -0400, Steven Rostedt wrote:
>
> As nobody else commented, I will ;)
>
> Hi Zhenzhong!
>
> On Sun, 14 Apr 2019 11:11:04 +0800
> Zhenzhong Duan wrote:
>
> > As stated in "Documentation/lockup-watchdogs.txt:line 22", the default
> > behaivor after 'hardlockup'
On Sat, May 11, 2019 at 1:56 AM Masahiro Yamada
wrote:
>
> conf_write_dep() has just one caller:
>
> conf_write_dep("include/config/auto.conf.cmd");
>
> "name" always points to a valid string.
>
> Signed-off-by: Masahiro Yamada
> ---
Applied to linux-kbuild.
> scripts/kconfig/confdata.c
From: swkhack
In 64-bit machine,the value of "vma->vm_end - vma->vm_start"
maybe negative in 32bit int and the "count >> PAGE_SHIFT"'s result
will be wrong.So change the local variable and return
value to unsigned long will fix the problem.
Signed-off-by: swkhack
---
mm/mlock.c | 4 ++--
1
On Thu, May 9, 2019 at 4:36 PM Masahiro Yamada
wrote:
>
> If the compiler specified by $(CC) is not present, the Kconfig stage
> sprinkles 'not found' messages, then succeeds.
>
> $ make CROSS_COMPILE=foo defconfig
> /bin/sh: 1: foogcc: not found
> /bin/sh: 1: foogcc: not found
> ***
On Thu, May 9, 2019 at 9:58 AM Masahiro Yamada
wrote:
>
> This warning was disabled by commit bd664f6b3e37 ("disable new
> gcc-7.1.1 warnings for now") just because it was too noisy.
>
> Thanks to Arnd Bergmann, all warnings have been fixed. Now, we are
> ready to re-enable it.
>
> Signed-off-by:
On Thu, May 9, 2019 at 10:01 AM Masahiro Yamada
wrote:
>
> Do not descend to sub-directories when unneeded.
>
> I used subdir-$(CONFIG_...) for hidraw, seccomp, and vfs because
> they only contain host programs.
>
> While we are here, let's add SPDX License tag, and sort the directories
>
On Thu, May 9, 2019 at 11:46 AM Masahiro Yamada
wrote:
>
> There are still some trailing whitespaces under scripts/kconfig/tests/,
> but they must be kept. Otherwise, "make testconfig" would break.
>
> Signed-off-by: Masahiro Yamada
> ---
Applied to linux-kbuild.
> scripts/kconfig/gconf.c
On Fri, May 10, 2019 at 1:52 AM Nick Desaulniers
wrote:
>
> > On Wed, May 8, 2019 at 11:46 PM Masahiro Yamada
> > wrote:
> > > This flag is documented in the GCC 4.6 manual, and recognized by
> > > Clang as well. Let's rip off the cc-option switch.
>
> Checked w/ godbolt w/ Clang 4 and GCC
On Fri, May 10, 2019 at 1:47 AM Nick Desaulniers
wrote:
>
> From: Masahiro Yamada
> > On Thu, May 9, 2019 at 4:11 PM Sedat Dilek wrote:
> > > BTW, is this a speedup when doing CC/LD FLAGS etc checks unconditionally?
> >
> > Yes.
> > cc-option is somewhat costly because it invoked the compiler
On Thu, May 9, 2019 at 8:49 PM Nathan Chancellor
wrote:
>
> This is no longer a valid option in clang, it was removed in 3.5, which
> we don't support.
>
> https://github.com/llvm/llvm-project/commit/cb3f812b6b9fab8f3b41414f24e90222170417b4
>
> Signed-off-by: Nathan Chancellor
> ---
>
> Let me
On Tue, Apr 30, 2019 at 07:15:55PM +0200, Guido Günther wrote:
> Add a node for the irqsteer interrupt controller found on the iMX8MQ
> SoC.
>
> Signed-off-by: Guido Günther
> Reviewed-by: Lucas Stach
Applied, thanks.
On Fri, May 10, 2019 at 11:11 PM Masahiro Yamada
wrote:
>
> We do not support old Clang versions. Upgrade your clang version
> if any of these flags is unsupported.
>
> Let's add all flags within ifdef CONFIG_CC_IS_CLANG unconditionally.
>
> Signed-off-by: Masahiro Yamada
> Reviewed-by: Sedat
As of Linux 5.1, alpha and s390 are the last architectures that
have defconfig in arch/*/ instead of arch/*/configs/.
$ find arch -name defconfig | sort
arch/alpha/defconfig
arch/arm64/configs/defconfig
arch/csky/configs/defconfig
arch/nds32/configs/defconfig
On Sun, 12 May 2019 21:20:12 -0400, "Alex Xu (Hello71)" said:
> I bisected this to 76f969e, "cgroup: cgroup v2 freezer". I reverted the
> entire patchset (reverting only that one caused a conflict), which
> resolved the issue. I skimmed the patch and came up with this
> workaround, which also
Sorry, this patch still has issue when the queue is almost full, for the sample
window becomes very small.
How about we calculating the delta of each time read and then accumulating it
to compare with the to_idr? This can guarantee to get real rd_idx with more
than 1 wraps.
Thanks,
Heyi
Hi,
I was trying to use strace recently and found that it exhibited some
strange behavior. I produced this minimal test case:
#include
int main() {
write(1, "a", 1);
return 0;
}
which, when run using "gcc test.c && strace ./a.out" produces this
strace output:
[ pre-main omitted ]
Hi all,
After merging the thermal-soc tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
ld: drivers/infiniband/hw/cxgb4/cm.o: in function
`.devm_thermal_of_cooling_device_register':
(.text+0x23f0): multiple definition of
`.devm_thermal_of_cooling_device_register';
Dear Sir / Madam,
Please forgive me if my request is not acceptable by your kind person.
I am Dr. Nor Salah Ibrahim, Working at MAYBANK (Malaysia) as the
Independent Non-Executive Director & Audit Committee. During our last
banking Audits we discovered an abandoned account belongs to one of
our
It is safe to do SIMD in an interrupt on PowerPC.
Only disable when there is no SIMD available
(and this is a static branch).
Tested and works with the WireGuard (Zinc) patch I wrote that needs this.
Also improves performance of the crypto subsystem that checks this.
Re-sending because this
Hi all,
Today's linux-next merge of the thermal-soc tree got a conflict in:
MAINTAINERS
between commit:
f23afd75fc99 ("RDMA/efa: Add driver to Kconfig/Makefile")
from Linus' tree and commit:
7e34eb7dd067 ("thermal: Introduce Amazon's Annapurna Labs Thermal Driver")
from the
Dear Stephen,
Sorry for the late reply.
On Tue, 2019-05-07 at 13:49 -0700, Stephen Boyd wrote:
> Quoting Roger Lu (2019-05-07 00:50:57)
> > Dear Stephen,
> >
> > Sorry for the late reply.
> >
> > On Fri, 2019-05-03 at 14:08 -0700, Stephen Boyd wrote:
> > > Quoting Roger Lu (2019-05-01
On May 12, 2019 8:31:05 AM PDT, Dominik Brodowski
wrote:
>On Sun, May 12, 2019 at 03:18:16AM -0700, h...@zytor.com wrote:
>> > Couldn't this parsing of the .xattr-list file and the setting of
>the xattrs
>> > be done equivalently by the initramfs' /init? Why is kernel
>involvement
>> > actually
On May 12, 2019 5:02:30 PM PDT, Mimi Zohar wrote:
>On Sun, 2019-05-12 at 17:31 +0200, Dominik Brodowski wrote:
>> On Sun, May 12, 2019 at 08:52:47AM -0400, Mimi Zohar wrote:
>
>
>> > It's too late. The /init itself should be signed and verified.
>>
>> Could you elaborate a bit more about the
On Sun, 2019-05-12 at 17:31 +0200, Dominik Brodowski wrote:
> On Sun, May 12, 2019 at 08:52:47AM -0400, Mimi Zohar wrote:
> > It's too late. The /init itself should be signed and verified.
>
> Could you elaborate a bit more about the threat model, and why deferring
> this to the initramfs is
Hi all,
Today's linux-next merge of the mips tree got a conflict in:
arch/mips/sgi-ip27/ip27-irq.c
between commit:
e4952b0c2c03 ("MIPS: SGI-IP27: Fix use of unchecked pointer in
shutdown_bridge_irq")
from Linus' tree and commit:
e6308b6d35ea ("MIPS: SGI-IP27: abstract chipset irq from
Resolve trailing whitespace error from checkpatch.pl
ERROR: trailing whitespace
Signed-off-by: Vandana BN
---
drivers/staging/kpc2000/kpc_dma/dma.c | 86 ++---
drivers/staging/kpc2000/kpc_dma/fileops.c | 114 +-
.../staging/kpc2000/kpc_dma/kpc_dma_driver.c
This patch resolves below errors reported by checkpatch
ERROR: "(foo*)" should be "(foo *)"
ERROR: "foo * bar" should be "foo *bar"
ERROR: "foo __init bar" should be "foo __init bar"
ERROR: "foo __exit bar" should be "foo __exit bar"
Signed-off-by: Vandana BN
---
This Patch resolves unnecessary cast warning and const file_operations
WARNING: unnecessary cast may hide bugs
WARNING: struct file_operations should normally be const
Signed-off-by: Vandana BN
---
drivers/staging/kpc2000/kpc_dma/fileops.c| 4 ++--
This patch resloves below warnings reported by checkpath in kpc_dma
WARNING: Missing a blank line after declarations
WARNING: labels should not be indented
CHECK: Please don't use multiple blank lines
CHECK: Please use a blank line after function/struct/union/enum
declarations
Signed-off-by:
This patch fixes below errors reported by checkpath
ERROR: Macros with complex values should be enclosed in parentheses
CHECK: Prefer using the BIT macro
ERROR: trailing statements should be on next line
ERROR: trailing statements should be on next line
Signed-off-by: Vandana BN
---
This patch resolves below errors reported by checkpath
ERROR: space required before the open brace '{'
ERROR: space prohibited after that '!' (ctx:BxW)
ERROR: space prohibited after that open parenthesis '('
Signed-off-by: Vandana BN
---
drivers/staging/kpc2000/kpc_dma/dma.c | 28
This patch resolves warnings to use __func__ insted of funtion name.
WARNING: Prefer using '"%s...", __func__' to using 'setup_dma_engine', this
function's name, in a string
Signed-off-by: Vandana BN
---
drivers/staging/kpc2000/kpc_dma/dma.c | 6 ++---
This patch fixes code indentaion error reported by checkpath
ERROR: switch and case should be at the same indent
ERROR: trailing statements should be on next line
Signed-off-by: Vandana BN
---
drivers/staging/kpc2000/kpc_dma/fileops.c | 12
1 file changed, 8 insertions(+), 4
Hi all,
On Wed, 1 May 2019 13:40:54 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the input tree got a conflict in:
>
> Documentation/devicetree/bindings/vendor-prefixes.txt
>
> between commit:
>
> 2c98d9e47533 ("dt-bindings: vendor-prefixes: add AZW")
>
> from the
On Sun, May 12, 2019 at 04:26:13AM -0400, Yangtao Li wrote:
> This patch adds the support for allwinner thermal sensor, within
> allwinner SoC. It will register sensors for thermal framework
> and use device tree to bind cooling device.
>
> Based on driver code found here:
>
The pull request you sent on Sun, 12 May 2019 23:41:49 +0200 (CEST):
> git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git
> tags/for-linus-5.2-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/983dfa4b6ee556563f7963348e4e2f97fc8a15b8
Thank you!
--
The pull request you sent on Sun, 12 May 2019 23:42:26 +0200 (CEST):
> git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git
> tags/upstream-5.2-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d7a02fa0a8f9ec1b81d57628ca9834563208ef33
Thank you!
--
The pull request you sent on Sun, 12 May 2019 23:42:07 +0200 (CEST):
> git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git tags/mtd/for-5.2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4dbf09fea60d158e60a30c419e0cfa1ea138dd57
Thank you!
--
Deet-doot-dot,
Hello Yangtao,
On Sun, May 12, 2019 at 04:26:13AM -0400, Yangtao Li wrote:
> diff --git a/drivers/thermal/sun50i_thermal.c
> b/drivers/thermal/sun50i_thermal.c
> new file mode 100644
> index ..3bdb3677b3d4
> --- /dev/null
> +++ b/drivers/thermal/sun50i_thermal.c
> @@ -0,0 +1,357 @@
>
Linus,
The following changes since commit 37624b58542fb9f2d9a70e6ea006ef8a5f66c30b:
Linux 5.1-rc7 (2019-04-28 17:04:13 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git
tags/upstream-5.2-rc1
for you to fetch changes up to
Linus,
The following changes since commit 37624b58542fb9f2d9a70e6ea006ef8a5f66c30b:
Linux 5.1-rc7 (2019-04-28 17:04:13 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git
tags/for-linus-5.2-rc1
for you to fetch changes up to
Linus,
The following changes since commit 37624b58542fb9f2d9a70e6ea006ef8a5f66c30b:
Linux 5.1-rc7 (2019-04-28 17:04:13 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git tags/mtd/for-5.2
for you to fetch changes up to
Hello Maxime,
On Sun, May 12, 2019 at 03:39:30PM +0200, Maxime Ripard wrote:
> Hi,
>
> Thanks a lot for working on this!
>
> On Sun, May 12, 2019 at 04:26:13AM -0400, Yangtao Li wrote:
> > This patch adds the support for allwinner thermal sensor, within
> > allwinner SoC. It will register
The c3600 doesn't have any PCI-X slots (only PCI) as far as I can tell from
user manuals.
The SY-PCX40009 PCI-X card that I have says it supports two models: 32-bit at
66 MHz and 64-bit
at 133 MHz. The 32-bit slots in c3600 are 33 MHz. Whether the card will work
at 33 MHz is not
clear. The
> The c3600 doesn't have any PCI-X slots (only PCI) as far as I can tell from
> user manuals.
PCI-32/33 device I/O bus
PCI-64/33 high-performance device I/O bus <- this is
PCI-X, 64bit 5V
PCI-64/66 high-performance graphics I/O bus <- this is
PCI-X, 64bit 3.3V
Increasing the SATA/AHCI DMA TX/RX FIFOs (P0DMACR.TXTS and .RXTS, ie.
TX_TRANSACTION_SIZE and RX_TRANSACTION_SIZE) from default 0x0 each
to 0x3 each, gives a write performance boost of 120 MiB/s to 132 MiB/s
from lame 36 MiB/s to 45 MiB/s previously.
Read performance is about 200 MiB/s.
[tested on
Hi,
On 07.05.2019 at 07:01, Peter Hutterer wrote:
On Fri, May 03, 2019 at 01:59:23PM +0200, Benjamin Tissoires wrote:
Hi,
On Fri, May 3, 2019 at 11:43 AM Igor Kushnir wrote:
Hi Benjamin,
On 5/3/19 10:36 AM, Benjamin Tissoires wrote:
Hi,
On Thu, May 2, 2019 at 11:37 PM Błażej Szczygieł
MPLL_5OM (the capital letter o) should indeed be MPLL_50M (the number)
Fix this before it gets used.
Reported-by: Martin Blumenstingl
Fixes: 25db146aa726 ("dt-bindings: clk: meson: add g12a periph clock controller
bindings")
Signed-off-by: Jerome Brunet
---
drivers/clk/meson/g12a.c
kernel's config and dmesg are here
http://www.downthebunker.com/chunk_of/stuff/public/projects/workstations/hppa/c3600/kernel/5.1-git-v5.2-64bit/
http://www.downthebunker.com/chunk_of/stuff/public/projects/workstations/hppa/c3600/kernel/4.16.2-64bit/
Il giorno dom 12 mag 2019 alle ore 22:44
guys,
I asked a friend to lend us his card, which is the card2 listed below
and not things are becoming really weird
card1, Silicon Image, Inc. Adaptec AAR-1210SA
card2, Silicon Image, Inc. SiI 3124 PCI-X Serial ATA
the card1 is a PCI32 bit card, and uses the "sata_sil" driver
the card2 is a
Since recent high resolution scrolling changes the A4Tech driver must
check for the "REL_WHEEL_HI_RES" usage code.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=203369
Fixes: 2dc702c991e3774af9d7ce410eef410ca9e2357e ("HID: input: use the
Resolution Multiplier for high-resolution scrolling")
Parameters passed to check helpers are now obtained by dereferencing
unverified pointer arguments. Check validity of those pointers first.
Signed-off-by: Janusz Krzysztofik
---
drivers/media/v4l2-core/v4l2-subdev.c | 27 +++
1 file changed, 27 insertions(+)
diff --git
Invalid arguments passed to v4l2_subdev_call generally mean bugs. Be
noisy if that happens.
Signed-off-by: Janusz Krzysztofik
---
drivers/media/v4l2-core/v4l2-subdev.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/media/v4l2-core/v4l2-subdev.c
Extend parameter checks performed by v4l2_subdev_call() with a check for
a non-NULL pad config pointer if V4L2_SUBDEV_FORMAT_TRY format type is
requested so drivers don't need to care.
Signed-off-by: Janusz Krzysztofik
---
drivers/media/v4l2-core/v4l2-subdev.c | 27 +--
Correctness of format type (try or active) and pad ID parameters passed
to subdevice operation callbacks is now verified only for IOCTL calls.
However, those callbacks are also used by drivers, e.g., V4L2 host
interfaces.
Since both subdev_do_ioctl() and drivers are using v4l2_subdev_call()
macro
Correctness of format type (try or active) and pad ID parameters passed
to subdevice operation callbacks is now verified only for IOCTL calls.
However, those callbacks are also used by drivers, e.g., V4L2 host
interfaces.
Since both subdev_do_ioctl() and drivers are using v4l2_subdev_call()
Le dimanche 12 mai 2019 à 18:32 +0200, Paul Kocialkowski a écrit :
> Hi Nicolas,
>
> Le dimanche 12 mai 2019 à 10:17 -0400, Nicolas Dufresne a écrit :
> > Le dimanche 12 mai 2019 à 13:35 +0200, Paul Kocialkowski a écrit :
> > > Hi,
> > >
> > > With the work done on the media request API and the
walter harms wrote:
> Sorry, you misunderstood me, my fault, i did not see that size is unsigned.
> NTL i do not think size=0 is useful.
Allow me to quote from the getxattr manpage:
If size is specified as zero, these calls return the current size of
the named extended
The variable which holds the parent names for the VPU clocks has a typo
in it. Fix this typo to make the variable naming in the driver
consistent. No functional changes.
Fixes: 41785ce562491d ("clk: meson: meson8b: add the VPU clock trees")
Signed-off-by: Martin Blumenstingl
---
This is a simple typo fix for a clock which was introduced with the
v5.2 development cycle.
Nothing critical, so I'm fine if it's queued for v5.3 (no need to send
it as v5.2 fix).
Martin Blumenstingl (1):
clk: meson: meson8b: fix a typo in the VPU parent names array variable
On Sun, May 12, 2019 at 05:05:48PM +, Rob Landley wrote:
> On 5/12/19 7:52 AM, Mimi Zohar wrote:
> > On Sun, 2019-05-12 at 11:17 +0200, Dominik Brodowski wrote:
> >> On Thu, May 09, 2019 at 01:24:17PM +0200, Roberto Sassu wrote:
> >>> This proposal consists in marshaling pathnames and xattrs
Hi Greg,
This is the pull request containing fixes for 5.2-rc1/2.
It contains 2 fixes (1 of them for stable) and 1 change to a new IOCTL
that was introduced to kernel 5.2 in the previous pull requests.
See the tag comment for more details.
Thanks,
Oded
The following changes since commit
Amlogic's vendor kernel defines an OPP for the GPU on Meson8b boards
with a voltage of 1.15V. It turns out that the vendor kernel relies on
the bootloader to set up the voltage. The bootloader however sets a
fixed voltage of 1.10V.
Amlogic's patched u-boot sources (uboot-2015-01-15-23a3562521)
Currently I am working on the PWM driver to complete .get_state()
support. This allowed me to read the VDDEE voltage set by u-boot
on my Meson8b boards (EC-100 and Odroid-C1). VDDEE supplies the
Mali GPU.
It turns out that the bootloader configures a VDDEE voltage of 1.10V
instead of 1.15V. 1.15V
Hi,
I regret to inform you that I have now the third crippling issue in
Linux 5.1, with the fourth one in the process of being isolated.
This time, it's a PC Engines APU2 running in circles right after
booting:
May 12 20:56:01 prom kernel: CPU: 2 PID: 657 Comm: kworker/2:2 Tainted: G
W
On Sun, 2019-05-12 at 07:18 -0500, Alex Elder wrote:
> On 5/12/19 1:33 AM, Kalle Valo wrote:
> > Alex Elder writes:
> >
> > > Define FIELD_MAX(), which supplies the maximum value that can be
> > > represented by a field value. Define field_max() as well, to go
> > > along with the lower-case
1 - 100 of 251 matches
Mail list logo
