Re: v2022.05.0

ср, 18 мая 2022 г. в 16:00, Sascha Hauer : > Hi All, > barebox-2022.05.0 is out. Hello. After updating to the new version, I found errors... This is probably the result of the "gpio: allocate dynamic gpio numbers top down" patch. In the gpiochip_find_base function, it seems to me that we should

Re: [PATCH] clk: fix clk_round_rate() behaviour

Hi, On Mon, 16 May 2022 at 12:07, Sascha Hauer wrote: > I smell problems with this patch. Which clocks do you have that do not > have a round_rate hook but still allow to set its rate? Well, the reason for making this patch was actually the lack of any output from the clk_set_rate command if

Re: One barebox image for multiple boards

Hi, I was pleasantly surprised to get so many comments on this topic. Thank you everyone for your input! Since I want to avoid duplicating the i2c bus driver in a PBL capable version, I decided to have a common barebox device tree for all boards. This means that the detection takes place in

[PATCH] gpiolib: fix allocating dynamic gpio numbers.

Since f349b66267 the loop in gpiochip_find_base() counts downwards, hence we must decrease i by the number of GPIOs in the current chip, not increase them. Fixes: f349b66267 ("gpio: allocate dynamic gpio numbers top down") Reported-by: Alexander Shiyan Signed-off-by: Sascha Hauer ---

Driver load order

Hi, I try to create a basic driver for rk808 pmic/iodomains. I've noticed that first the iodomain driver is probed and then the rk808 on,but i need it reversed as rk808 registers regulators linked in iodomain via devicetree. How can i defer iodomain probing till rk808 is ready (regulators

Re: Driver load order

Hello Frank, On 19.05.22 12:59, Frank Wunderlich wrote: > Hi, > > I try to create a basic driver for rk808 pmic/iodomains. I've noticed that > first the iodomain driver is probed and then the rk808 on,but i need it > reversed as rk808 registers regulators linked in iodomain via devicetree. >

Re: Driver load order

Hi Frank, On Thu, May 19, 2022 at 12:59:35PM +0200, Frank Wunderlich wrote: > Hi, > > I try to create a basic driver for rk808 pmic/iodomains. I've noticed > that first the iodomain driver is probed and then the rk808 on,but i > need it reversed as rk808 registers regulators linked in iodomain

[PATCH 2/2] regulator: add Rockchip rk808 support

From: Ahmad Fatoum Signed-off-by: Ahmad Fatoum --- drivers/mfd/rk808.c | 395 drivers/regulator/Kconfig | 10 + drivers/regulator/Makefile | 1 + drivers/regulator/rk808-regulator.c | 897 include/linux/mfd/rk808.h

[PATCH 1/2] regmap: implement regmap_init_i2c_smbus

From: Ahmad Fatoum Signed-off-by: Ahmad Fatoum --- Works good enough to toggle Ethernet PHY regulator on a rk3399-based Rock Pi N10. --- drivers/base/regmap/regmap-i2c.c | 37 include/regmap.h | 3 +++ 2 files changed, 40 insertions(+) diff

Re: Aw: Re: Driver load order

On Thu, May 19, 2022 at 02:50:13PM +0200, Ahmad Fatoum wrote: > On 19.05.22 14:43, Frank Wunderlich wrote: > > @ahmad: thanks for your driver. Take a quick look into it... > > > > it seems nearly complete, is there anything not working or was the only > > problem the missing regmap-handling added

Re: v2022.05.0

On Thu, May 19, 2022 at 11:11:06AM +0300, Alexander Shiyan wrote: > ср, 18 мая 2022 г. в 16:00, Sascha Hauer : > > Hi All, > > barebox-2022.05.0 is out. > > Hello. > After updating to the new version, I found errors... > This is probably the result of the "gpio: allocate dynamic gpio > numbers

Re: [PATCH] of: address: treat absent dma-ranges as 1:1 translation

On Wed, May 18, 2022 at 07:57:45PM +0200, Lucas Stach wrote: > Some DTs use dma-ranges in child busses without this property being present > in the parent bus. To avoid failing the address translation, do the same as > the Linux kernel and treat absence of this property as a 1:1 translation. > >

Aw: Re: Driver load order

Hi, > Gesendet: Donnerstag, 19. Mai 2022 um 13:54 Uhr > Von: "Sascha Hauer" > An: "Frank Wunderlich" > Cc: barebox@lists.infradead.org > Betreff: Re: Driver load order > > Hi Frank, > > On Thu, May 19, 2022 at 12:59:35PM +0200, Frank Wunderlich wrote: > > Hi, > > > > I try to create a basic

Re: Driver load order

On 19.05.22 14:17, Ahmad Fatoum wrote: > Hello Frank, > > On 19.05.22 12:59, Frank Wunderlich wrote: >> Hi, >> >> I try to create a basic driver for rk808 pmic/iodomains. I've noticed that >> first the iodomain driver is probed and then the rk808 on,but i need it >> reversed as rk808 registers

Re: Aw: Re: Driver load order

On 19.05.22 14:43, Frank Wunderlich wrote: > @ahmad: thanks for your driver. Take a quick look into it... > > it seems nearly complete, is there anything not working or was the only > problem the missing regmap-handling added in part1? IIRC, Linux just has regmap_i2c_init which does the correct

Aw: Re: Re: Driver load order

Hi > Gesendet: Donnerstag, 19. Mai 2022 um 15:10 Uhr > Von: "Sascha Hauer" > > I gave it a test with your rk808 driver. It just works \o/ > > regulator_get() triggers probing of the rk808 regulator driver and > returns a valid regulator. Added rk808 drivers to my and added basic

Re: [PATCH] mci: core: add device parameter for eMMC boot ack

Hello Sascha, On 18.05.20 09:08, Sascha Hauer wrote: > On Wed, May 13, 2020 at 01:46:36PM +0200, Lucas Stach wrote: >> This adds an easy way to enable the boot acknowledge function of >> a eMMC device, without the need to frob the EXT_CSD setting via >> the mmc_extcsd command. >> A boot ack is