Re: [linux-sunxi] [PATCH v2 14/14] ARM: dts: sun8i: Enable DVFS on Orange Pi One

Hello, On 25 June 2016 at 05:45, wrote: > From: Ondrej Jirman > > Use Xulong Orange Pi One GPIO based regulator for > passive cooling and thermal management. > > Signed-off-by: Ondrej Jirman > --- >

Re: [linux-sunxi] Re: [PATCH 06/14] ARM: dts: sun8i: Add cpu0 label to sun8i-h3.dtsi

Hello, On 29 June 2016 at 23:11, Ondřej Jirman wrote: > On 29.6.2016 22:45, Maxime Ripard wrote: >> Hi, >> >> On Sat, Jun 25, 2016 at 04:50:24PM +0200, Ondřej Jirman wrote: >>> On 25.6.2016 09:02, Maxime Ripard wrote: On Sat, Jun 25, 2016 at 09:02:48AM +0800, Chen-Yu Tsai

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

On Thursday, June 30, 2016 12:25:15 PM CEST Hans de Goede wrote: > > So then how about making use of a more specific compatible string? > > > > e.g. > > > > brcmf { > > compatible = "foo,ap6210", "brcm,bcm4329-fmac"; > > ... > > }; > > > > and if the compatible has more than one

Re: [linux-sunxi] [PATCH v2 14/14] ARM: dts: sun8i: Enable DVFS on Orange Pi One

On Thu, 30 Jun 2016 13:13:48 +0200 Michal Suchanek wrote: > Hello, > > On 25 June 2016 at 05:45, wrote: > > From: Ondrej Jirman > > > > Use Xulong Orange Pi One GPIO based regulator for > > passive cooling and thermal management. > >

[linux-sunxi] Re: USB OTG on Orange Pi PC

Hi, hopefuly, it was the NPE that I fixed. It was specifically in the H3 usb phy code path for phy0. So I believe it was untested, because I didn't find any dts file that would use phy0. Good luck with the audio driver. regards, o. On 30.6.2016 07:17, boob...@gmail.com wrote: > Nice work.

Re: [linux-sunxi] [PATCH v2 14/14] ARM: dts: sun8i: Enable DVFS on Orange Pi One

Hello, On 30.6.2016 13:13, Michal Suchanek wrote: > Hello, > > On 25 June 2016 at 05:45, wrote: >> From: Ondrej Jirman >> >> Use Xulong Orange Pi One GPIO based regulator for >> passive cooling and thermal management. >> >> Signed-off-by: Ondrej Jirman

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Hi, On 29-06-16 20:51, 'Arend Van Spriel' via linux-sunxi wrote: On 29-6-2016 20:01, Hans de Goede wrote: Hi, On 29-06-16 19:00, Kalle Valo wrote: Hans de Goede writes: Hi, On 29-06-16 16:42, Jonas Gorski wrote: Hi, On 29 June 2016 at 16:04, Hans de Goede

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Hi, On 30-06-16 11:58, Kalle Valo wrote: Hans de Goede writes: Hi, On 30-06-16 11:02, Kalle Valo wrote: Priit Laes writes: What is the size of this nvram file? As it's board specific, I wonder if we can simply include it inside of the DT verbatim. I

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Priit Laes writes: >> What is the size of this nvram file? As it's board specific, I wonder >> if we can simply include it inside of the DT verbatim. I remember >> doing that (in the pre-dtb days, on real open firmware) for the >> "spidernet" >> ethernet driver. > > It contains

Re: [linux-sunxi] Re: [PATCH 1/4] ARM: dts: sun5i: Enable otg on the auxtex t004

Hi, On 29-06-16 22:38, Maxime Ripard wrote: Hi, On Wed, Jun 29, 2016 at 08:46:59PM +0200, Hans de Goede wrote: The auxtek t004 has its otg usb vbus hardwired to 5v (likely in case people use it to power the board instead of the dedicated power micro usb connector), it does have an id pin, so

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Hi, On 30-06-16 12:18, Jonas Gorski wrote: Hi, On 30 June 2016 at 12:04, Hans de Goede wrote: Hi, On 30-06-16 11:58, Kalle Valo wrote: Hans de Goede writes: Hi, On 30-06-16 11:02, Kalle Valo wrote: Priit Laes writes:

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Arend Van Spriel writes: >>> Typical wifi devices will have some sort of non volatile storage >>> on board to not only store the ethernet(mac) address, but also >>> to contain e.g. info about the antenna gain so that the firmware >>> and/or the driver can take the

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Hi Kalle, On 30 Jun 2016 6:46 p.m., "Kalle Valo" wrote: > > Arend Van Spriel writes: > > >> Since we are dealing with a per-board config-file here, which is > >> loaded from the os filesystem we really need to specify a basename > >> here as

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Hi, On 30-06-16 10:46, Kalle Valo wrote: Arend Van Spriel writes: Since we are dealing with a per-board config-file here, which is loaded from the os filesystem we really need to specify a basename here as the list of possible boards is endless, so we cannot

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Hi, On 30-06-16 11:02, Kalle Valo wrote: Priit Laes writes: What is the size of this nvram file? As it's board specific, I wonder if we can simply include it inside of the DT verbatim. I remember doing that (in the pre-dtb days, on real open firmware) for the "spidernet"

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Hi, On 30 June 2016 at 12:04, Hans de Goede wrote: > Hi, > > > On 30-06-16 11:58, Kalle Valo wrote: >> >> Hans de Goede writes: >> >>> Hi, >>> >>> On 30-06-16 11:02, Kalle Valo wrote: Priit Laes writes: >> What is

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Hans de Goede writes: > Hi, > > On 30-06-16 11:02, Kalle Valo wrote: >> Priit Laes writes: >> What is the size of this nvram file? As it's board specific, I wonder if we can simply include it inside of the DT verbatim. I remember doing that

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Arend Van Spriel writes: >> Since we are dealing with a per-board config-file here, which is >> loaded from the os filesystem we really need to specify a basename >> here as the list of possible boards is endless, so we cannot >> have a lookup table in the driver. >

Re: [linux-sunxi] [PATCH v2 14/14] ARM: dts: sun8i: Enable DVFS on Orange Pi One

On 30 June 2016 at 16:19, Ondřej Jirman wrote: > Hello, > > On 30.6.2016 13:13, Michal Suchanek wrote: >> Hello, >> >> On 25 June 2016 at 05:45, wrote: >>> From: Ondrej Jirman >>> >>> Use Xulong Orange Pi One GPIO based regulator for >>>

Re: [linux-sunxi] [PATCH v2 14/14] ARM: dts: sun8i: Enable DVFS on Orange Pi One

On 30.6.2016 17:50, Michal Suchanek wrote: > On 30 June 2016 at 17:16, Michal Suchanek wrote: >> On 30 June 2016 at 16:19, Ondřej Jirman wrote: >>> Hello, >>> >>> On 30.6.2016 13:13, Michal Suchanek wrote: Hello, On 25 June 2016 at 05:45,

Re: [linux-sunxi] [PATCH v2 14/14] ARM: dts: sun8i: Enable DVFS on Orange Pi One

On 30 June 2016 at 17:16, Michal Suchanek wrote: > On 30 June 2016 at 16:19, Ondřej Jirman wrote: >> Hello, >> >> On 30.6.2016 13:13, Michal Suchanek wrote: >>> Hello, >>> >>> On 25 June 2016 at 05:45, wrote: From: Ondrej Jirman

Re: [linux-sunxi] [PATCH v2 14/14] ARM: dts: sun8i: Enable DVFS on Orange Pi One

On 30.6.2016 17:16, Michal Suchanek wrote: > On 30 June 2016 at 16:19, Ondřej Jirman wrote: >> Hello, >> >> On 30.6.2016 13:13, Michal Suchanek wrote: >>> Hello, >>> >>> On 25 June 2016 at 05:45, wrote: From: Ondrej Jirman

Re: [linux-sunxi] Re: USB OTG on Orange Pi PC

Hello, On 30 June 2016 at 16:44, Ondřej Jirman wrote: > Hi, > > hopefuly, it was the NPE that I fixed. It was specifically in the H3 usb > phy code path for phy0. So I believe it was untested, > because I didn't find any dts file that would use phy0. > This WorksForMe(TM). I can

Re: [linux-sunxi] Re: USB OTG on Orange Pi PC

On 30 June 2016 at 20:06, Michal Suchanek wrote: > Hello, > > On 30 June 2016 at 16:44, Ondřej Jirman wrote: >> Hi, >> >> hopefuly, it was the NPE that I fixed. It was specifically in the H3 usb >> phy code path for phy0. So I believe it was untested, >> because

Re: [linux-sunxi] Re: USB OTG on Orange Pi PC

On 30.6.2016 20:21, Michal Suchanek wrote: > On 30 June 2016 at 20:06, Michal Suchanek wrote: >> Hello, >> >> On 30 June 2016 at 16:44, Ondřej Jirman wrote: >>> Hi, >>> >>> hopefuly, it was the NPE that I fixed. It was specifically in the H3 usb >>> phy code path

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

On 30-6-2016 13:31, Arnd Bergmann wrote: > On Thursday, June 30, 2016 12:25:15 PM CEST Hans de Goede wrote: >>> So then how about making use of a more specific compatible string? >>> >>> e.g. >>> >>> brcmf { >>> compatible = "foo,ap6210", "brcm,bcm4329-fmac"; >>> ... >>> }; >>>

[linux-sunxi] Re: [PATCH v2 06/14] ARM: sun8i: clk: Add clk-factor rate application method

Hi, On Sat, Jun 25, 2016 at 05:45:03AM +0200, meg...@megous.com wrote: > From: Ondrej Jirman > > PLL1 on H3 requires special factors application algorithm, > when the rate is changed. This algorithm was extracted > from the arisc code that handles frequency scaling > in the

Re: [linux-sunxi] Re: [PATCH 06/14] ARM: dts: sun8i: Add cpu0 label to sun8i-h3.dtsi

On Thu, Jun 30, 2016 at 01:04:40PM +0200, Michal Suchanek wrote: > > You're probably right. Operating points should be part of h3.dtsi, and > > if some board is particularly bad, and can't handle being above certain > > frequency safely, due to thermal design issues, we can override > > operating

[linux-sunxi] Re: [PATCH 1/3] clk: sunxi: Add a driver for the CCU

On Wed, Jun 29, 2016 at 10:12:56AM +0200, Jean-Francois Moine wrote: > On Tue, 28 Jun 2016 22:45:02 +0200 > Maxime Ripard wrote: > > > On Tue, Jun 28, 2016 at 05:37:35PM +0200, Jean-Francois Moine wrote: > > > +/* --- prepare / enable --- */ > > > +int

Re: [linux-sunxi] Re: [PATCH] mmc: pwrseq-simple: Add an optional post-power-on-delay

Hi All, On Fri, Jul 1, 2016 at 10:47 AM, Rob Herring wrote: > On Thu, Jun 23, 2016 at 11:33:27AM +0200, Hans de Goede wrote: >> Hi, >> >> On 23-06-16 00:25, Rob Herring wrote: >> >On Wed, Jun 22, 2016 at 12:59 PM, Hans de Goede wrote: >> >>Some devices need

[linux-sunxi] Re: [PATCH v2 06/14] ARM: sun8i: clk: Add clk-factor rate application method

On 30.6.2016 22:40, Maxime Ripard wrote: > Hi, > > On Sat, Jun 25, 2016 at 05:45:03AM +0200, meg...@megous.com wrote: >> From: Ondrej Jirman >> >> PLL1 on H3 requires special factors application algorithm, >> when the rate is changed. This algorithm was extracted >> from the

Re: [linux-sunxi] Re: [PATCH] mmc: pwrseq-simple: Add an optional post-power-on-delay

On Thu, Jun 23, 2016 at 11:33:27AM +0200, Hans de Goede wrote: > Hi, > > On 23-06-16 00:25, Rob Herring wrote: > >On Wed, Jun 22, 2016 at 12:59 PM, Hans de Goede wrote: > >>Some devices need a while to boot their firmware after providing clks / > >>de-asserting resets before

Re: [linux-sunxi] [PATCH v2 14/14] ARM: dts: sun8i: Enable DVFS on Orange Pi One

On 30.6.2016 16:23, Siarhei Siamashka wrote: > On Thu, 30 Jun 2016 13:13:48 +0200 > Michal Suchanek wrote: > >> Hello, >> >> On 25 June 2016 at 05:45, wrote: >>> From: Ondrej Jirman >>> >>> Use Xulong Orange Pi One GPIO based

[linux-sunxi] Re: [PATCH v2 06/14] ARM: sun8i: clk: Add clk-factor rate application method

Hi, On 30.6.2016 22:40, Maxime Ripard wrote: > Hi, > > On Sat, Jun 25, 2016 at 05:45:03AM +0200, meg...@megous.com wrote: >> From: Ondrej Jirman >> >> PLL1 on H3 requires special factors application algorithm, >> when the rate is changed. This algorithm was extracted >> from

[linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

On Wed, Jun 29, 2016 at 04:04:31PM +0200, Hans de Goede wrote: > Add a brcm,nvram_file_name dt property to allow overruling the default > nvram filename for sdio devices. The idea is that we can specify a > board specific nvram file, e.g. brcmfmac43362-ap6210.txt for boards > with an ap6210 wifi