* Re: [PATCH] dt-bindings: arm: Convert RDA Micro board/soc bindings to json-schema
From: Rob Herring @ 2019-07-09 17:03 UTC (permalink / raw)
To: devicetree; +Cc: Andreas Färber, linux-arm-kernel, Manivannan Sadhasivam
In-Reply-To: <20190618212229.32302-4-robh@kernel.org>
On Tue, Jun 18, 2019 at 03:22:28PM -0600, Rob Herring wrote:
> Convert RDA Micro SoC bindings to DT schema format using json-schema.
>
> Cc: "Andreas Färber" <afaerber@suse.de>
> Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> Andreas, Update the license on this one too to dual licensed if you
> want.
Ping.
>
> Documentation/devicetree/bindings/arm/rda.txt | 17 ----------------
> .../devicetree/bindings/arm/rda.yaml | 20 +++++++++++++++++++
> MAINTAINERS | 2 +-
> 3 files changed, 21 insertions(+), 18 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/arm/rda.txt
> create mode 100644 Documentation/devicetree/bindings/arm/rda.yaml
^ permalink raw reply
* Re: [PATCH v1 01/22] docs: Documentation/*.txt: rename all ReST files to *.rst
From: Rob Herring @ 2019-07-09 17:02 UTC (permalink / raw)
To: Mauro Carvalho Chehab
Cc: linux-wireless, linux-fbdev, linux-ia64, kvm, linux-sh, linux-pci,
dri-devel, platform-driver-x86, linux-mm, kernel-hardening,
sparclinux, linux-arch, linux-s390, Jonathan Corbet, x86, iommu,
devicetree, linux-watchdog, Mauro Carvalho Chehab, linux-block,
linux-gpio, openipmi-developer, linux-arm-kernel, linaro-mm-sig,
linux-parisc, netdev, Linux Doc Mailing List, linux-kernel,
linux-securit
In-Reply-To: <6b6b6db8d6de9b66223dd6d4b43eb60ead4c71d7.1560891322.git.mchehab+samsung@kernel.org>
On Tue, Jun 18, 2019 at 06:05:25PM -0300, Mauro Carvalho Chehab wrote:
> Those files are actually at ReST format. Ok, currently, they
> don't belong to any place yet at the organized book series,
> but we don't want patches to break them as ReST files. So,
> rename them and add a :orphan: in order to shut up warning
> messages like those:
>
> ...
> Documentation/svga.rst: WARNING: document isn't included in any toctree
> Documentation/switchtec.rst: WARNING: document isn't included in any toctree
> ...
>
> Later patches will move them to a better place and remove the
> :orphan: markup.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> ---
>
> I had to remove the long list of maintainers got by
> getpatch.pl, as it was too long. I opted to keep only the
> mailing lists.
>
> Documentation/ABI/removed/sysfs-class-rfkill | 2 +-
> Documentation/ABI/stable/sysfs-class-rfkill | 2 +-
> Documentation/ABI/stable/sysfs-devices-node | 2 +-
> Documentation/ABI/testing/procfs-diskstats | 2 +-
> Documentation/ABI/testing/sysfs-block | 2 +-
> .../ABI/testing/sysfs-class-switchtec | 2 +-
> .../ABI/testing/sysfs-devices-system-cpu | 4 +-
> .../{DMA-API-HOWTO.txt => DMA-API-HOWTO.rst} | 2 +
> Documentation/{DMA-API.txt => DMA-API.rst} | 8 ++-
> .../{DMA-ISA-LPC.txt => DMA-ISA-LPC.rst} | 4 +-
> ...{DMA-attributes.txt => DMA-attributes.rst} | 2 +
> Documentation/{IPMI.txt => IPMI.rst} | 2 +
> .../{IRQ-affinity.txt => IRQ-affinity.rst} | 2 +
> .../{IRQ-domain.txt => IRQ-domain.rst} | 2 +
> Documentation/{IRQ.txt => IRQ.rst} | 2 +
> .../{Intel-IOMMU.txt => Intel-IOMMU.rst} | 2 +
> Documentation/PCI/pci.rst | 8 +--
> Documentation/{SAK.txt => SAK.rst} | 3 +-
> Documentation/{SM501.txt => SM501.rst} | 2 +
> Documentation/admin-guide/hw-vuln/l1tf.rst | 2 +-
> .../admin-guide/kernel-parameters.txt | 4 +-
> .../{atomic_bitops.txt => atomic_bitops.rst} | 3 +-
> Documentation/block/biodoc.txt | 2 +-
> .../{bt8xxgpio.txt => bt8xxgpio.rst} | 3 +-
> Documentation/{btmrvl.txt => btmrvl.rst} | 2 +
> ...-mapping.txt => bus-virt-phys-mapping.rst} | 54 +++++++++---------
> ...g-warn-once.txt => clearing-warn-once.rst} | 2 +
> Documentation/{cpu-load.txt => cpu-load.rst} | 2 +
> .../{cputopology.txt => cputopology.rst} | 2 +
> Documentation/{crc32.txt => crc32.rst} | 2 +
> Documentation/{dcdbas.txt => dcdbas.rst} | 2 +
> ...ging-modules.txt => debugging-modules.rst} | 2 +
> ...hci1394.txt => debugging-via-ohci1394.rst} | 2 +
> Documentation/{dell_rbu.txt => dell_rbu.rst} | 3 +-
> Documentation/device-mapper/statistics.rst | 4 +-
> .../devicetree/bindings/phy/phy-bindings.txt | 2 +-
Acked-by: Rob Herring <robh@kernel.org>
> Documentation/{digsig.txt => digsig.rst} | 2 +
> Documentation/driver-api/usb/dma.rst | 6 +-
> Documentation/driver-model/device.rst | 2 +-
> Documentation/{efi-stub.txt => efi-stub.rst} | 2 +
> Documentation/{eisa.txt => eisa.rst} | 2 +
> Documentation/fb/vesafb.rst | 2 +-
> Documentation/filesystems/sysfs.txt | 2 +-
> ...ex-requeue-pi.txt => futex-requeue-pi.rst} | 2 +
> .../{gcc-plugins.txt => gcc-plugins.rst} | 2 +
> Documentation/gpu/drm-mm.rst | 2 +-
> Documentation/{highuid.txt => highuid.rst} | 4 +-
> .../{hw_random.txt => hw_random.rst} | 2 +
> .../{hwspinlock.txt => hwspinlock.rst} | 2 +
> Documentation/ia64/irq-redir.rst | 2 +-
> .../{intel_txt.txt => intel_txt.rst} | 2 +
> .../{io-mapping.txt => io-mapping.rst} | 2 +
> .../{io_ordering.txt => io_ordering.rst} | 2 +
> Documentation/{iostats.txt => iostats.rst} | 2 +
> ...flags-tracing.txt => irqflags-tracing.rst} | 3 +-
> Documentation/{isa.txt => isa.rst} | 2 +
> Documentation/{isapnp.txt => isapnp.rst} | 2 +
> ...hreads.txt => kernel-per-CPU-kthreads.rst} | 4 +-
> Documentation/{kobject.txt => kobject.rst} | 6 +-
> Documentation/{kprobes.txt => kprobes.rst} | 3 +-
> Documentation/{kref.txt => kref.rst} | 2 +
> Documentation/laptops/thinkpad-acpi.rst | 6 +-
> Documentation/{ldm.txt => ldm.rst} | 5 +-
> Documentation/locking/rt-mutex.rst | 2 +-
> ...kup-watchdogs.txt => lockup-watchdogs.rst} | 2 +
> Documentation/{lsm.txt => lsm.rst} | 2 +
> Documentation/{lzo.txt => lzo.rst} | 2 +
> Documentation/{mailbox.txt => mailbox.rst} | 2 +
> Documentation/memory-barriers.txt | 6 +-
> ...hameleon-bus.txt => men-chameleon-bus.rst} | 2 +
> Documentation/networking/scaling.rst | 4 +-
> .../{nommu-mmap.txt => nommu-mmap.rst} | 2 +
> Documentation/{ntb.txt => ntb.rst} | 2 +
> Documentation/{numastat.txt => numastat.rst} | 3 +-
> Documentation/{padata.txt => padata.rst} | 2 +
> ...port-lowlevel.txt => parport-lowlevel.rst} | 2 +
> ...-semaphore.txt => percpu-rw-semaphore.rst} | 2 +
> Documentation/{phy.txt => phy.rst} | 2 +
> Documentation/{pi-futex.txt => pi-futex.rst} | 2 +
> Documentation/{pnp.txt => pnp.rst} | 13 +++--
> ...reempt-locking.txt => preempt-locking.rst} | 4 +-
> Documentation/{pwm.txt => pwm.rst} | 2 +
> Documentation/{rbtree.txt => rbtree.rst} | 54 +++++++++---------
> .../{remoteproc.txt => remoteproc.rst} | 4 +-
> Documentation/{rfkill.txt => rfkill.rst} | 2 +
> ...ust-futex-ABI.txt => robust-futex-ABI.rst} | 2 +
> ...{robust-futexes.txt => robust-futexes.rst} | 2 +
> Documentation/{rpmsg.txt => rpmsg.rst} | 2 +
> Documentation/{rtc.txt => rtc.rst} | 8 ++-
> Documentation/s390/vfio-ccw.rst | 6 +-
> Documentation/{sgi-ioc4.txt => sgi-ioc4.rst} | 2 +
> Documentation/{siphash.txt => siphash.rst} | 2 +
> .../{smsc_ece1099.txt => smsc_ece1099.rst} | 2 +
> .../{speculation.txt => speculation.rst} | 2 +
> .../{static-keys.txt => static-keys.rst} | 2 +
> Documentation/{svga.txt => svga.rst} | 2 +
> .../{switchtec.txt => switchtec.rst} | 4 +-
> .../{sync_file.txt => sync_file.rst} | 2 +
> Documentation/sysctl/kernel.txt | 4 +-
> Documentation/sysctl/vm.txt | 2 +-
> Documentation/{tee.txt => tee.rst} | 2 +
> .../{this_cpu_ops.txt => this_cpu_ops.rst} | 2 +
> Documentation/trace/kprobetrace.rst | 2 +-
> .../translations/ko_KR/memory-barriers.txt | 6 +-
> Documentation/translations/zh_CN/IRQ.txt | 4 +-
> .../translations/zh_CN/filesystems/sysfs.txt | 2 +-
> .../translations/zh_CN/io_ordering.txt | 4 +-
> ...access.txt => unaligned-memory-access.rst} | 2 +
> ...ed-device.txt => vfio-mediated-device.rst} | 4 +-
> Documentation/{vfio.txt => vfio.rst} | 2 +
> .../{video-output.txt => video-output.rst} | 3 +-
> Documentation/watchdog/hpwdt.rst | 2 +-
> Documentation/x86/topology.rst | 2 +-
> Documentation/{xillybus.txt => xillybus.rst} | 2 +
> Documentation/{xz.txt => xz.rst} | 2 +
> Documentation/{zorro.txt => zorro.rst} | 7 ++-
> MAINTAINERS | 56 +++++++++----------
> arch/Kconfig | 4 +-
> arch/arm/Kconfig | 2 +-
> arch/ia64/hp/common/sba_iommu.c | 12 ++--
> arch/ia64/sn/pci/pci_dma.c | 4 +-
> arch/parisc/Kconfig | 2 +-
> arch/parisc/kernel/pci-dma.c | 2 +-
> arch/sh/Kconfig | 2 +-
> arch/sparc/Kconfig | 2 +-
> arch/unicore32/include/asm/io.h | 2 +-
> arch/x86/Kconfig | 4 +-
> arch/x86/include/asm/dma-mapping.h | 4 +-
> arch/x86/kernel/amd_gart_64.c | 2 +-
> block/partitions/Kconfig | 2 +-
> drivers/base/core.c | 2 +-
> drivers/char/Kconfig | 4 +-
> drivers/char/hw_random/core.c | 2 +-
> drivers/char/ipmi/Kconfig | 2 +-
> drivers/char/ipmi/ipmi_si_hotmod.c | 2 +-
> drivers/char/ipmi/ipmi_si_intf.c | 2 +-
> drivers/dma-buf/Kconfig | 2 +-
> drivers/gpio/Kconfig | 2 +-
> drivers/parisc/sba_iommu.c | 16 +++---
> drivers/pci/switch/Kconfig | 2 +-
> drivers/platform/x86/Kconfig | 4 +-
> drivers/platform/x86/dcdbas.c | 2 +-
> drivers/platform/x86/dell_rbu.c | 2 +-
> drivers/pnp/isapnp/Kconfig | 2 +-
> drivers/vfio/Kconfig | 2 +-
> drivers/vfio/mdev/Kconfig | 2 +-
> include/asm-generic/bitops/atomic.h | 2 +-
> include/linux/dma-mapping.h | 2 +-
> include/linux/hw_random.h | 2 +-
> include/linux/io-mapping.h | 2 +-
> include/linux/jump_label.h | 2 +-
> include/linux/kobject.h | 2 +-
> include/linux/kobject_ns.h | 2 +-
> include/linux/rbtree.h | 2 +-
> include/linux/rbtree_augmented.h | 2 +-
> include/media/videobuf-dma-sg.h | 2 +-
> init/Kconfig | 2 +-
> kernel/dma/debug.c | 2 +-
> kernel/padata.c | 2 +-
> lib/Kconfig | 2 +-
> lib/Kconfig.debug | 2 +-
> lib/crc32.c | 2 +-
> lib/kobject.c | 4 +-
> lib/lzo/lzo1x_decompress_safe.c | 2 +-
> lib/xz/Kconfig | 2 +-
> mm/Kconfig | 2 +-
> mm/nommu.c | 2 +-
> samples/kprobes/kprobe_example.c | 2 +-
> samples/kprobes/kretprobe_example.c | 2 +-
> scripts/gcc-plugins/Kconfig | 2 +-
> security/Kconfig | 2 +-
> tools/include/linux/rbtree.h | 2 +-
> tools/include/linux/rbtree_augmented.h | 2 +-
> 173 files changed, 397 insertions(+), 242 deletions(-)
> rename Documentation/{DMA-API-HOWTO.txt => DMA-API-HOWTO.rst} (99%)
> rename Documentation/{DMA-API.txt => DMA-API.rst} (99%)
> rename Documentation/{DMA-ISA-LPC.txt => DMA-ISA-LPC.rst} (98%)
> rename Documentation/{DMA-attributes.txt => DMA-attributes.rst} (99%)
> rename Documentation/{IPMI.txt => IPMI.rst} (99%)
> rename Documentation/{IRQ-affinity.txt => IRQ-affinity.rst} (99%)
> rename Documentation/{IRQ-domain.txt => IRQ-domain.rst} (99%)
> rename Documentation/{IRQ.txt => IRQ.rst} (99%)
> rename Documentation/{Intel-IOMMU.txt => Intel-IOMMU.rst} (99%)
> rename Documentation/{SAK.txt => SAK.rst} (99%)
> rename Documentation/{SM501.txt => SM501.rst} (99%)
> rename Documentation/{atomic_bitops.txt => atomic_bitops.rst} (99%)
> rename Documentation/{bt8xxgpio.txt => bt8xxgpio.rst} (99%)
> rename Documentation/{btmrvl.txt => btmrvl.rst} (99%)
> rename Documentation/{bus-virt-phys-mapping.txt => bus-virt-phys-mapping.rst} (93%)
> rename Documentation/{clearing-warn-once.txt => clearing-warn-once.rst} (96%)
> rename Documentation/{cpu-load.txt => cpu-load.rst} (99%)
> rename Documentation/{cputopology.txt => cputopology.rst} (99%)
> rename Documentation/{crc32.txt => crc32.rst} (99%)
> rename Documentation/{dcdbas.txt => dcdbas.rst} (99%)
> rename Documentation/{debugging-modules.txt => debugging-modules.rst} (98%)
> rename Documentation/{debugging-via-ohci1394.txt => debugging-via-ohci1394.rst} (99%)
> rename Documentation/{dell_rbu.txt => dell_rbu.rst} (99%)
> rename Documentation/{digsig.txt => digsig.rst} (99%)
> rename Documentation/{efi-stub.txt => efi-stub.rst} (99%)
> rename Documentation/{eisa.txt => eisa.rst} (99%)
> rename Documentation/{futex-requeue-pi.txt => futex-requeue-pi.rst} (99%)
> rename Documentation/{gcc-plugins.txt => gcc-plugins.rst} (99%)
> rename Documentation/{highuid.txt => highuid.rst} (99%)
> rename Documentation/{hw_random.txt => hw_random.rst} (99%)
> rename Documentation/{hwspinlock.txt => hwspinlock.rst} (99%)
> rename Documentation/{intel_txt.txt => intel_txt.rst} (99%)
> rename Documentation/{io-mapping.txt => io-mapping.rst} (99%)
> rename Documentation/{io_ordering.txt => io_ordering.rst} (99%)
> rename Documentation/{iostats.txt => iostats.rst} (99%)
> rename Documentation/{irqflags-tracing.txt => irqflags-tracing.rst} (99%)
> rename Documentation/{isa.txt => isa.rst} (99%)
> rename Documentation/{isapnp.txt => isapnp.rst} (98%)
> rename Documentation/{kernel-per-CPU-kthreads.txt => kernel-per-CPU-kthreads.rst} (99%)
> rename Documentation/{kobject.txt => kobject.rst} (99%)
> rename Documentation/{kprobes.txt => kprobes.rst} (99%)
> rename Documentation/{kref.txt => kref.rst} (99%)
> rename Documentation/{ldm.txt => ldm.rst} (98%)
> rename Documentation/{lockup-watchdogs.txt => lockup-watchdogs.rst} (99%)
> rename Documentation/{lsm.txt => lsm.rst} (99%)
> rename Documentation/{lzo.txt => lzo.rst} (99%)
> rename Documentation/{mailbox.txt => mailbox.rst} (99%)
> rename Documentation/{men-chameleon-bus.txt => men-chameleon-bus.rst} (99%)
> rename Documentation/{nommu-mmap.txt => nommu-mmap.rst} (99%)
> rename Documentation/{ntb.txt => ntb.rst} (99%)
> rename Documentation/{numastat.txt => numastat.rst} (99%)
> rename Documentation/{padata.txt => padata.rst} (99%)
> rename Documentation/{parport-lowlevel.txt => parport-lowlevel.rst} (99%)
> rename Documentation/{percpu-rw-semaphore.txt => percpu-rw-semaphore.rst} (99%)
> rename Documentation/{phy.txt => phy.rst} (99%)
> rename Documentation/{pi-futex.txt => pi-futex.rst} (99%)
> rename Documentation/{pnp.txt => pnp.rst} (98%)
> rename Documentation/{preempt-locking.txt => preempt-locking.rst} (99%)
> rename Documentation/{pwm.txt => pwm.rst} (99%)
> rename Documentation/{rbtree.txt => rbtree.rst} (94%)
> rename Documentation/{remoteproc.txt => remoteproc.rst} (99%)
> rename Documentation/{rfkill.txt => rfkill.rst} (99%)
> rename Documentation/{robust-futex-ABI.txt => robust-futex-ABI.rst} (99%)
> rename Documentation/{robust-futexes.txt => robust-futexes.rst} (99%)
> rename Documentation/{rpmsg.txt => rpmsg.rst} (99%)
> rename Documentation/{rtc.txt => rtc.rst} (99%)
> rename Documentation/{sgi-ioc4.txt => sgi-ioc4.rst} (99%)
> rename Documentation/{siphash.txt => siphash.rst} (99%)
> rename Documentation/{smsc_ece1099.txt => smsc_ece1099.rst} (99%)
> rename Documentation/{speculation.txt => speculation.rst} (99%)
> rename Documentation/{static-keys.txt => static-keys.rst} (99%)
> rename Documentation/{svga.txt => svga.rst} (99%)
> rename Documentation/{switchtec.txt => switchtec.rst} (98%)
> rename Documentation/{sync_file.txt => sync_file.rst} (99%)
> rename Documentation/{tee.txt => tee.rst} (99%)
> rename Documentation/{this_cpu_ops.txt => this_cpu_ops.rst} (99%)
> rename Documentation/{unaligned-memory-access.txt => unaligned-memory-access.rst} (99%)
> rename Documentation/{vfio-mediated-device.txt => vfio-mediated-device.rst} (99%)
> rename Documentation/{vfio.txt => vfio.rst} (99%)
> rename Documentation/{video-output.txt => video-output.rst} (99%)
> rename Documentation/{xillybus.txt => xillybus.rst} (99%)
> rename Documentation/{xz.txt => xz.rst} (99%)
> rename Documentation/{zorro.txt => zorro.rst} (99%)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply
* Re: [PATCH 5/6] dt-bindings: display: ssd1307fb: Add initialization properties
From: Rob Herring @ 2019-07-09 16:58 UTC (permalink / raw)
Cc: Mark Rutland, devicetree, linux-fbdev, Michal Vokáč,
Bartlomiej Zolnierkiewicz, David Airlie, dri-devel, Marko Kohtala
In-Reply-To: <20190618074111.9309-6-marko.kohtala@okoko.fi>
On Tue, 18 Jun 2019 10:41:10 +0300, Marko Kohtala wrote:
> Document new bindings for adapting ssd1307fb driver to new displays.
>
> Signed-off-by: Marko Kohtala <marko.kohtala@okoko.fi>
> ---
> .../devicetree/bindings/display/ssd1307fb.txt | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply
* Re: [PATCH 1/4] dt-bindings: mfd: Add Actions Semi ATC260x PMIC binding
From: Rob Herring @ 2019-07-09 16:48 UTC (permalink / raw)
Cc: lee.jones, lgirdwood, broonie, robh+dt, afaerber, linux-actions,
linux-kernel, thomas.liau, devicetree, linus.walleij,
Manivannan Sadhasivam
In-Reply-To: <20190617155011.15376-2-manivannan.sadhasivam@linaro.org>
On Mon, 17 Jun 2019 21:20:08 +0530, Manivannan Sadhasivam wrote:
> Add devicetree binding for Actions Semi ATC260x PMICs.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
> .../devicetree/bindings/mfd/atc260x.txt | 162 ++++++++++++++++++
> 1 file changed, 162 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mfd/atc260x.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
^ permalink raw reply
* RE: [v4 4/6] dt-bindings: phy: Document the Synopsys MIPI DPHY Rx bindings
From: Luis de Oliveira @ 2019-07-09 16:28 UTC (permalink / raw)
To: Rob Herring, Luis Oliveira
Cc: mchehab@kernel.org, davem@davemloft.net,
gregkh@linuxfoundation.org, Jonathan.Cameron@huawei.com,
nicolas.ferre@microchip.com, paulmck@linux.ibm.com,
mark.rutland@arm.com, kishon@ti.com, devicetree@vger.kernel.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Joao.Pinto@synopsys.com
In-Reply-To: <20190709142000.GA995@bogus>
From: Rob Herring <robh@kernel.org>
Date: Tue, Jul 09, 2019 at 15:20:00
> On Tue, Jun 11, 2019 at 09:20:53PM +0200, Luis Oliveira wrote:
> > Add device-tree bindings documentation for SNPS DesignWare MIPI D-PHY in
> > RX mode.
> >
> > Signed-off-by: Luis Oliveira <luis.oliveira@synopsys.com>
> > ---
> > Changelog
> > v3-v4
> > - @Laurent I know I told you I could remove the snps,dphy-frequency on V3 but
> > it is really useful for me here. I removed all other the proprietary
> > properties except this one. Do you still think it must be removed?
> > - Frequency units @Rob
>
> Frequency units means append '-khz' to the property name. That also
> makes the 'frequency' part redundant, so maybe name it more around what
> the frequency is. The frequency for what?
>
> Rob
>
This is the D-PHY high speed frequency configuration that corresponds to
the high speed data transfer of the bus.
Basically is the transmission speed per lane.
Do you think I can use "link-frequencies" (present in
video-interfaces.txt) with one frequency?
> >
> > .../devicetree/bindings/phy/snps,dw-dphy-rx.txt | 29 ++++++++++++++++++++++
> > 1 file changed, 29 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/phy/snps,dw-dphy-rx.txt
> >
> > diff --git a/Documentation/devicetree/bindings/phy/snps,dw-dphy-rx.txt b/Documentation/devicetree/bindings/phy/snps,dw-dphy-rx.txt
> > new file mode 100644
> > index 0000000..50603e6
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/phy/snps,dw-dphy-rx.txt
> > @@ -0,0 +1,29 @@
> > +Synopsys DesignWare MIPI Rx D-PHY block details
> > +
> > +Description
> > +-----------
> > +
> > +The Synopsys MIPI D-PHY controller supports MIPI-DPHY in receiver mode.
> > +Please refer to phy-bindings.txt for more information.
> > +
> > +Required properties:
> > +- compatible : Shall be "snps,dw-dphy-rx".
> > +- #phy-cells : Must be 1.
> > +- bus-width : Size of the test interface data bus (8 bits->8 or
> > + 12bits->12).
> > +- snps,dphy-frequency : Frequency at which D-PHY should start, configurable.
> > + Check Synopsys databook. (-kHz)
> > +- reg : Test interface register. This correspondes to the
> > + physical base address of the controller and size of
> > + the device memory mapped registers; Check Synopsys
> > + databook.
> > +
> > +Example:
> > +
> > + mipi_dphy_rx1: dphy@d00003040 {
> > + compatible = "snps,dw-dphy-rx";
> > + #phy-cells = <1>;
> > + bus-width = <12>;
> > + snps,dphy-frequency = <300000>;
> > + reg = <0xd0003040 0x20>;
> > + };
> > --
> > 2.7.4
> >
Thank you Rob,
Luis
^ permalink raw reply
* Re: [PATCH 8/8] dt-bindings: timer: renesas, cmt: Update R-Car Gen3 CMT1 usage
From: Rob Herring @ 2019-07-09 16:26 UTC (permalink / raw)
To: Magnus Damm; +Cc: devicetree, mark.rutland, linux-renesas-soc, robh+dt
In-Reply-To: <156076224112.4736.5038116002723317642.sendpatchset@octo>
On Mon, 17 Jun 2019 18:04:01 +0900, Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
>
> The R-Car Gen3 SoCs so far come with a total for 4 on-chip CMT devices:
> - CMT0
> - CMT1
> - CMT2
> - CMT3
>
> CMT0 includes two rather basic 32-bit timer channels. The rest of the on-chip
> CMT devices support 48-bit counters and have 8 channels each.
>
> Based on the data sheet information "CMT2/3 are exactly same as CMT1"
> it seems that CMT2 and CMT3 now use the CMT1 compat string in the DTSI.
>
> Clarify this in the DT binding documentation by describing R-Car Gen3 and
> RZ/G2 CMT1 as "48-bit CMT devices".
>
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> ---
>
> Documentation/devicetree/bindings/timer/renesas,cmt.txt | 26 +++++++--------
> 1 file changed, 13 insertions(+), 13 deletions(-)
>
> --- 0014/Documentation/devicetree/bindings/timer/renesas,cmt.txt
> +++ work/Documentation/devicetree/bindings/timer/renesas,cmt.txt 2019-06-17 14:07:46.502422801 +0900
> @@ -28,9 +28,9 @@ Required Properties:
> - "renesas,r8a77470-cmt0" for the 32-bit CMT0 device included in r8a77470.
> - "renesas,r8a77470-cmt1" for the 48-bit CMT1 device included in r8a77470.
> - "renesas,r8a774a1-cmt0" for the 32-bit CMT0 device included in r8a774a1.
> - - "renesas,r8a774a1-cmt1" for the 48-bit CMT1 device included in r8a774a1.
> + - "renesas,r8a774a1-cmt1" for the 48-bit CMT devices included in r8a774a1.
> - "renesas,r8a774c0-cmt0" for the 32-bit CMT0 device included in r8a774c0.
> - - "renesas,r8a774c0-cmt1" for the 48-bit CMT1 device included in r8a774c0.
> + - "renesas,r8a774c0-cmt1" for the 48-bit CMT devices included in r8a774c0.
> - "renesas,r8a7790-cmt0" for the 32-bit CMT0 device included in r8a7790.
> - "renesas,r8a7790-cmt1" for the 48-bit CMT1 device included in r8a7790.
> - "renesas,r8a7791-cmt0" for the 32-bit CMT0 device included in r8a7791.
> @@ -42,34 +42,34 @@ Required Properties:
> - "renesas,r8a7794-cmt0" for the 32-bit CMT0 device included in r8a7794.
> - "renesas,r8a7794-cmt1" for the 48-bit CMT1 device included in r8a7794.
> - "renesas,r8a7795-cmt0" for the 32-bit CMT0 device included in r8a7795.
> - - "renesas,r8a7795-cmt1" for the 48-bit CMT1 device included in r8a7795.
> + - "renesas,r8a7795-cmt1" for the 48-bit CMT devices included in r8a7795.
> - "renesas,r8a7796-cmt0" for the 32-bit CMT0 device included in r8a7796.
> - - "renesas,r8a7796-cmt1" for the 48-bit CMT1 device included in r8a7796.
> + - "renesas,r8a7796-cmt1" for the 48-bit CMT devices included in r8a7796.
> - "renesas,r8a77965-cmt0" for the 32-bit CMT0 device included in r8a77965.
> - - "renesas,r8a77965-cmt1" for the 48-bit CMT1 device included in r8a77965.
> + - "renesas,r8a77965-cmt1" for the 48-bit CMT devices included in r8a77965.
> - "renesas,r8a77970-cmt0" for the 32-bit CMT0 device included in r8a77970.
> - - "renesas,r8a77970-cmt1" for the 48-bit CMT1 device included in r8a77970.
> + - "renesas,r8a77970-cmt1" for the 48-bit CMT devices included in r8a77970.
> - "renesas,r8a77980-cmt0" for the 32-bit CMT0 device included in r8a77980.
> - - "renesas,r8a77980-cmt1" for the 48-bit CMT1 device included in r8a77980.
> + - "renesas,r8a77980-cmt1" for the 48-bit CMT devices included in r8a77980.
> - "renesas,r8a77990-cmt0" for the 32-bit CMT0 device included in r8a77990.
> - - "renesas,r8a77990-cmt1" for the 48-bit CMT1 device included in r8a77990.
> + - "renesas,r8a77990-cmt1" for the 48-bit CMT devices included in r8a77990.
> - "renesas,r8a77995-cmt0" for the 32-bit CMT0 device included in r8a77995.
> - - "renesas,r8a77995-cmt1" for the 48-bit CMT1 device included in r8a77995.
> + - "renesas,r8a77995-cmt1" for the 48-bit CMT devices included in r8a77995.
> - "renesas,sh73a0-cmt0" for the 32-bit CMT0 device included in sh73a0.
> - "renesas,sh73a0-cmt1" for the 48-bit CMT1 device included in sh73a0.
> - "renesas,sh73a0-cmt2" for the 32-bit CMT2 device included in sh73a0.
> - "renesas,sh73a0-cmt3" for the 32-bit CMT3 device included in sh73a0.
> - "renesas,sh73a0-cmt4" for the 32-bit CMT4 device included in sh73a0.
>
> - - "renesas,rcar-gen2-cmt0" for 32-bit CMT0 devices included in R-Car Gen2
> + - "renesas,rcar-gen2-cmt0" for 32-bit CMT0 device included in R-Car Gen2
> and RZ/G1.
> - - "renesas,rcar-gen2-cmt1" for 48-bit CMT1 devices included in R-Car Gen2
> + - "renesas,rcar-gen2-cmt1" for 48-bit CMT1 device included in R-Car Gen2
> and RZ/G1.
> These are fallbacks for r8a73a4, R-Car Gen2 and RZ/G1 entries
> listed above.
> - - "renesas,rcar-gen3-cmt0" for 32-bit CMT0 devices included in R-Car Gen3
> + - "renesas,rcar-gen3-cmt0" for 32-bit CMT0 device included in R-Car Gen3
> and RZ/G2.
> - - "renesas,rcar-gen3-cmt1" for 48-bit CMT1 devices included in R-Car Gen3
> + - "renesas,rcar-gen3-cmt1" for 48-bit CMT devices included in R-Car Gen3
> and RZ/G2.
> These are fallbacks for R-Car Gen3 and RZ/G2 entries listed
> above.
>
Reviewed-by: Rob Herring <robh@kernel.org>
^ permalink raw reply
* Re: [PATCH 7/8] dt-bindings: timer: renesas, cmt: Add CMT0 and CMT1 to r8a77995
From: Rob Herring @ 2019-07-09 16:25 UTC (permalink / raw)
To: Magnus Damm; +Cc: devicetree, mark.rutland, linux-renesas-soc, robh+dt
In-Reply-To: <156076223184.4736.11067127180512614106.sendpatchset@octo>
On Mon, 17 Jun 2019 18:03:51 +0900, Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
>
> This patch adds DT binding documentation for the CMT devices on
> the R-Car Gen3 D3 (r8a77995) SoC.
>
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> ---
>
> Documentation/devicetree/bindings/timer/renesas,cmt.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> --- 0012/Documentation/devicetree/bindings/timer/renesas,cmt.txt
> +++ work/Documentation/devicetree/bindings/timer/renesas,cmt.txt 2019-06-17 14:00:04.813217175 +0900
> @@ -53,6 +53,8 @@ Required Properties:
> - "renesas,r8a77980-cmt1" for the 48-bit CMT1 device included in r8a77980.
> - "renesas,r8a77990-cmt0" for the 32-bit CMT0 device included in r8a77990.
> - "renesas,r8a77990-cmt1" for the 48-bit CMT1 device included in r8a77990.
> + - "renesas,r8a77995-cmt0" for the 32-bit CMT0 device included in r8a77995.
> + - "renesas,r8a77995-cmt1" for the 48-bit CMT1 device included in r8a77995.
> - "renesas,sh73a0-cmt0" for the 32-bit CMT0 device included in sh73a0.
> - "renesas,sh73a0-cmt1" for the 48-bit CMT1 device included in sh73a0.
> - "renesas,sh73a0-cmt2" for the 32-bit CMT2 device included in sh73a0.
>
Reviewed-by: Rob Herring <robh@kernel.org>
^ permalink raw reply
* Re: [PATCH 6/8] dt-bindings: timer: renesas, cmt: Add CMT0 and CMT1 to r8a77990
From: Rob Herring @ 2019-07-09 16:25 UTC (permalink / raw)
To: Magnus Damm; +Cc: devicetree, mark.rutland, linux-renesas-soc, robh+dt
In-Reply-To: <156076222206.4736.3009593403446400658.sendpatchset@octo>
On Mon, 17 Jun 2019 18:03:42 +0900, Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
>
> This patch adds DT binding documentation for the CMT devices on
> the R-Car Gen3 E3 (r8a77990) SoC.
>
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> ---
>
> Documentation/devicetree/bindings/timer/renesas,cmt.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> --- 0010/Documentation/devicetree/bindings/timer/renesas,cmt.txt
> +++ work/Documentation/devicetree/bindings/timer/renesas,cmt.txt 2019-06-17 13:58:48.559219302 +0900
> @@ -51,6 +51,8 @@ Required Properties:
> - "renesas,r8a77970-cmt1" for the 48-bit CMT1 device included in r8a77970.
> - "renesas,r8a77980-cmt0" for the 32-bit CMT0 device included in r8a77980.
> - "renesas,r8a77980-cmt1" for the 48-bit CMT1 device included in r8a77980.
> + - "renesas,r8a77990-cmt0" for the 32-bit CMT0 device included in r8a77990.
> + - "renesas,r8a77990-cmt1" for the 48-bit CMT1 device included in r8a77990.
> - "renesas,sh73a0-cmt0" for the 32-bit CMT0 device included in sh73a0.
> - "renesas,sh73a0-cmt1" for the 48-bit CMT1 device included in sh73a0.
> - "renesas,sh73a0-cmt2" for the 32-bit CMT2 device included in sh73a0.
>
Reviewed-by: Rob Herring <robh@kernel.org>
^ permalink raw reply
* Re: [PATCH 5/8] dt-bindings: timer: renesas, cmt: Add CMT0 and CMT1 to r8a77965
From: Rob Herring @ 2019-07-09 16:23 UTC (permalink / raw)
To: Magnus Damm; +Cc: devicetree, mark.rutland, linux-renesas-soc, robh+dt
In-Reply-To: <156076221311.4736.11788780573341776795.sendpatchset@octo>
On Mon, 17 Jun 2019 18:03:33 +0900, Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
>
> This patch adds DT binding documentation for the CMT devices on
> the R-Car Gen3 M3-N (r8a77965) SoC.
>
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> ---
>
> Documentation/devicetree/bindings/timer/renesas,cmt.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> --- 0009/Documentation/devicetree/bindings/timer/renesas,cmt.txt
> +++ work/Documentation/devicetree/bindings/timer/renesas,cmt.txt 2019-06-17 13:57:59.708658149 +0900
> @@ -45,6 +45,8 @@ Required Properties:
> - "renesas,r8a7795-cmt1" for the 48-bit CMT1 device included in r8a7795.
> - "renesas,r8a7796-cmt0" for the 32-bit CMT0 device included in r8a7796.
> - "renesas,r8a7796-cmt1" for the 48-bit CMT1 device included in r8a7796.
> + - "renesas,r8a77965-cmt0" for the 32-bit CMT0 device included in r8a77965.
> + - "renesas,r8a77965-cmt1" for the 48-bit CMT1 device included in r8a77965.
> - "renesas,r8a77970-cmt0" for the 32-bit CMT0 device included in r8a77970.
> - "renesas,r8a77970-cmt1" for the 48-bit CMT1 device included in r8a77970.
> - "renesas,r8a77980-cmt0" for the 32-bit CMT0 device included in r8a77980.
>
Reviewed-by: Rob Herring <robh@kernel.org>
^ permalink raw reply
* Re: [PATCH 4/8] dt-bindings: timer: renesas, cmt: Add CMT0 and CMT1 to r8a7795
From: Rob Herring @ 2019-07-09 16:23 UTC (permalink / raw)
To: Magnus Damm; +Cc: devicetree, mark.rutland, linux-renesas-soc, robh+dt
In-Reply-To: <156076220389.4736.5742093495634461883.sendpatchset@octo>
On Mon, 17 Jun 2019 18:03:23 +0900, Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
>
> This patch adds DT binding documentation for the CMT devices on
> the R-Car Gen3 H3 (r8a7795) SoC.
>
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> ---
>
> Documentation/devicetree/bindings/timer/renesas,cmt.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> --- 0006/Documentation/devicetree/bindings/timer/renesas,cmt.txt
> +++ work/Documentation/devicetree/bindings/timer/renesas,cmt.txt 2019-06-17 13:53:43.252212551 +0900
> @@ -41,6 +41,8 @@ Required Properties:
> - "renesas,r8a7793-cmt1" for the 48-bit CMT1 device included in r8a7793.
> - "renesas,r8a7794-cmt0" for the 32-bit CMT0 device included in r8a7794.
> - "renesas,r8a7794-cmt1" for the 48-bit CMT1 device included in r8a7794.
> + - "renesas,r8a7795-cmt0" for the 32-bit CMT0 device included in r8a7795.
> + - "renesas,r8a7795-cmt1" for the 48-bit CMT1 device included in r8a7795.
> - "renesas,r8a7796-cmt0" for the 32-bit CMT0 device included in r8a7796.
> - "renesas,r8a7796-cmt1" for the 48-bit CMT1 device included in r8a7796.
> - "renesas,r8a77970-cmt0" for the 32-bit CMT0 device included in r8a77970.
>
Reviewed-by: Rob Herring <robh@kernel.org>
^ permalink raw reply
* Re: [PATCH 3/8] dt-bindings: timer: renesas, cmt: Add CMT0 and CMT1 to r8a7792
From: Rob Herring @ 2019-07-09 16:23 UTC (permalink / raw)
To: Magnus Damm; +Cc: devicetree, mark.rutland, linux-renesas-soc, robh+dt
In-Reply-To: <156076219472.4736.14727682068388338615.sendpatchset@octo>
On Mon, 17 Jun 2019 18:03:14 +0900, Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
>
> This patch adds DT binding documentation for the CMT devices on
> the R-Car Gen2 V2H (r8a7792) SoC.
>
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> ---
>
> Documentation/devicetree/bindings/timer/renesas,cmt.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> --- 0004/Documentation/devicetree/bindings/timer/renesas,cmt.txt
> +++ work/Documentation/devicetree/bindings/timer/renesas,cmt.txt 2019-06-17 13:35:10.526874153 +0900
> @@ -35,6 +35,8 @@ Required Properties:
> - "renesas,r8a7790-cmt1" for the 48-bit CMT1 device included in r8a7790.
> - "renesas,r8a7791-cmt0" for the 32-bit CMT0 device included in r8a7791.
> - "renesas,r8a7791-cmt1" for the 48-bit CMT1 device included in r8a7791.
> + - "renesas,r8a7792-cmt0" for the 32-bit CMT0 device included in r8a7792.
> + - "renesas,r8a7792-cmt1" for the 48-bit CMT1 device included in r8a7792.
> - "renesas,r8a7793-cmt0" for the 32-bit CMT0 device included in r8a7793.
> - "renesas,r8a7793-cmt1" for the 48-bit CMT1 device included in r8a7793.
> - "renesas,r8a7794-cmt0" for the 32-bit CMT0 device included in r8a7794.
>
Reviewed-by: Rob Herring <robh@kernel.org>
^ permalink raw reply
* Re: [PATCH 2/8] dt-bindings: timer: renesas, cmt: Update CMT1 on sh73a0 and r8a7740
From: Rob Herring @ 2019-07-09 16:23 UTC (permalink / raw)
To: Magnus Damm; +Cc: devicetree, mark.rutland, linux-renesas-soc, robh+dt
In-Reply-To: <156076218574.4736.10317127566447729303.sendpatchset@octo>
On Mon, 17 Jun 2019 18:03:05 +0900, Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
>
> This patch reworks the DT binding documentation for the 6-channel
> 48-bit CMTs known as CMT1 on r8a7740 and sh73a0.
>
> After the update the same style of DT binding as the rest of the upstream
> SoCs will now also be used by r8a7740 and sh73a0. The DT binding "cmt-48"
> is removed from the DT binding documentation, however software support for
> this deprecated binding will still remain in the CMT driver for some time.
>
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> ---
>
> Documentation/devicetree/bindings/timer/renesas,cmt.txt | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
>
> --- 0002/Documentation/devicetree/bindings/timer/renesas,cmt.txt
> +++ work/Documentation/devicetree/bindings/timer/renesas,cmt.txt 2019-06-17 13:31:52.766505901 +0900
> @@ -12,17 +12,10 @@ datasheets.
> Required Properties:
>
> - compatible: must contain one or more of the following:
> - - "renesas,cmt-48-sh73a0" for the sh73A0 48-bit CMT
> - (CMT1)
> - - "renesas,cmt-48-r8a7740" for the r8a7740 48-bit CMT
> - (CMT1)
> - - "renesas,cmt-48" for all non-second generation 48-bit CMT
> - (CMT1 on sh73a0 and r8a7740)
> - This is a fallback for the above renesas,cmt-48-* entries.
> -
> - "renesas,r8a73a4-cmt0" for the 32-bit CMT0 device included in r8a73a4.
> - "renesas,r8a73a4-cmt1" for the 48-bit CMT1 device included in r8a73a4.
> - "renesas,r8a7740-cmt0" for the 32-bit CMT0 device included in r8a7740.
> + - "renesas,r8a7740-cmt1" for the 48-bit CMT1 device included in r8a7740.
> - "renesas,r8a7740-cmt2" for the 32-bit CMT2 device included in r8a7740.
> - "renesas,r8a7740-cmt3" for the 32-bit CMT3 device included in r8a7740.
> - "renesas,r8a7740-cmt4" for the 32-bit CMT4 device included in r8a7740.
> @@ -53,6 +46,7 @@ Required Properties:
> - "renesas,r8a77980-cmt0" for the 32-bit CMT0 device included in r8a77980.
> - "renesas,r8a77980-cmt1" for the 48-bit CMT1 device included in r8a77980.
> - "renesas,sh73a0-cmt0" for the 32-bit CMT0 device included in sh73a0.
> + - "renesas,sh73a0-cmt1" for the 48-bit CMT1 device included in sh73a0.
> - "renesas,sh73a0-cmt2" for the 32-bit CMT2 device included in sh73a0.
> - "renesas,sh73a0-cmt3" for the 32-bit CMT3 device included in sh73a0.
> - "renesas,sh73a0-cmt4" for the 32-bit CMT4 device included in sh73a0.
>
Reviewed-by: Rob Herring <robh@kernel.org>
^ permalink raw reply
* Re: [PATCH 1/8] dt-bindings: timer: renesas, cmt: Add CMT0234 to sh73a0 and r8a7740
From: Rob Herring @ 2019-07-09 16:21 UTC (permalink / raw)
To: Magnus Damm; +Cc: devicetree, mark.rutland, linux-renesas-soc, robh+dt
In-Reply-To: <156076217672.4736.6510117188637868943.sendpatchset@octo>
On Mon, 17 Jun 2019 18:02:56 +0900, Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
>
> Document the on-chip CMT devices included in r8a7740 and sh73a0.
>
> Included in this patch is DT binding documentation for 32-bit CMTs
> CMT0, CMT2, CMT3 and CMT4. They all contain a single channel and are
> quite similar however some minor differences still exist:
> - "Counter input clock" (clock input and on-device divider)
> One example is that RCLK 1/1 is supported by CMT2, CMT3 and CMT4.
> - "Wakeup request" (supported by CMT0 and CMT2)
>
> Because of this one unique compat string per CMT device is selected.
>
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> ---
>
> Documentation/devicetree/bindings/timer/renesas,cmt.txt | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> --- 0001/Documentation/devicetree/bindings/timer/renesas,cmt.txt
> +++ work/Documentation/devicetree/bindings/timer/renesas,cmt.txt 2019-06-17 13:26:56.325963995 +0900
> @@ -22,6 +22,10 @@ Required Properties:
>
> - "renesas,r8a73a4-cmt0" for the 32-bit CMT0 device included in r8a73a4.
> - "renesas,r8a73a4-cmt1" for the 48-bit CMT1 device included in r8a73a4.
> + - "renesas,r8a7740-cmt0" for the 32-bit CMT0 device included in r8a7740.
> + - "renesas,r8a7740-cmt2" for the 32-bit CMT2 device included in r8a7740.
> + - "renesas,r8a7740-cmt3" for the 32-bit CMT3 device included in r8a7740.
> + - "renesas,r8a7740-cmt4" for the 32-bit CMT4 device included in r8a7740.
> - "renesas,r8a7743-cmt0" for the 32-bit CMT0 device included in r8a7743.
> - "renesas,r8a7743-cmt1" for the 48-bit CMT1 device included in r8a7743.
> - "renesas,r8a7744-cmt0" for the 32-bit CMT0 device included in r8a7744.
> @@ -48,6 +52,10 @@ Required Properties:
> - "renesas,r8a77970-cmt1" for the 48-bit CMT1 device included in r8a77970.
> - "renesas,r8a77980-cmt0" for the 32-bit CMT0 device included in r8a77980.
> - "renesas,r8a77980-cmt1" for the 48-bit CMT1 device included in r8a77980.
> + - "renesas,sh73a0-cmt0" for the 32-bit CMT0 device included in sh73a0.
> + - "renesas,sh73a0-cmt2" for the 32-bit CMT2 device included in sh73a0.
> + - "renesas,sh73a0-cmt3" for the 32-bit CMT3 device included in sh73a0.
> + - "renesas,sh73a0-cmt4" for the 32-bit CMT4 device included in sh73a0.
>
> - "renesas,rcar-gen2-cmt0" for 32-bit CMT0 devices included in R-Car Gen2
> and RZ/G1.
>
Reviewed-by: Rob Herring <robh@kernel.org>
^ permalink raw reply
* Re: [PATCH v2 17/28] drivers: Introduce bus_find_device_by_of_node() helper
From: Rob Herring @ 2019-07-09 16:19 UTC (permalink / raw)
Cc: linux-kernel, gregkh, rafael, suzuki.poulose, Maarten Lankhorst,
Maxime Ripard, dri-devel, David Airlie, Daniel Vetter, devicetree,
Florian Fainelli, Frank Rowand, Heiko Stuebner, Liam Girdwood,
linux-i2c, linux-rockchip, linux-spi, Mathieu Poirier,
Srinivas Kandagatla, Takashi Iwai, Wolfram Sang
In-Reply-To: <1560534863-15115-18-git-send-email-suzuki.poulose@arm.com>
On Fri, 14 Jun 2019 18:54:12 +0100, Suzuki K Poulose wrote:
> Add a wrapper to bus_find_device() to search for a device
> by the of_node pointer, reusing the generic match function.
> Also convert the existing users to make use of the new helper.
>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Maxime Ripard <maxime.ripard@bootlin.com>
> Cc: dri-devel@lists.freedesktop.org
> Cc: David Airlie <airlied@linux.ie>
> Cc: Daniel Vetter <daniel@ffwll.ch>
> Cc: devicetree@vger.kernel.org
> Cc: Florian Fainelli <f.fainelli@gmail.com>
> Cc: Frank Rowand <frowand.list@gmail.com>
> Cc: Heiko Stuebner <heiko@sntech.de>
> Cc: Liam Girdwood <lgirdwood@gmail.com>
> Cc: linux-i2c@vger.kernel.org
> Cc: linux-rockchip@lists.infradead.org
> Cc: linux-spi@vger.kernel.org
> Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> Cc: Takashi Iwai <tiwai@suse.com>
> Cc: Wolfram Sang <wsa@the-dreams.de>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: "Rafael J. Wysocki" <rafael@kernel.org>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
> ---
> drivers/gpu/drm/drm_mipi_dsi.c | 7 +------
> drivers/hwtracing/coresight/of_coresight.c | 11 ++---------
> drivers/i2c/i2c-core-of.c | 7 +------
> drivers/nvmem/core.c | 7 +------
> drivers/of/of_mdio.c | 8 +-------
> drivers/of/platform.c | 7 +------
> drivers/spi/spi.c | 9 ++-------
> include/linux/device.h | 12 ++++++++++++
> sound/soc/rockchip/rk3399_gru_sound.c | 9 ++-------
> 9 files changed, 23 insertions(+), 54 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
^ permalink raw reply
* Re: [PATCH] ARM: bcm47094: add missing #cells for mdio-bus-mux
From: Florian Fainelli @ 2019-07-09 16:16 UTC (permalink / raw)
To: bcm-kernel-feedback-list, Arnd Bergmann, Hauke Mehrtens,
Rafał Miłecki, Rob Herring, Mark Rutland
Cc: Vivek Unune, Alexandre TORGUE, Neil Armstrong, linux-arm-kernel,
devicetree, linux-kernel
In-Reply-To: <20190703132255.852025-1-arnd@arndb.de>
On Wed, 3 Jul 2019 15:22:45 +0200, Arnd Bergmann <arnd@arndb.de> wrote:
> The mdio-bus-mux has no #address-cells/#size-cells property,
> which causes a few dtc warnings:
>
> arch/arm/boot/dts/bcm47094-linksys-panamera.dts:129.4-18: Warning (reg_format): /mdio-bus-mux/mdio@200:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
> arch/arm/boot/dts/bcm47094-linksys-panamera.dtb: Warning (pci_device_bus_num): Failed prerequisite 'reg_format'
> arch/arm/boot/dts/bcm47094-linksys-panamera.dtb: Warning (i2c_bus_reg): Failed prerequisite 'reg_format'
> arch/arm/boot/dts/bcm47094-linksys-panamera.dtb: Warning (spi_bus_reg): Failed prerequisite 'reg_format'
> arch/arm/boot/dts/bcm47094-linksys-panamera.dts:128.22-132.5: Warning (avoid_default_addr_size): /mdio-bus-mux/mdio@200: Relying on default #address-cells value
> arch/arm/boot/dts/bcm47094-linksys-panamera.dts:128.22-132.5: Warning (avoid_default_addr_size): /mdio-bus-mux/mdio@200: Relying on default #size-cells value
>
> Add the normal cell numbers.
>
> Fixes: 2bebdfcdcd0f ("ARM: dts: BCM5301X: Add support for Linksys EA9500")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
Applied to devicetree/fixes, thanks!
--
Florian
^ permalink raw reply
* Re: [PATCH v2 7/9] dt-bindings: sun6i-dsi: Add R40 DPHY compatible (w/ A31 fallback)
From: Rob Herring @ 2019-07-09 16:16 UTC (permalink / raw)
Cc: Maxime Ripard, David Airlie, Daniel Vetter, Chen-Yu Tsai,
dri-devel, linux-arm-kernel, linux-kernel, devicetree,
Jernej Skrabec, linux-sunxi, Michael Trimarchi, linux-amarula,
Jagan Teki
In-Reply-To: <20190614164324.9427-8-jagan@amarulasolutions.com>
On Fri, 14 Jun 2019 22:13:22 +0530, Jagan Teki wrote:
> The MIPI DSI PHY controller on Allwinner R40 is similar
> on the one on A31.
>
> Add R40 compatible and append A31 compatible as fallback.
>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---
> Documentation/devicetree/bindings/display/sunxi/sun6i-dsi.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
^ permalink raw reply
* Re: [PATCH V4 2/2] gpio: inverter: document the inverter bindings
From: Rob Herring @ 2019-07-09 16:08 UTC (permalink / raw)
To: Harish Jenny K N
Cc: Linus Walleij, Bartosz Golaszewski, Mark Rutland, devicetree,
open list:GPIO SUBSYSTEM, Balasubramani Vivekanandan
In-Reply-To: <06c95f15-d577-e43d-e046-ee222f86c406@mentor.com>
On Mon, Jul 8, 2019 at 11:25 PM Harish Jenny K N
<harish_kandiga@mentor.com> wrote:
>
> Hi Rob,
>
>
> On 09/07/19 4:06 AM, Rob Herring wrote:
> > On Fri, Jun 28, 2019 at 3:31 AM Harish Jenny K N
> > <harish_kandiga@mentor.com> wrote:
> >> Document the device tree binding for the inverter gpio
> >> controller to configure the polarity of the gpio pins
> >> used by the consumers.
> >>
> >> Signed-off-by: Harish Jenny K N <harish_kandiga@mentor.com>
> >> ---
> >> .../devicetree/bindings/gpio/gpio-inverter.txt | 29 ++++++++++++++++++++++
> >> 1 file changed, 29 insertions(+)
> >> create mode 100644 Documentation/devicetree/bindings/gpio/gpio-inverter.txt
> >>
> >> diff --git a/Documentation/devicetree/bindings/gpio/gpio-inverter.txt b/Documentation/devicetree/bindings/gpio/gpio-inverter.txt
> >> new file mode 100644
> >> index 0000000..8bb6b2e
> >> --- /dev/null
> >> +++ b/Documentation/devicetree/bindings/gpio/gpio-inverter.txt
> >> @@ -0,0 +1,29 @@
> >> +GPIO-INVERTER
> >> +======
> >> +This binding defines the gpio-inverter. The gpio-inverter is a driver that
> >> +allows to properly describe the gpio polarities on the hardware.
> > I don't understand. Please explain this in terms of the hardware, not a driver.
>
>
> gpio inverters can be used on different hardware to alter the polarity of gpio chips.
> The polarity of pins can change from hardware to hardware with the use of inverters.
Yes, I know what an inverter is.
> This device tree binding models gpio inverters in the device tree to properly describe the hardware.
We already define the active state of GPIOs in the consumers. If
there's an inverter in the middle, the consumer active state is simply
inverted. I don't agree that that is a hack as Linus said without some
reasoning why an inverter needs to be modeled in DT. Anything about
what 'userspace' needs is not a reason. That's a Linux thing that has
little to do with hardware description.
Rob
^ permalink raw reply
* Re: [PATCH 5.2 v2 2/2] dt-binding: edac: add NPCM ECC documentation
From: Rob Herring @ 2019-07-09 15:48 UTC (permalink / raw)
To: George Hung (洪忠敬)
Cc: George Hung, Mark Rutland, Linus Walleij, Tali Perry,
paulmck@linux.ibm.com, wak@google.com, benjaminfair@google.com,
openbmc@lists.ozlabs.org, tomer.maimon@nuvoton.com,
devicetree@vger.kernel.org, Borislav Petkov,
Avi.Fishman@nuvoton.com, Jonathan Cameron, Mauro Carvalho Chehab,
linux-edac, Patrick Venture, Nicolas Ferre
In-Reply-To: <0c90f9376c0e425c9a226379f7e5bfad@quantatw.com>
On Tue, Jul 9, 2019 at 3:50 AM George Hung (洪忠敬)
<George.Hung@quantatw.com> wrote:
>
> Hi Rob,
>
>
> > -----Original Message-----
> > From: openbmc
> > [mailto:openbmc-bounces+george.hung=quantatw.com@lists.ozlabs.org] On
> > Behalf Of Rob Herring
> > Sent: Tuesday, July 09, 2019 9:41 AM
> > To: George Hung
> > Cc: Mark Rutland; Linus Walleij; Tali Perry; paulmck@linux.ibm.com;
> > wak@google.com; benjaminfair@google.com; openbmc@lists.ozlabs.org;
> > tomer.maimon@nuvoton.com; devicetree@vger.kernel.org; Borislav Petkov;
> > Avi.Fishman@nuvoton.com; Jonathan Cameron; Mauro Carvalho Chehab;
> > linux-edac; Patrick Venture; Nicolas Ferre; linux-kernel; James Morse; Greg
> > Kroah-Hartman; davem@davemloft.net
> > Subject: Re: [PATCH 5.2 v2 2/2] dt-binding: edac: add NPCM ECC
> > documentation
> >
> > On Wed, Jun 05, 2019 at 10:12:53PM +0800, George Hung wrote:
> > > Add device tree documentation for Nuvoton BMC ECC
> > >
> > > Signed-off-by: George Hung <ghung.quanta@gmail.com>
> > > ---
> > > .../bindings/edac/npcm7xx-sdram-edac.txt | 17
> > +++++++++++++++++
> > > 1 file changed, 17 insertions(+)
> > > create mode 100644
> > > Documentation/devicetree/bindings/edac/npcm7xx-sdram-edac.txt
> > >
> > > diff --git
> > > a/Documentation/devicetree/bindings/edac/npcm7xx-sdram-edac.txt
> > > b/Documentation/devicetree/bindings/edac/npcm7xx-sdram-edac.txt
> > > new file mode 100644
> > > index 000000000000..dd4dac59a5bd
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/edac/npcm7xx-sdram-edac.txt
> > > @@ -0,0 +1,17 @@
> > > +Nuvoton NPCM7xx SoC EDAC device driver
> > > +
> > > +The Nuvoton NPCM7xx SoC supports DDR4 memory with/without ECC and
> > the
> > > +driver uses the EDAC framework to implement the ECC detection and
> > corrtection.
> > > +
> > > +Required properties:
> > > +- compatible: should be "nuvoton,npcm7xx-sdram-edac"
> >
> > Is this for the whole SDRAM controller or just ECC related registers?
> > In the former case, the naming should just reflect the block name and not a
> > Linux term.
>
> Sorry for confused naming, the address space is for the whole memory controller registers indeed,
> but the driver only uses the ECC related registers.
> Should I change the name to "nuvoton,npcm7xx-edac" ?
No, you should drop the 'edac' part. The DT describes the h/w, not
what one driver (currently) uses.
Rob
^ permalink raw reply
* Re: [PATCH v2 1/6] dt-bindings: Remove unused compatible strings
From: Rob Herring @ 2019-07-09 15:46 UTC (permalink / raw)
To: Paul Cercueil
Cc: Thierry Reding, Mark Rutland, od, Linux PWM List, devicetree,
linux-kernel@vger.kernel.org
In-Reply-To: <1562642299.1834.0@crapouillou.net>
On Mon, Jul 8, 2019 at 9:18 PM Paul Cercueil <paul@crapouillou.net> wrote:
>
>
>
> Le lun. 8 juil. 2019 à 22:04, Rob Herring <robh@kernel.org> a écrit :
> > On Fri, Jun 07, 2019 at 05:44:05PM +0200, Paul Cercueil wrote:
> >> Right now none of the Ingenic-based boards probe this driver from
> >> devicetree. This driver defined three compatible strings for the
> >> exact
> >> same behaviour. Before these strings are used, we can remove two of
> >> them.
> >>
> >> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
> >> ---
> >>
> >> Notes:
> >> v2: Rebase on v5.2-rc3
> >>
> >> Documentation/devicetree/bindings/pwm/ingenic,jz47xx-pwm.txt | 5
> >> +----
> >> 1 file changed, 1 insertion(+), 4 deletions(-)
> >>
> >> diff --git
> >> a/Documentation/devicetree/bindings/pwm/ingenic,jz47xx-pwm.txt
> >> b/Documentation/devicetree/bindings/pwm/ingenic,jz47xx-pwm.txt
> >> index 7d9d3f90641b..493bec80d59b 100644
> >> --- a/Documentation/devicetree/bindings/pwm/ingenic,jz47xx-pwm.txt
> >> +++ b/Documentation/devicetree/bindings/pwm/ingenic,jz47xx-pwm.txt
> >> @@ -2,10 +2,7 @@ Ingenic JZ47xx PWM Controller
> >> =============================
> >>
> >> Required properties:
> >> -- compatible: One of:
> >> - * "ingenic,jz4740-pwm"
> >> - * "ingenic,jz4770-pwm"
> >> - * "ingenic,jz4780-pwm"
> >> +- compatible: Should be "ingenic,jz4740-pwm"
> >
> > Are you sure all 3 chips are exactly the same features and bugs?
>
> The hardware on these chips have tiny differences, but the current
> driver code works on all the SoCs.
>
>
> > The correct thing to do here generally is the 4770 and 4780 would also
> > have ingenic,jz4740-pwm as a fallback compatible. Then the driver can
> > match on that until you find some difference and can use the more
> > specific compatible.
>
> Why not just update the devicetree with the new compatible string when
> a difference is found?
Because dtb's should be part of the firmware/bootloader and can be
updated independently. Maybe you don't care on your platform, but
that's the preferred model for DT and what we follow. DTs live in the
kernel tree for convenience, but are independent from the kernel.
Rob
^ permalink raw reply
* Re: [PATCH v7 16/18] MAINTAINERS: add entry for KUnit the unit testing framework
From: shuah @ 2019-07-09 14:53 UTC (permalink / raw)
To: Brendan Higgins, frowand.list, gregkh, jpoimboe, keescook,
kieran.bingham, mcgrof, peterz, robh, sboyd, tytso,
yamada.masahiro
Cc: pmladek, linux-doc, amir73il, dri-devel, Alexander.Levin,
linux-kselftest, shuah, linux-nvdimm, khilman, knut.omang, wfg,
joel, rientjes, jdike, dan.carpenter, devicetree, linux-kbuild,
Tim.Bird, linux-um, rostedt, julia.lawall, kunit-dev, richard,
rdunlap, linux-kernel, mpe, linux-fsdevel, logang
In-Reply-To: <20190709063023.251446-17-brendanhiggins@google.com>
On 7/9/19 12:30 AM, Brendan Higgins wrote:
> Add myself as maintainer of KUnit, the Linux kernel's unit testing
> framework.
>
> Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
> ---
> MAINTAINERS | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 677ef41cb012c..48d04d180a988 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8599,6 +8599,17 @@ S: Maintained
> F: tools/testing/selftests/
> F: Documentation/dev-tools/kselftest*
>
> +KERNEL UNIT TESTING FRAMEWORK (KUnit)
> +M: Brendan Higgins <brendanhiggins@google.com>
> +L: linux-kselftest@vger.kernel.org
> +L: kunit-dev@googlegroups.com
> +W: https://google.github.io/kunit-docs/third_party/kernel/docs/
> +S: Maintained
> +F: Documentation/dev-tools/kunit/
> +F: include/kunit/
> +F: kunit/
> +F: tools/testing/kunit/
> +
> KERNEL USERMODE HELPER
> M: Luis Chamberlain <mcgrof@kernel.org>
> L: linux-kernel@vger.kernel.org
>
Thanks Brendan.
I am good with this. I can take KUnit patches through kselftest
with your Ack.
thanks,
-- Shuah
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply
* Re: [PATCH v2 6/9] dt-bindings: sun6i-dsi: Add R40 MIPI-DSI compatible (w/ A64 fallback)
From: Rob Herring @ 2019-07-09 14:50 UTC (permalink / raw)
Cc: Maxime Ripard, David Airlie, Daniel Vetter, Chen-Yu Tsai,
dri-devel, linux-arm-kernel, linux-kernel, devicetree,
Jernej Skrabec, Michael Trimarchi, linux-sunxi, linux-amarula,
Jagan Teki
In-Reply-To: <20190614164324.9427-7-jagan@amarulasolutions.com>
On Fri, 14 Jun 2019 22:13:21 +0530, Jagan Teki wrote:
> The MIPI DSI controller on Allwinner R40 is similar on
> the one on A64 like doesn't associate any DSI_SCLK gating.
>
> So, add R40 compatible and append A64 compatible as fallback.
>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---
> Documentation/devicetree/bindings/display/sunxi/sun6i-dsi.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
^ permalink raw reply
* Re: [PATCH v2 1/9] dt-bindings: display: Add TCON LCD compatible for R40
From: Rob Herring @ 2019-07-09 14:49 UTC (permalink / raw)
Cc: Maxime Ripard, David Airlie, Daniel Vetter, Chen-Yu Tsai,
dri-devel, linux-arm-kernel, linux-kernel, devicetree,
Jernej Skrabec, Michael Trimarchi, linux-sunxi, linux-amarula,
Jagan Teki
In-Reply-To: <20190614164324.9427-2-jagan@amarulasolutions.com>
On Fri, 14 Jun 2019 22:13:16 +0530, Jagan Teki wrote:
> Like TCON TV0, TV1 allwinner R40 has TCON LCD0, LCD1 which
> are managed via TCON TOP.
>
> Add tcon lcd compatible R40, the same compatible can handle
> TCON LCD0, LCD1.
>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> Acked-by: Chen-Yu Tsai <wens@csie.org>
> ---
> Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
^ permalink raw reply
* Re: [v3 2/2] dt-bindings: nand: Add Cadence NAND controller driver
From: Rob Herring @ 2019-07-09 14:48 UTC (permalink / raw)
To: Piotr Sroka
Cc: linux-kernel, David Woodhouse, BrianNorris, Boris Brezillon,
Marek Vasut, Richard Weinberger, Mark Rutland, linux-mtd,
devicetree
In-Reply-To: <20190614151301.5371-1-piotrs@cadence.com>
On Fri, Jun 14, 2019 at 04:13:01PM +0100, Piotr Sroka wrote:
> Signed-off-by: Piotr Sroka <piotrs@cadence.com>
> ---
> Changes for v3:
> - add unit suffix for board_delay
> - move child description to proper place
> - remove prefix cadence_ for reg and sdma fields
> Changes for v2:
> - remove chip dependends parameters from dts bindings
> - add names for register ranges in dts bindings
> - add generic bindings to describe NAND chip representation
> ---
> .../bindings/mtd/cadence-nand-controller.txt | 51 ++++++++++++++++++++++
> 1 file changed, 51 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt
>
> diff --git a/Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt b/Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt
> new file mode 100644
> index 000000000000..e485b87075bd
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt
> @@ -0,0 +1,51 @@
> +* Cadence NAND controller
> +
> +Required properties:
> + - compatible : "cdns,hpnfc"
Only 1 version of h/w features and bugs?
'hp-nfc' would be a bit more readable IMO.
> + - reg : Contains two entries, each of which is a tuple consisting of a
> + physical address and length. The first entry is the address and
> + length of the controller register set. The second entry is the
> + address and length of the Slave DMA data port.
> + - reg-names: should contain "reg" and "sdma"
> + - interrupts : The interrupt number.
> + - clocks: phandle of the controller core clock (nf_clk).
> +
> +Optional properties:
> + - dmas: shall reference DMA channel associated to the NAND controller
> + - cdns,board-delay_ps : Estimated Board delay. The value includes the total
s/_/-/
> + round trip delay for the signals and is used for deciding on values
> + associated with data read capture. The example formula for SDR mode is
> + the following:
> + board_delay = RE#PAD_delay + PCB trace to device + PCB trace from device
> + + DQ PAD delay
> +
> +Children nodes represent the available NAND chips.
Child nodes...
> +
> +Required properties of NAND chips:
> + - reg: shall contain the native Chip Select ids from 0 to max supported by
> + the cadence nand flash controller
> +
> +
> +See Documentation/devicetree/bindings/mtd/nand.txt for more details on
> +generic bindings.
> +
> +Example:
> +
> +nand_controller: nand-controller @60000000 {
remove space ^
> +
> + compatible = "cdns,hpnfc";
> + reg = <0x60000000 0x10000>, <0x80000000 0x10000>;
> + reg-names = "reg", "sdma";
> + clocks = <&nf_clk>;
> + cdns,board-delay_ps = <4830>;
> + interrupts = <2 0>;
> + nand@0 {
> + reg = <0>;
> + label = "nand-1";
> + };
> + nand@1 {
> + reg = <1>;
> + label = "nand-2";
> + };
> +
> +};
> --
> 2.15.0
>
^ permalink raw reply
* Re: [PATCH 4/8] dt-bindings: tpm: document properties for cr50
From: Rob Herring @ 2019-07-09 14:41 UTC (permalink / raw)
To: Stephen Boyd
Cc: Peter Huewe, Jarkko Sakkinen, Andrey Pronin, linux-kernel,
Jason Gunthorpe, Arnd Bergmann, Greg Kroah-Hartman,
linux-integrity, devicetree, Duncan Laurie, Guenter Roeck
In-Reply-To: <20190613180931.65445-5-swboyd@chromium.org>
On Thu, Jun 13, 2019 at 11:09:27AM -0700, Stephen Boyd wrote:
> From: Andrey Pronin <apronin@chromium.org>
>
> Add TPM2.0 PTP FIFO compatible SPI interface for chips with Cr50
> firmware.
>
> Signed-off-by: Andrey Pronin <apronin@chromium.org>
> Cc: Rob Herring <robh+dt@kernel.org>
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> ---
>
> This is a resend of https://lkml.kernel.org/r/1469757314-116169-2-git-send-email-apronin@chromium.org
> with status removed.
>
> .../bindings/security/tpm/cr50_spi.txt | 19 +++++++++++++++++++
google,cr50.txt instead.
With that,
Reviewed-by: Rob Herring <robh@kernel.org>
> 1 file changed, 19 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/security/tpm/cr50_spi.txt
^ permalink raw reply
* Re: [PATCH v3 02/10] dt-bindings: serial: add optional pinctrl states
From: Rob Herring @ 2019-07-09 14:38 UTC (permalink / raw)
To: Erwan Le Ray
Cc: Greg Kroah-Hartman, Jiri Slaby, Maxime Coquelin, Alexandre Torgue,
Mark Rutland, linux-serial, linux-stm32, linux-arm-kernel,
linux-kernel, devicetree, Fabrice Gasnier, Bich Hemon
In-Reply-To: <1560433800-12255-3-git-send-email-erwan.leray@st.com>
On Thu, Jun 13, 2019 at 03:49:52PM +0200, Erwan Le Ray wrote:
> From: Bich Hemon <bich.hemon@st.com>
>
> Add options for pinctrl states:
> - "sleep" for low power
> - "idle" for low power and wakeup capabilities enabled
> - "no_console_suspend" for enabling console messages in low power
>
> Signed-off-by: Bich Hemon <bich.hemon@st.com>
> Signed-off-by: Erwan Le Ray <erwan.leray@st.com>
>
> diff --git a/Documentation/devicetree/bindings/serial/st,stm32-usart.txt b/Documentation/devicetree/bindings/serial/st,stm32-usart.txt
> index 5ec80c1..64a5ea9 100644
> --- a/Documentation/devicetree/bindings/serial/st,stm32-usart.txt
> +++ b/Documentation/devicetree/bindings/serial/st,stm32-usart.txt
> @@ -13,7 +13,14 @@ Required properties:
> - clocks: The input clock of the USART instance
>
> Optional properties:
> -- pinctrl: The reference on the pins configuration
> +- pinctrl-names: Set to "default". An additional "sleep" state can be defined
> + to set pins in sleep state when in low power. In case the device is used as
> + a wakeup source, "idle" state is defined in order to keep RX pin active.
> + For a console device, an optional state "no_console_suspend" can be defined
> + to enable console messages during suspend. Typically, "no_console_suspend" and
> + "default" states can refer to the same pin configuration.
no_console_suspend is a linux thing and doesn't belong in DT.
Rob
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox