On Mon, Oct 30, 2023 at 04:43:28PM +0100, Ilario Gelmetti wrote:
> So, the final DTS file looks like this:
>
> ```
> /dts-v1/;
> /plugin/;
>
> / {
> compatible = "allwinner,sun50i-a64",
> "olimex,a64-olinuxino";
> description = "Enable 1-Wire port";
>
>
On Sun, Feb 05, 2023 at 09:50:22PM +0200, Oleg Verych wrote:
> Hello!
>
> On 1/17/23, Oleg Verych wrote:
> > Update wiki page link to the Allwinner sunXi SoC Clock Control Module.
> >
> > Signed-off-by: Oleg Verych
> > ---
> > Hi!
> >
> > Can I ask additional question to those in the file?
>
>
On Fri, May 27, 2022 at 10:08:16AM -0700, Oranż Metylowy wrote:
> Yes, it doesn't work, at least for me. I tried it a million times.
If you're using an A20, this is likely to be due to:
https://lore.kernel.org/u-boot/20210624120540.7oyhdmerjndsylbq@gilmour/
However, I must emphathize that
On Mon, Jan 17, 2022 at 09:12:37PM +0530, Jagan Teki wrote:
> On Mon, Dec 13, 2021 at 10:32 PM Maxime Ripard wrote:
> >
> > On Fri, Dec 10, 2021 at 04:47:06PM +0530, Jagan Teki wrote:
> > > Existing host driver will keep looking for DRM pointer in
> > >
Hi,
On Tue, Jan 11, 2022 at 09:08:23PM +0100, Philip Rinn wrote:
> Enable the audio hardware on the Olimex A64-OLinuXino board family.
> Tested on the A64-OLinuXino-2Ge8G-IND variant.
>
> Signed-off-by: Philip Rinn
>
> ---
>
>
> Changes in v2: added missing {...} part
> Changes in v3:
On Fri, Dec 10, 2021 at 04:47:08PM +0530, Jagan Teki wrote:
> Some display panels would come up with a non-DSI output, those
> can have an option to connect the DSI host by means of interface
> bridge converter.
>
> This DSI to non-DSI interface bridge converter would require
> DSI Host to handle
On Fri, Dec 10, 2021 at 04:47:07PM +0530, Jagan Teki wrote:
> Having component_add for running all drm bind callbacks returns
> error or unbound due to chain of DSI devices connected across
> bridge topology on a display pipeline.
I'm not sure what that means?
> In a typical bridge oriented
On Fri, Dec 10, 2021 at 04:47:06PM +0530, Jagan Teki wrote:
> Existing host driver will keep looking for DRM pointer in
> sun6i_dsi_attach and defers even if the particular DSI device
> is found for the first time. Meanwhile it triggers the bind
> callback and gets the DRM pointer and then
Hi,
On Fri, Dec 10, 2021 at 04:47:05PM +0530, Jagan Teki wrote:
> This series add bridge support for Allwinner DSI controller.
>
> In addition to previous version, this series add bridge support
> only not doing any bridge conversion at the moment.
>
> Previous version changes [1].
>
> Patch
On Thu, Nov 25, 2021 at 09:44:14PM +0530, Jagan Teki wrote:
> On Thu, Nov 25, 2021 at 9:40 PM Maxime Ripard wrote:
> >
> > On Thu, Nov 25, 2021 at 07:55:41PM +0530, Jagan Teki wrote:
> > > Hi,
> > >
> > > On Thu, Nov 25, 2021 at 7:45 PM Maxime Ripard w
On Thu, Nov 25, 2021 at 07:55:41PM +0530, Jagan Teki wrote:
> Hi,
>
> On Thu, Nov 25, 2021 at 7:45 PM Maxime Ripard wrote:
> >
> > On Wed, Nov 24, 2021 at 12:02:47AM +0530, Jagan Teki wrote:
> > > > > > > > + dsi->panel = of_drm_find_panel(remo
On Wed, Nov 24, 2021 at 12:02:47AM +0530, Jagan Teki wrote:
> > > > > > + dsi->panel = of_drm_find_panel(remote);
> > > > > > + if (IS_ERR(dsi->panel)) {
> > > > > > + dsi->panel = NULL;
> > > > > > +
> > > > > > + dsi->next_bridge = of_drm_find_bridge(remote);
> >
On Mon, Nov 22, 2021 at 08:01:47PM +0530, Jagan Teki wrote:
> On Mon, Nov 22, 2021 at 7:39 PM Maxime Ripard wrote:
> >
> > On Mon, Nov 22, 2021 at 07:21:57PM +0530, Jagan Teki wrote:
> > > > It's perfectly valid to dereference the pointer in atomic_enable, and
>
On Mon, Nov 22, 2021 at 07:49:26PM +0530, Jagan Teki wrote:
> On Mon, Nov 22, 2021 at 7:35 PM Maxime Ripard wrote:
> > On Mon, Nov 22, 2021 at 07:18:13PM +0530, Jagan Teki wrote:
> > > On Mon, Nov 22, 2021 at 3:37 PM Maxime Ripard wrote:
> > > >
> > > >
On Mon, Nov 22, 2021 at 07:21:57PM +0530, Jagan Teki wrote:
> > It's perfectly valid to dereference the pointer in atomic_enable, and
> > that patch would consume memory for no particular reason.
>
> Again, I'm not pointing any mistake in dereference and certainly not
> understand about what
On Mon, Nov 22, 2021 at 07:18:13PM +0530, Jagan Teki wrote:
> Hi Maxime,
>
> On Mon, Nov 22, 2021 at 3:37 PM Maxime Ripard wrote:
> >
> > On Mon, Nov 22, 2021 at 12:22:19PM +0530, Jagan Teki wrote:
> > > Some display panels would come up with a non-DSI output,
On Mon, Nov 22, 2021 at 06:35:58PM +0530, Jagan Teki wrote:
> On Mon, Nov 22, 2021 at 3:38 PM Maxime Ripard wrote:
> >
> > On Mon, Nov 22, 2021 at 12:22:20PM +0530, Jagan Teki wrote:
> > > Get the display mode settings via mode_set bridge function
> > > i
On Mon, Nov 22, 2021 at 12:22:20PM +0530, Jagan Teki wrote:
> Get the display mode settings via mode_set bridge function
> instead of explicitly de-reference.
What's wrong with dereferencing the mode?
Maxime
--
You received this message because you are subscribed to the Google Groups
On Mon, Nov 22, 2021 at 12:22:19PM +0530, Jagan Teki wrote:
> Some display panels would come up with a non-DSI output, those
> can have an option to connect the DSI host by means of interface
> bridge converter.
>
> This DSI to non-DSI interface bridge converter would requires
> DSI Host to
On Wed, 1 Sep 2021 11:18:25 +0200, Maxime Ripard wrote:
> The R40 MBUS compatible was introduced recently but it was never
> documented.
>
>
Applied to sunxi/linux.git (sunxi/dt-for-5.16).
Thanks!
Maxime
--
You received this message because you are subscribed to the Google Gr
On Mon, Sep 06, 2021 at 10:02:26AM +0100, Lee Jones wrote:
> On Fri, 03 Sep 2021, Rob Herring wrote:
>
> > On Wed, 01 Sep 2021 11:18:29 +0200, Maxime Ripard wrote:
> > > The X-Powers AXP PMICs are supported by Linux thanks to its device tree
> > > binding.
> &
On Sun, Sep 05, 2021 at 11:24:48PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:52 CEST je Maxime Ripard napisal(a):
> > Neither the binding nor the driver make any use of the wakeup-source
> > property for the AXP803. Remove it.
> >
> > S
On Sun, Sep 05, 2021 at 11:14:34PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:51 CEST je Maxime Ripard napisal(a):
> > The anx6345 bridge mandates that the input port is named port@0. Since
> > we have a unit-address, this implies that we need
On Sun, Sep 05, 2021 at 11:14:08PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:50 CEST je Maxime Ripard napisal(a):
> > The fixed regulator clock name has a unit address, but no reg property,
> > which generates a warning in DTC. Change its name to rem
On Sun, Sep 05, 2021 at 11:13:46PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:49 CEST je Maxime Ripard napisal(a):
> > The thermal zones one the A100 are called $device-thermal-zone.
> >
> > However, the thermal zone binding explicitly requires that
On Sun, Sep 05, 2021 at 11:13:25PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:48 CEST je Maxime Ripard napisal(a):
> > While it doesn't really matter from a functional point of view in this
> > driver's case, it's usually a good practice to
On Sun, Sep 05, 2021 at 11:12:27PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:46 CEST je Maxime Ripard napisal(a):
> > The dumb-vga-dac and adi,adv7123 compatibles are not supposed to be used
> > together according to the binding.
> >
> &
On Sun, Sep 05, 2021 at 11:11:58PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:45 CEST je Maxime Ripard napisal(a):
> > The edt,edt-ft5x06 compatible has never been a valid compatible
> > according to the binding. Let's change for one that is.
>
On Sun, Sep 05, 2021 at 11:06:45PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:43 CEST je Maxime Ripard napisal(a):
> > According to the SPI NOR bindings, the flash node names are supposed to
> > be flash@. Let's fix our users to use that new scheme.
>
On Sun, Sep 05, 2021 at 11:05:58PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:42 CEST je Maxime Ripard napisal(a):
> > The operating-points-v2 nodes are named inconsistently, but mostly
> > either opp_table0 or gpu-opp-table. However, the underscore is
On Sun, Sep 05, 2021 at 11:04:59PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:41 CEST je Maxime Ripard napisal(a):
> > Even though it translates to the same thing down to the binary level, we
> > should have an array of 2 number cells to describe
On Sun, Sep 05, 2021 at 11:03:11PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:40 CEST je Maxime Ripard napisal(a):
> > We've had a pinctrl node name convention for a while now, let's follow
> > it for the AXP pinctrl nodes as well.
> >
> > S
On Sun, Sep 05, 2021 at 11:02:44PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:39 CEST je Maxime Ripard napisal(a):
> > The name of our PMIC power supply names conflict with the generic
> > regulator supply check that matches anything called *-su
On Sun, Sep 05, 2021 at 11:01:17PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:35 CEST je Maxime Ripard napisal(a):
> > Even though we've used the A80 PRCM driver for some time and a number of
> > boards using it already, we never had a binding fo
On Sun, Sep 05, 2021 at 11:00:25PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:34 CEST je Maxime Ripard napisal(a):
> > Even though we've used the CPU configuration driver for some time and a
> > number of boards using it already, we never had a bindin
On Sun, Sep 05, 2021 at 10:50:32PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:09 CEST je Maxime Ripard napisal(a):
> > Even though both the driver and the device trees all use the
> > allwinner,sun50i-h6-de3-clk, we documented the compatible as
> >
Hi Mark,
On Wed, Sep 01, 2021 at 03:39:50PM +0100, Mark Brown wrote:
> On Wed, Sep 01, 2021 at 11:18:01AM +0200, Maxime Ripard wrote:
> > Even though we had the wm8978 driver for some time and a number of
> > boards using it already, we never had a binding for it. Let's add it
&g
Neither the binding nor the driver make any use of the wakeup-source
property for the AXP803. Remove it.
Signed-off-by: Maxime Ripard
---
arch/arm64/boot/dts/allwinner/sun50i-a64-teres-i.dts | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-teres-i.dts
The anx6345 bridge mandates that the input port is named port@0. Since
we have a unit-address, this implies that we need a reg property with
the same value, but it was found to be missing in the Teres-I device
tree. Make sure it's there.
Signed-off-by: Maxime Ripard
---
arch/arm64/boot/dts
The fixed regulator clock name has a unit address, but no reg property,
which generates a warning in DTC. Change its name to remove its useless
unit address.
Signed-off-by: Maxime Ripard
---
arch/arm64/boot/dts/allwinner/sun50i-a64-pinetab.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion
-by: Maxime Ripard
---
arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi
b/arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi
index 30d396e8c762..46ed529a4dc2 100644
--- a/arch/arm64/boot/dts
The thermal zones one the A100 are called $device-thermal-zone.
However, the thermal zone binding explicitly requires that zones are
called *-thermal. Let's fix it.
Signed-off-by: Maxime Ripard
---
arch/arm64/boot/dts/allwinner/sun50i-a100.dtsi | 6 +++---
1 file changed, 3 insertions(+), 3
The GPU thermal zone is named gpu_thermal. However, the underscore is
an invalid character for a node name and the thermal zone binding
explicitly requires that zones are called *-thermal. Let's fix it.
Signed-off-by: Maxime Ripard
---
arch/arm64/boot/dts/allwinner/sun50i-h5.dtsi | 2 +-
1 file
The dumb-vga-dac and adi,adv7123 compatibles are not supposed to be used
together according to the binding.
Since the corpro gm7123 is a drop-in replacement for the adv7123, let's
remove dumb-vga-dac from our compatible list.
Reviewed-by: Chen-Yu Tsai
Signed-off-by: Maxime Ripard
---
arch/arm
The edt,edt-ft5x06 compatible has never been a valid compatible
according to the binding. Let's change for one that is.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun8i-a83t-tbs-a711.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/sun8i-a83t-tbs
The crypto engine binding doesn't allow for any DMA property, yet the
v3s define some. Remove them.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun8i-v3s.dtsi | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm/boot/dts/sun8i-v3s.dtsi b/arch/arm/boot/dts/sun8i-v3s.dtsi
index
The operating-points-v2 nodes are named inconsistently, but mostly
either opp_table0 or gpu-opp-table. However, the underscore is an
invalid character for a node name and the thermal zone binding
explicitly requires that zones are called opp-table-*. Let's fix it.
Signed-off-by: Maxime Ripard
According to the SPI NOR bindings, the flash node names are supposed to
be flash@. Let's fix our users to use that new scheme.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun8i-v3-sl631.dtsi | 2 +-
arch/arm/boot/dts/sunxi-libretech-all-h3-it.dtsi | 2
Even though it translates to the same thing down to the binary level, we
should have an array of 2 number cells to describe each OPP, which in
turns create a validation warning.
Let's fix this.
Signed-off-by: Maxime Ripard
---
.../arm/boot/dts/sun4i-a10-olinuxino-lime.dts | 11 +++--
arch/arm
We've had a pinctrl node name convention for a while now, let's follow
it for the AXP pinctrl nodes as well.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/axp81x.dtsi | 4 ++--
arch/arm64/boot/dts/allwinner/axp803.dtsi | 4 ++--
2 files changed, 4 insertions(+), 4 deletions
Bitbanged 1-Wire buses are supported by Linux thanks to their device
tree binding.
Now that we have the DT validation in place, let's convert the device
tree bindings for that driver over to a YAML schema.
Cc: Daniel Mack
Cc: Evgeniy Polyakov
Signed-off-by: Maxime Ripard
---
Changes from v1
-by: Maxime Ripard
---
arch/arm/boot/dts/axp209.dtsi | 6 +++---
arch/arm/boot/dts/axp22x.dtsi | 6 +++---
arch/arm/boot/dts/axp81x.dtsi | 6 +++---
arch/arm64/boot/dts/allwinner/axp803.dtsi | 6 +++---
4 files changed, 12 insertions(+), 12 deletions(-)
diff
-...@vger.kernel.org
Signed-off-by: Maxime Ripard
---
Documentation/devicetree/bindings/usb/snps,dwc3.yaml | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/devicetree/bindings/usb/snps,dwc3.yaml
b/Documentation/devicetree/bindings/usb/snps,dwc3.yaml
index 078fb7889593
-off-by: Maxime Ripard
---
Changes from v1:
- Added maximum number of items for clocks and gpios
- Fixed the example node name
---
.../devicetree/bindings/usb/smsc,usb3503.yaml | 108 ++
.../devicetree/bindings/usb/usb3503.txt | 39 ---
2 files changed, 108 insertions
Even though we've used the CPU configuration driver for some time and a
number of boards using it already, we never had a binding for it. Let's
add it based on what the driver expects and the boards are providing.
Reviewed-by: Rob Herring
Signed-off-by: Maxime Ripard
---
.../sunxi/allwinner
Even though we've used the A80 PRCM driver for some time and a number of
boards using it already, we never had a binding for it. Let's add it
based on what the driver expects and the boards are providing.
Reviewed-by: Rob Herring
Signed-off-by: Maxime Ripard
---
.../arm/sunxi/allwinner,sun9i
: Ondrej Jirman
Reviewed-by: Rob Herring
Signed-off-by: Maxime Ripard
---
.../bindings/regulator/silergy,sy8106a.yaml | 52 +++
.../bindings/regulator/sy8106a-regulator.txt | 23
2 files changed, 52 insertions(+), 23 deletions(-)
create mode 100644
Documentation
b Kicinski
Cc: Kalle Valo
Cc: linux-wirel...@vger.kernel.org
Cc: net...@vger.kernel.org
Reviewed-by: Rob Herring
Signed-off-by: Maxime Ripard
---
.../bindings/net/wireless/esp,esp8089.txt | 30 -
.../bindings/net/wireless/esp,esp8089.yaml| 43 +++
2 files c
Abreu
Cc: net...@vger.kernel.org
Reviewed-by: Rob Herring
Signed-off-by: Maxime Ripard
---
.../devicetree/bindings/net/allwinner,sun8i-a83t-emac.yaml | 4 ++--
Documentation/devicetree/bindings/net/snps,dwmac.yaml | 6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
though they are not generic and do not apply to any
device, so we took the occasion to fix this.
Cc: linux-...@vger.kernel.org
Cc: Ulf Hansson
Signed-off-by: Maxime Ripard
---
Changes from v1:
- Fixed additionalProperties
---
.../devicetree/bindings/mmc/mmc-card.txt | 30
The X-Powers AXP PMICs are supported by Linux thanks to its device tree
binding.
Now that we have the DT validation in place, let's convert the device
tree bindings for that driver over to a YAML schema.
Cc: Chen-Yu Tsai
Cc: Lee Jones
Signed-off-by: Maxime Ripard
---
Changes from v1
The X-Powers AC100 hybrid devices are supported by Linux thanks to its
device tree binding.
Now that we have the DT validation in place, let's convert the device
tree bindings for that driver over to a YAML schema.
Cc: Lee Jones
Acked-by: Chen-Yu Tsai
Signed-off-by: Maxime Ripard
-by: Maxime Ripard
---
.../devicetree/bindings/media/i2c/ov5640.txt | 92 ---
.../bindings/media/i2c/ovti,ov5640.yaml | 154 ++
2 files changed, 154 insertions(+), 92 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/media/i2c/ov5640.txt
create mode
The OV5640 sensor used in the example doesn't follow the binding and
omits the regulators. Add some to make the example valid.
Signed-off-by: Maxime Ripard
---
Documentation/devicetree/bindings/media/ti,cal.yaml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
The R40 MBUS compatible was introduced recently but it was never
documented.
Reviewed-by: Rob Herring
Signed-off-by: Maxime Ripard
---
.../devicetree/bindings/arm/sunxi/allwinner,sun4i-a10-mbus.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git
a/Documentation/devicetree/bindings/arm
Signed-off-by: Maxime Ripard
---
Changes from v1:
- Reduced the maximum number of io-channels, and added a comment for
the limitation
---
.../devicetree/bindings/hwmon/iio-hwmon.yaml | 37 +++
1 file changed, 37 insertions(+)
create mode 100644 Documentation/devicetree
The Silead GSL1680 Touchscreen Controller is supported by Linux thanks
to its device tree binding.
Now that we have the DT validation in place, let's convert the device
tree bindings for that driver over to a YAML schema.
Cc: Dmitry Torokhov
Cc: linux-in...@vger.kernel.org
Signed-off-by: Maxime
: linux-g...@vger.kernel.org
Signed-off-by: Maxime Ripard
---
Changes from v1:
- Removed the example and moved it in the mfd schema
---
.../devicetree/bindings/gpio/gpio-axp209.txt | 75 ---
.../bindings/gpio/x-powers,axp209-gpio.yaml | 55 ++
2 files changed, 55
The UBlox Neo 6M is supported by Linux thanks to its device tree
binding.
Now that we have the DT validation in place, let's convert the device
tree bindings for that driver over to a YAML schema.
Cc: Johan Hovold
Signed-off-by: Maxime Ripard
---
Changes from v1:
- Fixed a typo
- Fixed
A few panel-lvds compatibles were never documented. Let's add them.
Cc: dri-de...@lists.freedesktop.org
Cc: Laurent Pinchart
Cc: Sam Ravnborg
Cc: Thierry Reding
Signed-off-by: Maxime Ripard
---
Documentation/devicetree/bindings/display/panel/lvds.yaml | 2 ++
1 file changed, 2 insertions
: Laurent Pinchart
Cc: Sam Ravnborg
Cc: Thierry Reding
Signed-off-by: Maxime Ripard
---
.../bindings/display/panel/lvds.yaml | 2 +
.../display/panel/sgd,gktw70sdae4se.yaml | 68 ---
2 files changed, 2 insertions(+), 68 deletions(-)
delete mode 100644
Documentation
Ravnborg
Cc: Thierry Reding
Signed-off-by: Maxime Ripard
---
.../bindings/display/panel/lvds.yaml | 5 +-
.../display/panel/mitsubishi,aa121td01.yaml | 69 ---
2 files changed, 4 insertions(+), 70 deletions(-)
delete mode 100644
Documentation/devicetree/bindings
The Mitsubishi AA121TD01 Device Tree Binding was requiring a
data-mapping property value which was set to another value in the
existing Device Trees. Fix this.
Cc: dri-de...@lists.freedesktop.org
Cc: Laurent Pinchart
Cc: Sam Ravnborg
Cc: Thierry Reding
Signed-off-by: Maxime Ripard
: Laurent Pinchart
Cc: Sam Ravnborg
Cc: Thierry Reding
Signed-off-by: Maxime Ripard
---
.../bindings/display/panel/mitsubishi,aa121td01.yaml | 5 -
1 file changed, 5 deletions(-)
diff --git
a/Documentation/devicetree/bindings/display/panel/mitsubishi,aa121td01.yaml
b/Documentation
Ravnborg
Cc: Thierry Reding
Signed-off-by: Maxime Ripard
---
.../bindings/display/panel/lvds.yaml | 12
.../display/panel/mitsubishi,aa104xd12.yaml | 70 ---
2 files changed, 12 insertions(+), 70 deletions(-)
delete mode 100644
Documentation/devicetree/bindings
The Mitsubishi AA140XD12 Device Tree Binding was requiring a
data-mapping property value which was set to another value in the
existing Device Trees. Fix this.
Cc: dri-de...@lists.freedesktop.org
Cc: Laurent Pinchart
Cc: Sam Ravnborg
Cc: Thierry Reding
Signed-off-by: Maxime Ripard
: Laurent Pinchart
Cc: Sam Ravnborg
Cc: Thierry Reding
Signed-off-by: Maxime Ripard
---
.../bindings/display/panel/mitsubishi,aa104xd12.yaml | 5 -
1 file changed, 5 deletions(-)
diff --git
a/Documentation/devicetree/bindings/display/panel/mitsubishi,aa104xd12.yaml
b/Documentation
-by: Maxime Ripard
---
.../display/panel/innolux,ee101ia-01d.yaml| 31 ---
.../bindings/display/panel/lvds.yaml | 1 +
2 files changed, 1 insertion(+), 31 deletions(-)
delete mode 100644
Documentation/devicetree/bindings/display/panel/innolux,ee101ia-01d.yaml
diff --git
the data-mapping
requirement to a conditional.
Let's move it to the generic panel-lvds binding
Cc: dri-de...@lists.freedesktop.org
Cc: Laurent Pinchart
Cc: Sam Ravnborg
Cc: Thierry Reding
Signed-off-by: Maxime Ripard
---
.../display/panel/advantech,idk-2121wr.yaml | 121
Ravnborg
Cc: Thierry Reding
Signed-off-by: Maxime Ripard
---
.../display/panel/advantech,idk-1110wr.yaml | 69 ---
.../bindings/display/panel/lvds.yaml | 22 --
2 files changed, 15 insertions(+), 76 deletions(-)
delete mode 100644
Documentation/devicetree
Even though both the driver and the device trees all use the
allwinner,sun50i-h6-de3-clk, we documented the compatible as
allwinner,sun50i-h6-de2-clk in the binding. Let's fix this.
Reviewed-by: Rob Herring
Signed-off-by: Maxime Ripard
---
.../devicetree/bindings/clock/allwinner,sun8i-a83t-de2
due to the way the bus bindings have been
described. Let's add max-speed to remove the warning.
Cc: Alistair Francis
Cc: "David S. Miller"
Cc: Jakub Kicinski
Cc: net...@vger.kernel.org
Cc: Vasily Khoruzhick
Reviewed-by: Alistair Francis
Reviewed-by: Rob Herring
Signed-off-by: Max
: Linus Walleij
Cc: net...@vger.kernel.org
Reviewed-by: Rob Herring
Signed-off-by: Maxime Ripard
---
.../bindings/net/broadcom-bluetooth.yaml| 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/net/broadcom-bluetooth.yaml
b/
The ARM CCI-400 Interconnect is supported by Linux thanks to its device
tree binding.
Now that we have the DT validation in place, let's convert the device
tree bindings for that driver over to a YAML schema.
Cc: Lorenzo Pieralisi
Signed-off-by: Maxime Ripard
---
Changes from v1:
- Reduced
The Reserved Memory mechanism is supported by Linux thanks to its device
tree binding.
Now that we have the DT validation in place, let's convert the device
tree bindings for that driver over to a YAML schema.
Cc: Mailing List
Signed-off-by: Maxime Ripard
---
Changes from v1:
- Fixed
Reviewed-by: Rob Herring
Signed-off-by: Maxime Ripard
---
.../bindings/sound/simple-amplifier.txt | 17 ---
.../sound/simple-audio-amplifier.yaml | 45 +++
2 files changed, 45 insertions(+), 17 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/sound
Herring
Signed-off-by: Maxime Ripard
---
.../bindings/sound/linux,spdif-dit.yaml | 32 +++
.../bindings/sound/spdif-transmitter.txt | 10 --
2 files changed, 32 insertions(+), 10 deletions(-)
create mode 100644 Documentation/devicetree/bindings/sound/linux,spdif
Brown
Cc: Samuel Holland
Signed-off-by: Maxime Ripard
---
Changes from v1:
- Accept either a 0 or 1 #sound-dai-cells
---
.../devicetree/bindings/sound/bt-sco.txt | 13 ---
.../bindings/sound/linux,bt-sco.yaml | 38 +++
2 files changed, 38 insertions(+), 13
Cc: patc...@opensource.cirrus.com
Reviewed-by: Rob Herring
Signed-off-by: Maxime Ripard
---
Changes from v1:
- Changed the maintainers of the bindings
---
.../devicetree/bindings/sound/wlf,wm8978.yaml | 58 +++
1 file changed, 58 insertions(+)
create mode 100644 Documentation
, and
since that means we have all our devices properly validated I don't expect more
fixes now, aside from the usual bunch of regressions.
Let me know what you think,
Maxime
Maxime Ripard (52):
ASoC: dt-bindings: Add WM8978 Binding
ASoC: dt-bindings: Convert Bluetooth SCO Link binding
, and
since that means we have all our devices properly validated I don't expect more
fixes now, aside from the usual bunch of regressions.
Let me know what you think,
Maxime
Maxime Ripard (52):
ASoC: dt-bindings: Add WM8978 Binding
ASoC: dt-bindings: Convert Bluetooth SCO Link binding
, and
since that means we have all our devices properly validated I don't expect more
fixes now, aside from the usual bunch of regressions.
Let me know what you think,
Maxime
Maxime Ripard (52):
ASoC: dt-bindings: Add WM8978 Binding
ASoC: dt-bindings: Convert Bluetooth SCO Link binding
On Wed, Aug 18, 2021 at 10:04:07AM +0100, Andre Przywara wrote:
> On Tue, 17 Aug 2021 09:38:10 +0200
> Maxime Ripard wrote:
>
> Hi Maxime,
>
> > On Mon, Aug 02, 2021 at 01:39:38AM +0100, Andre Przywara wrote:
> > > On Mon, 26 Jul 2021 16:41:37 +0
Hi,
On Wed, Aug 18, 2021 at 08:48:46AM -0500, Rob Herring wrote:
> On Wed, Aug 18, 2021 at 7:43 AM Maxime Ripard wrote:
> >
> > Hi Rob, Sam,
> >
> > On Wed, Jul 21, 2021 at 08:29:47PM -0600, Rob Herring wrote:
> > > On Wed, Jul 21, 2021 at 0
Salut Alex,
On Tue, Aug 17, 2021 at 10:13:11AM +0200, Alexandre Belloni wrote:
> On 17/08/2021 09:38:10+0200, Maxime Ripard wrote:
> > > > It's not entirely clear to me what those clocks are about though. If we
> > > > look at the clock output in the user manual,
Hi Rob, Sam,
On Wed, Jul 21, 2021 at 08:29:47PM -0600, Rob Herring wrote:
> On Wed, Jul 21, 2021 at 04:03:40PM +0200, Maxime Ripard wrote:
> > The binding mentions that all the drivers using that driver must use a
> > vendor-specific compatible but never enforces it, nor documents
Hi Rob,
On Wed, Jul 21, 2021 at 08:30:43AM -0600, Rob Herring wrote:
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/reserved-memory/reserved-memory.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: /reserved-memory Node
> > +
> > +maintainers:
>
Hi Kalle,
On Fri, Aug 06, 2021 at 08:47:09AM +, Kalle Valo wrote:
> Maxime Ripard wrote:
>
> > The ESP8089 Wireless Chip is supported by Linux (through an out-of-tree
> > driver) thanks to its device tree binding.
> >
> > Now that we have the DT vali
On Mon, Aug 02, 2021 at 01:39:43AM +0100, Andre Przywara wrote:
> Add the obvious compatible name to the existing RTC binding.
> The actual RTC part of the device uses a different day/month/year
> storage scheme, so it's not compatible with the previous devices.
> Also the clock part is quite
Hi,
On Mon, Aug 02, 2021 at 01:39:38AM +0100, Andre Przywara wrote:
> On Mon, 26 Jul 2021 16:41:37 +0200
> Maxime Ripard wrote:
>
> > Hi,
> >
> > On Fri, Jul 23, 2021 at 04:38:29PM +0100, Andre Przywara wrote:
> > > Add the obvious compatible name to the ex
1 - 100 of 4280 matches
Mail list logo
