On Sat, Jul 24, 2021 at 5:54 AM Rob Herring wrote:
>
> On Wed, Jul 21, 2021 at 04:03:53PM +0200, Maxime Ripard wrote:
> > 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
>
On Wed, Jul 21, 2021 at 10:06 PM Maxime Ripard wrote:
>
> 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.
>
>
On Wed, Jul 21, 2021 at 10:05 PM Maxime Ripard wrote:
>
> The AXP803 compatible was introduced recently with a fallback to the
> AXP813, but it was never documented.
>
> Cc: Chen-Yu Tsai
> Cc: linux...@vger.kernel.org
> Cc: Sebastian Reichel
> Signed-off-by: Maxime Ripard
Reviewed-by: Chen-Yu
The H616 RTC changes its day storage to the newly introduced linear day
scheme, so pair the new compatible string with this feature flag.
The clock part is missing an external 32768 Hz oscillator input pin,
for future expansion we must thus ignore any provided clock for now.
Signed-off-by: Andre
This (relatively) new SoC is similar to the H6, but drops the (broken)
PCIe support and the USB 3.0 controller. It also gets the management
controller removed, which in turn removes *some*, but not all of the
devices formerly dedicated to the ARISC (CPUS).
And while there is still the extra sunxi
Signed-off-by: Andre Przywara
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/arm/sunxi.yaml | 10 ++
1 file changed, 10 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/sunxi.yaml
b/Documentation/devicetree/bindings/arm/sunxi.yaml
index
Hi,
some minor update of the basic Allwinner H616 support, still on top
of 5.14-rc1.
The only change is some minor change in the date calculation, as per
Jernej's comment.
The USB support is still separate, to split off the discussion, and
simplify the core SoC support.
For a complete
The AXP305 PMIC used on many boards with the H616 SoC seems to be fully
compatible to the AXP805 PMIC, so add the proper chain of compatible
strings.
Also at least on one board (Orangepi Zero2) there is no interrupt line
connected to the CPU, so make the "interrupts" property optional.
The OrangePi Zero 2 is a development board with the new H616 SoC. It
comes with the following features:
- Four ARM Cortex-A53 cores, Mali-G31 MP2 GPU
- 512MiB/1GiB DDR3 DRAM
- AXP305 PMIC
- Raspberry-Pi-1 compatible GPIO header
- extra 13 pin expansion header, exposing pins for 2x USB
The X96 Mate is an Allwinner H616 based TV box, featuring:
- Four ARM Cortex-A53 cores, Mali-G31 MP2 GPU
- 2GiB/4GiB RAM (fully usable!)
- 16/32/64GiB eMMC
- 100Mbps Ethernet (via embedded AC200 EPHY, not yet supported)
- Unsupported Allwinner WiFi chip
- 2 x USB 2.0 host ports
-
Newer versions of the Allwinner RTC, for instance as found in the H616
SoC, not only store the current day as a linear number, but also change
the way the alarm is handled: There are now two registers, that
explicitly store the wakeup time, in the same format as the current
time.
Add support for
Some newer Allwinner RTCs (for instance the one in the H616 SoC) lack
a pin for an external 32768 Hz oscillator. As a consequence, this LOSC
can't be selected as the RTC clock source, and we must rely on the
internal RC oscillator.
To allow additions of clocks to the RTC node, add a feature bit to
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 different, as there is no external 32K LOSC
oscillator input.
Using "unsigned long" for UNIX timestamps is never a good idea, and
comparing the value of such a variable against U32_MAX does not do
anything useful on 32-bit systems.
Use the proper time64_t type when dealing with timestamps, and avoid
cutting down the time range unnecessarily. This also fixes
Newer versions of the Allwinner RTC, as for instance found in the H616
SoC, no longer store a broken-down day/month/year representation in the
RTC_DAY_REG, but just a linear day number.
The user manual does not give any indication about the expected epoch
time of this day count, but the BSP kernel
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 existing RTC binding.
> > The actual RTC part of the device uses a different day/month/year
> > storage scheme, so it's
On Sun, 25 Jul 2021 08:11:49 +0200
Jernej Škrabec wrote:
Hi Jernej,
> Dne petek, 23. julij 2021 ob 17:38:32 CEST je Andre Przywara napisal(a):
> > Newer versions of the Allwinner RTC, for instance as found in the H616
> > SoC, not only store the current day as a linear number, but also change
>
On Mon, 26 Jul 2021 16:52:30 +0200
Maxime Ripard wrote:
Hi,
> On Fri, Jul 23, 2021 at 04:38:27PM +0100, Andre Przywara wrote:
> > Hi,
> >
> > another try on the basic Allwinner H616 support, now on top of 5.14-rc1.
> >
> > This time I dropped the USB support from the basic series, to split
18 matches
Mail list logo
