On 17/01/21 1:48 AM, David Lechner wrote:
> On 1/15/21 10:45 AM, Suman Anna wrote:
>> + Sekhar and Bartosz
>>
>> Hi David,
>>
>> On 1/4/21 12:30 PM, David Lechner wrote:
>>> This adds a "ti,am1806-pruss" compatible type for the PRUSS found in
>>> TI AM18xx/OMAP-L138 SoCs.
>>>
>>> Signed-off-by:
+ Peter, Pawel and Roger for their acks.
On 08/12/20 10:38 AM, Aswath Govindraju wrote:
> I would like to help in reviewing CADENCE USB3 DRD IP DRIVER patches
>
> Signed-off-by: Aswath Govindraju
> ---
>
> Resending the patch to add more viewers.
>
> MAINTAINERS | 1 +
> 1 file changed, 1
On 24/11/20 3:22 PM, Pawel Laszczak wrote:
> Sekhar,
>
>>
>>
>> On 24/11/20 2:51 PM, Pawel Laszczak wrote:
>>> Peter,
>>>
On 20-11-19 15:12:57, Pawel Laszczak wrote:
> This patch introduce new Cadence USBSS DRD driver to linux kernel.
>
> The Cadence USBSS DRD Controller is a
On 24/11/20 2:51 PM, Pawel Laszczak wrote:
> Peter,
>
>> On 20-11-19 15:12:57, Pawel Laszczak wrote:
>>> This patch introduce new Cadence USBSS DRD driver to linux kernel.
>>>
>>> The Cadence USBSS DRD Controller is a highly configurable IP Core which
>>> can be instantiated as Dual-Role Device
On 24/11/20 6:51 AM, Nishanth Menon wrote:
> On 09:45-20201123, Sekhar Nori wrote:
>>>> The main reason I commented - is hope to get some clarification from DT
>>>> maintainers.
>>>> 90% of interrupt-controller nodes do not have #address-cells and I never
On 19/11/20 6:58 PM, Nishanth Menon wrote:
> Punting over to Rob and DT team's wisdom..
>
> On 13:17-20201119, Grygorii Strashko wrote:
>>
>>
>> On 18/11/2020 17:12, Nishanth Menon wrote:
>>> On 13:38-20201118, Grygorii Strashko wrote:
>>>> Hi Rob,
in interrupt provider
When building TI device-tree files with W=2 warning level.
Fix these.
Signed-off-by: Sekhar Nori
---
arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 1 +
arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am65
device-tree files. Any other #address-cells value is really only needed
if interrupt-map property is being used (which is not the case for existing
TI device-tree files)
Signed-off-by: Sekhar Nori
---
arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 5 +
arch/arm64/boot/dts/ti/k
in it.
The gpio group pins out 73 pins (5 banks). Add DT nodes for each module
instance in the wakeup domain.
Signed-off-by: Faiz Abbas
Signed-off-by: Sekhar Nori
---
arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 72 +++
.../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 34 +
2
unused gpio
modules
Sekhar Nori (2):
arm64: dts: ti: k3: squelch warning about lack of #interrupt-cells
arm64: dts: ti: k3: squelch warnings regarding no #address-cells for
interrupt-controller
arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 6 ++
arch/arm64/boot/dts/ti/k3-am65
linux context and disable the rest of the nodes.
Signed-off-by: Faiz Abbas
Signed-off-by: Sekhar Nori
---
.../boot/dts/ti/k3-j7200-common-proc-board.dts | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts
b/arch/arm64/boot
On 14/11/20 9:45 AM, Grygorii Strashko wrote:
> Hi
>
> On 13/11/2020 22:55, Nishanth Menon wrote:
>> On 00:39-20201114, Sekhar Nori wrote:
>>>
>>> I was using the latest schema from master. But I changed to 2020.08.1
>>> also, and still don't see the wa
On 14/11/20 12:10 AM, Nishanth Menon wrote:
> On 23:59-20201113, Sekhar Nori wrote:
> [..]
>>> dtbs_check: we added:
>>> arch/arm64/boot/dts/ti/k3-j7200-main.dtsi: /bus@10/gpio@60: Missing
>>> #address-cells in interrupt provider
>>> arch/arm64/b
Hi Nishanth,
On 12/11/20 10:09 PM, Nishanth Menon wrote:
> On 00:41-20201103, Faiz Abbas wrote:
>> There are 4 instances of gpio modules in main domain:
>> gpio0, gpio2, gpio4 and gpio6
>>
>> Groups are created to provide protection between different processor virtual
>> worlds. Each of
On 13/11/20 10:34 PM, Nishanth Menon wrote:
> On 21:19-20201113, Sekhar Nori wrote:
>> From: Faiz Abbas
>>
>> Add configs to help enable regulators that supply power to the SD card
>> on TI's J721e platform. These regulators are controlled by either
>> SoC
1975544810376346 535572 306673661d3f266 vmlinux
After:
textdata bss dec hex filename
1976923210381390 536212 306868341d43e72 vmlinux
difference is 19,468 (dec)
Acked-by: Tero Kristo
Signed-off-by: Faiz Abbas
Signed-off-by: Sekhar
On 29/10/20 10:39 AM, Vignesh Raghavendra wrote:
> J7200 has a single instance of 8 channel ADC in MCU domain. Add DT node
> for the same.
>
> Signed-off-by: Vignesh Raghavendra
Reviewed-by: Sekhar Nori
Thanks,
Sekhar
On 14/09/20 7:49 PM, Necip Fazil Yildiran wrote:
> When MACH_DAVINCI_DA830_EVM is enabled and GPIOLIB is disabled, it results
> in the following Kbuild warning:
>
> WARNING: unmet direct dependencies detected for GPIO_PCF857X
> Depends on [n]: GPIOLIB [=n] && I2C [=y]
> Selected by [y]:
> -
Hi Necip,
On 14/09/20 6:08 PM, Necip Fazil Yildiran wrote:
> When ARCH_DAVINCI is enabled and PINCTRL is disabled, it results
> in the following Kbuild warning:
>
> WARNING: unmet direct dependencies detected for PINCTRL_SINGLE
> Depends on [n]: PINCTRL [=n] && OF [=y] && HAS_IOMEM [=y]
>
s work going on to go higher too. That needs voltage switching
though and can come in as follow-on patches. This is good first step.
Reviewed-by: Sekhar Nori
Thanks,
Sekhar
On 23/09/20 10:01 PM, Vignesh Raghavendra wrote:
> This series adds HyperBus and HyperFlash nodes for TI's J7200 SoC
Reviewed-by: Sekhar Nori
On 23/09/20 9:23 PM, Vignesh Raghavendra wrote:
> Add I2C and I2C IO expanders nodes for J7200
>
> v2:
> Align reg address format with that of file's (s/0x0/0x00)
Reviewed-by: Sekhar Nori
On 16/09/20 6:13 PM, Vinod Koul wrote:
> On 16-09-20, 15:18, Laurent Pinchart wrote:
>> Hi Sekhar,
>>
>> On Wed, Sep 16, 2020 at 01:11:17PM +0530, Sekhar Nori wrote:
>>> On 11/09/20 11:48 AM, Swapnil Jakhade wrote:
>>>> This patch series adds a new PHY att
Hi Vinod,
On 11/09/20 11:48 AM, Swapnil Jakhade wrote:
> This patch series adds a new PHY attribute max_link_rate.
> It also updates Cadence Torrent PHY driver to set attributes bus_width,
> max_link_rate and mode for DisplayPort.
>
> It includes following patches:
>
> 1.
On 10/08/20 3:07 PM, Wolfram Sang wrote:
> On Sun, Aug 09, 2020 at 07:24:44PM +0200, Stephen Kitt wrote:
>> The i2c probe functions here don't use the id information provided in
>> their second argument, so the single-parameter i2c probe function
>> ("probe_new") can be used instead.
>>
>> This
On 8/20/20 7:09 PM, Roger Quadros wrote:
> AM654x PG1.0 has a silicon bug that D+ is pulled high after POR, which
> could cause enumeration failure with some USB hubs. Disabling the
> USB2_PHY Charger Detect function will put D+ into the normal state.
>
> This addresses Silicon Errata:
> i2075 -
On 8/20/20 7:10 PM, Roger Quadros wrote:
> Kishon,
>
> On 16/07/2020 11:22, Roger Quadros wrote:
>> Move ti,omap-usb2 to its own YAML schema.
>>
>> Signed-off-by: Roger Quadros
>> Reviewed-by: Rob Herring
>
> Can you please pick just this one patch from this series for -next? Thanks.
+ Vinod
Checking return value after each regfield write becomes
hard to read quickly as number of writes increase.
Simplify by checking for error only once.
Signed-off-by: Sekhar Nori
---
drivers/phy/ti/phy-am654-serdes.c | 48 +--
1 file changed, 20 insertions(+), 28
device.
Sekhar Nori (3):
phy: ti: am654: simplify regfield handling
phy: ti: am654: simplify return handling
phy: ti: am654: update PCIe serdes config
drivers/phy/ti/phy-am654-serdes.c | 325 +++---
1 file changed, 211 insertions(+), 114 deletions(-)
--
2.17.1
Update PCIe serdes config to latest suggested for
hardware. This fixes cases of failure to enumerate
in Gen2 mode with some cards.
Signed-off-by: Sekhar Nori
---
drivers/phy/ti/phy-am654-serdes.c | 140 --
1 file changed, 135 insertions(+), 5 deletions(-)
diff --git
-by: Sekhar Nori
---
drivers/phy/ti/phy-am654-serdes.c | 161 +-
1 file changed, 68 insertions(+), 93 deletions(-)
diff --git a/drivers/phy/ti/phy-am654-serdes.c
b/drivers/phy/ti/phy-am654-serdes.c
index 0a166d5a6414..836193a71018 100644
--- a/drivers/phy/ti/phy-am654-serdes.c
On 7/27/20 3:25 PM, Vinod Koul wrote:
> Hi Sekhar,
>
> On 26-07-20, 01:24, Sekhar Nori wrote:
>> Hi Vinod,
>>
>> On 7/17/20 12:20 PM, Swapnil Jakhade wrote:
>>> This patch series adds a new pair of PHY APIs that can be used to get/set
>>> all the PHY
Hi Vinod,
On 7/17/20 12:20 PM, Swapnil Jakhade wrote:
> This patch series adds a new pair of PHY APIs that can be used to get/set
> all the PHY attributes. It also adds a new PHY attribute max_link_rate.
>
> It includes following patches:
>
> 1.
This patch series updates AM654x PCIe serdes settings to
latest recommended by hardware. This fixes Gen2 enumeration
issues and significantly improves Gen3 enumeration failures
seen previously.
Sekhar Nori (3):
phy: ti: am654: simplify regfield handling
phy: ti: am654: simplify return
-by: Sekhar Nori
---
drivers/phy/ti/phy-am654-serdes.c | 161 +-
1 file changed, 69 insertions(+), 92 deletions(-)
diff --git a/drivers/phy/ti/phy-am654-serdes.c
b/drivers/phy/ti/phy-am654-serdes.c
index 0a166d5a6414..ed7669c6a7a0 100644
--- a/drivers/phy/ti/phy-am654-serdes.c
Checking return value after each regfield write becomes
hard to read quickly as number of writes increase.
Simplify by checking for error only once.
Signed-off-by: Sekhar Nori
---
drivers/phy/ti/phy-am654-serdes.c | 48 +--
1 file changed, 20 insertions(+), 28
Update PCIe serdes config to latest suggested for
hardware. This fixes cases of failure to enumerate
in Gen2 mode with some cards. It also improves Gen3
enumeration, but occassional failures still exist.
Signed-off-by: Sekhar Nori
---
drivers/phy/ti/phy-am654-serdes.c | 140
On 7/16/20 1:32 PM, Bartosz Golaszewski wrote:
> On Wed, Jul 15, 2020 at 2:48 PM Kieran Bingham
> wrote:
>>
>> The word 'descriptor' is misspelled throughout the tree.
>>
>> Fix it up accordingly:
>> decriptors -> descriptors
>>
>> Signed-off-by: Kieran Bingham
>> ---
>>
On 7/19/20 3:50 PM, Alexander A. Klimov wrote:
> Rationale:
> Reduces attack surface on kernel devs opening the links for MITM
> as HTTPS traffic is much harder to manipulate.
>
> Deterministic algorithm:
> For each file:
> If not .svg:
> For each line:
> If doesn't contain
On 7/20/20 8:00 PM, Tony Lindgren wrote:
> * Carlos Hernandez [200717 21:35]:
>> On 7/17/20 6:29 AM, Daniel Lezcano wrote:
>>> On 13/07/2020 18:26, Tony Lindgren wrote:
Fixes: 52762fbd1c47 ("clocksource/drivers/timer-ti-dm: Add clockevent and
clocksource support")
Reported-by:
Hi Santosh,
On 7/15/20 2:24 PM, Grygorii Strashko wrote:
> Since commit bcf3440c6dd7 ("net: phy: micrel: add phy-mode support for the
> KSZ9031 PHY") the networking is broken on keystone-k2g-evm board.
>
> The above board have phy-mode = "rgmii-id" and it is worked before because
> KSZ9031 PHY
On 7/16/20 5:49 PM, Faiz Abbas wrote:
> Hi,
>
> On 19/06/20 6:28 pm, Faiz Abbas wrote:
>> Enable CONFIG_SDHCI_AM654 to Support AM65x sdhci controller.
>>
>> Signed-off-by: Faiz Abbas
>> ---
>> arch/arm64/configs/defconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git
On 17/10/19 4:37 PM, Sekhar Nori wrote:
> On 30/08/19 3:53 PM, Peter Ujfalusi wrote:
>> The codec driver needs correct regulators in order to probe.
>> Both VCC_3.3V and VCC_1.8V is always on fixed regulators on the board.
>>
>> Signed-off-by: Peter Ujfalusi
>
>
On 17/10/19 4:39 PM, Sekhar Nori wrote:
> On 30/08/19 3:52 PM, Peter Ujfalusi wrote:
>> The codec driver needs correct regulators in order to probe.
>> Both VCC_3V3 and VCC_1V8 is always on fixed regulators on the board.
>>
>> Signed-off-by: Peter Ujfalusi
>
> A
On 30/08/19 3:52 PM, Peter Ujfalusi wrote:
> dm365 have only single McBSP, so the device name is without .0
>
> Fixes: 0c750e1fe481d ("ARM: davinci: dm365: Add dma_slave_map to edma")
> Signed-off-by: Peter Ujfalusi
Applied for v5.4
Thanks,
Sekhar
On 30/08/19 3:52 PM, Peter Ujfalusi wrote:
> The codec driver needs correct regulators in order to probe.
> Both VCC_3V3 and VCC_1V8 is always on fixed regulators on the board.
>
> Signed-off-by: Peter Ujfalusi
Applied for v5.4
Thanks,
Sekhar
On 30/08/19 3:53 PM, Peter Ujfalusi wrote:
> The codec driver needs correct regulators in order to probe.
> Both VCC_3.3V and VCC_1.8V is always on fixed regulators on the board.
>
> Signed-off-by: Peter Ujfalusi
Applied for v5.4
Thanks,
Sekhar
,7 +228,7 @@ CONFIG_RTC_DRV_OMAP=m
> CONFIG_DMADEVICES=y
> CONFIG_TI_EDMA=y
> CONFIG_COMMON_CLK_PWM=m
> -CONFIG_REMOTEPROC=m
> +CONFIG_REMOTEPROC=y
Acked-by: Sekhar Nori
Thanks,
Sekhar
On 08/09/19 7:01 PM, Bartosz Golaszewski wrote:
> sob., 7 wrz 2019 o 10:21 Arnd Bergmann napisał(a):
>>
>> On Wed, Aug 28, 2019 at 9:55 AM Bartosz Golaszewski
>> wrote:
>>> śr., 28 sie 2019 o 09:44 Sekhar Nori napisał(a):
>>>
>>> Actually
ned-off-by: Bartosz Golaszewski
Acked-by: Sekhar Nori
Thanks,
Sekhar
On 25/07/19 6:42 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Add all DaVinci boards to multi_v5_defconfig.
>
> Signed-off-by: Bartosz Golaszewski
Acked-by: Sekhar Nori
Thanks,
Sekhar
On 28/08/19 1:03 PM, Bartosz Golaszewski wrote:
> pon., 5 sie 2019 o 10:31 Bartosz Golaszewski napisał(a):
>>
>> czw., 25 lip 2019 o 16:57 Arnd Bergmann napisał(a):
>>>
>>> On Thu, Jul 25, 2019 at 3:13 PM Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
This series
On 23/07/19 3:06 AM, Christophe JAILLET wrote:
> The driver is dedicated to DM646x. So update the description in the top
> most comment accordingly.
>
> It must have been derived from dm644x.c, but looks DM646 speecific now.
>
> Signed-off-by: Christophe JAILLET
Applied to my v5.4/soc branch.
On 23/07/19 5:40 PM, Adam Ford wrote:
> Logic PD re-spun the L138 and AM1808 SOM's with larger flash.
> The m25p80 driver has a generic 'jedec,spi-nor' compatible option
> which is requests to use whenever possible since it will read the
> JEDEC READ ID opcode.
>
> Signed-off-by: Adam Ford
On 08/08/19 1:11 PM, Bartosz Golaszewski wrote:
> śr., 7 sie 2019 o 21:28 Sekhar Nori napisał(a):
>>
>> On 05/08/19 1:59 PM, Bartosz Golaszewski wrote:
>>> pon., 22 lip 2019 o 15:17 Bartosz Golaszewski napisał(a):
>>>>
>>>> From: Bartosz Golasz
On 05/08/19 2:00 PM, Bartosz Golaszewski wrote:
> pon., 22 lip 2019 o 15:44 Bartosz Golaszewski napisał(a):
>>
>> From: Bartosz Golaszewski
>>
>> This is another small step on the path to liberating davinci from legacy
>> GPIO API calls and shrinking the davinci GPIO driver by not having to
>>
On 05/08/19 1:59 PM, Bartosz Golaszewski wrote:
> pon., 22 lip 2019 o 15:17 Bartosz Golaszewski napisał(a):
>>
>> From: Bartosz Golaszewski
>>
>> Sekhar,
>>
>> the following patches switch DaVinci to using the new clocksource driver
>> which
>> is now upstream. They are rebased on top of
TI's
> downstream kernels. However, that kernel no longer supports dm365 after
> linux-2.6.37, and the mainline version moved in a different direction.
>
> Signed-off-by: Arnd Bergmann
Acked-by: Sekhar Nori
Thanks,
Sekhar
Hi Arnd,
On 22/07/19 1:42 PM, Arnd Bergmann wrote:
> The dm365_isif staging driver uses an odd method for configuring its
> pin muxing by calling directly into low-level davinci platform specific
> code, even when being compile-tested for other platforms.
>
> As we want davinci to be part of a
On 04/07/19 1:55 PM, Felipe Balbi wrote:
>
> Hi,
>
> Pawel Laszczak writes:
>
>>>
>>> Hi,
>>>
>>> On Thu, Jul 4, 2019 at 9:59 AM Greg KH wrote:
On Thu, Jul 04, 2019 at 04:34:58PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the usb tree, today's linux-next
On 25/06/19 10:19 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> We need to enable status changes for the fixed power supply for the USB
> controller.
>
> Fixes: 274e4c336192 ("ARM: davinci: da830-evm: add a fixed regulator for
> ohci-da8xx")
> Cc: sta...@vger.kernel.org
>
On 25/06/19 8:46 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> The fixed regulator driver doesn't specify any con_id for gpio lookup
> so it must be NULL in the table entry.
>
> Fixes: 274e4c336192 ("ARM: davinci: da830-evm: add a fixed regulator for
> ohci-da8xx")
> Cc:
davinci_voicecodec.c:22:10: fatal error: 'mach/hardware.h' file
>> not found
>>
>> The header is only used to access the io_v2p() macro, but the
>> result is already known because that comes from the resource
>> a little bit earlier.
>>
>> Signed-off-by: Arnd Bergmann
Acked-by: Sekhar Nori
Thanks,
Sekhar
On 28/06/19 4:21 PM, Arnd Bergmann wrote:
> The driver builds fine without these, and they cause build
> problems once davinci multiplatform support is enabled.
>
> Signed-off-by: Arnd Bergmann
Acked-by: Sekhar Nori
Thanks,
Sekhar
On 24/06/19 12:51 PM, Bartosz Golaszewski wrote:
> pon., 24 cze 2019 o 07:40 Daniel Lezcano
> napisał(a):
>>
>>
>> Sekhar, Bartosz,
>>
>> if the sparse warning is not fixed, the driver won't hit this kernel
>> version. Please fix it before the two next days otherwise it won't make
>> it for
On 27/05/19 1:52 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Note: resending rebased on top of v5.2-rc2
>
> ===
>
> This series adds cpufreq-dt operating points for da850 boards supported
> with device tree (da850-lcdk, da850-lego-ev3, da850-evm).
>
> Last patch enables
h/arm/mach-davinci/sleep.S:56: Error: selected processor does not support
> `blx ip' in ARM mode
>
> Add a .arch statement in the sources to make this file build.
>
> Signed-off-by: Arnd Bergmann
Tested on OMAP-L138 LCDK board with suspend-resume.
Assuming you will pick this
On 18/06/19 11:33 PM, Daniel Lezcano wrote:
> On 14/06/2019 16:25, Daniel Lezcano wrote:
>> On 14/06/2019 12:39, Sekhar Nori wrote:
>>> Hi Daniel,
>>>
>>> On 05/06/19 2:03 PM, Bartosz Golaszewski wrote:
>>>> From: Bartosz Golaszewski
>
On 07/06/19 8:03 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> The lcdc device is missing the dma_coherent_mask definition causing the
> following warning on da850-evm:
>
> da8xx_lcdc da8xx_lcdc.0: found Sharp_LK043T1DG01 panel
> [ cut here ]
> WARNING:
On 08/06/19 7:37 PM, Linus Walleij wrote:
> On Fri, Jun 7, 2019 at 11:02 AM Bartosz Golaszewski wrote:
>
>> From: Bartosz Golaszewski
>>
>> The BB expander at 0x21 i2c bus 1 fails to probe on da850-evm because
>> the board doesn't set has_full_constraints to true in the regulator
>> API.
>>
>>
Hi Daniel,
On 05/06/19 2:03 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> This is another version of the new davinci clocksource driver. After much
> discussion this contains many changes to simplify and improve the driver.
Does this look good to you now? If yes, can you
_disable() from interrupt context, we need to
> switch to using a oneshot threaded interrupt.
>
> Acked-by: Alan Stern
> Signed-off-by: Bartosz Golaszewski
> Signed-off-by: Sekhar Nori
> Signed-off-by: Sasha Levin
This is a preparatory patch for some clean-up. This should not be
backported to stable.
Thanks,
Sekhar
On 04/06/19 1:47 PM, Pawel Laszczak wrote:
>>
>> On 10/04/19 1:18 PM, Pawel Laszczak wrote:
>>> +static void cdns3_wa1_tray_restore_cycle_bit(struct cdns3_device *priv_dev,
>>> +struct cdns3_endpoint *priv_ep)
>>> +{
>>> + int dma_index;
>>> + u32
On 10/04/19 1:18 PM, Pawel Laszczak wrote:
> +static void cdns3_wa1_tray_restore_cycle_bit(struct cdns3_device *priv_dev,
> + struct cdns3_endpoint *priv_ep)
> +{
> + int dma_index;
> + u32 doorbell;
> +
> + doorbell =
On 16/05/19 6:18 PM, Axel Lin wrote:
> A NULL init_data once incremented will lead to oops, fix it.
>
> Fixes: f979c08f7624 ("regulator: tps6507x: Convert to regulator core's
> simplified DT parsing code")
> Reported-by: Sekhar Nori
> Signed-off-by: Axel Lin
>
Hi Axel Lin,
Your commit f979c08f7624 ("regulator: tps6507x: Convert to regulator
core's simplified DT parsing code") causes a boot regression on da850-
evm.
The device-tree file is arch/arm/boot/dts/da850-evm.dts
Full logs below. tps_board in tps6507x_pmic_probe() is NULL. The check
for
and drivers/clk/davinci
Acked-by: Sekhar Nori
Thanks,
Sekhar
On 16/04/19 2:07 PM, Bartosz Golaszewski wrote:
> If we agree on the direction of these patches, then I can go with a
> single enabled OPP for lcdk (456 MHz) and all OPPs up to 375 MHz
> enabled for da850-evm.
Sounds good to me.
Thanks,
Sekhar
On 16/04/19 5:18 PM, Adam Ford wrote:
> On Tue, Apr 16, 2019 at 3:38 AM Bartosz Golaszewski wrote:
>>
>> pon., 15 kwi 2019 o 12:21 Sekhar Nori napisał(a):
>>>
>>> On 12/04/19 9:01 PM, Bartosz Golaszewski wrote:
>>>> pt., 12 kwi 2019 o 15:53 Sekhar N
On 12/04/19 9:01 PM, Bartosz Golaszewski wrote:
> pt., 12 kwi 2019 o 15:53 Sekhar Nori napisał(a):
>>
>> On 12/04/19 5:41 PM, Bartosz Golaszewski wrote:
>>> pt., 12 kwi 2019 o 13:26 Sekhar Nori napisał(a):
>>>>
>>>> Hi Bartosz,
>>>>
>
On 12/04/19 5:41 PM, Bartosz Golaszewski wrote:
> pt., 12 kwi 2019 o 13:26 Sekhar Nori napisał(a):
>>
>> Hi Bartosz,
>>
>> On 08/04/19 1:29 PM, Bartosz Golaszewski wrote:
>>> From: David Lechner
>>>
>>> This adds a cpu node and operating poin
On 08/04/19 1:29 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Enable cpufreq-dt support for da850-evm. The cvdd is supplied by the
> tps6507 pmic with configurable output voltage, so all operating points
> can be enabled.
>
> Signed-off-by: Bartosz Golaszewski
Adam, can you
Hi Bartosz,
On 08/04/19 1:29 PM, Bartosz Golaszewski wrote:
> From: David Lechner
>
> This adds a cpu node and operating points to the common da850.dtsi file.
>
> Additionally, a regulator is added to the LEGO EV3 board along with
> some board-specific CPU configuration.
>
> Regulators need
Hi Bartosz,
On 11/04/19 3:00 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Historically the power supply management in this driver has been handled
> in two separate places in parallel. Device-tree users simply defined an
> appropriate regulator, while two boards with no DT
On 04/04/19 4:44 PM, Adam Ford wrote:
> On Thu, Apr 4, 2019 at 5:01 AM Bartosz Golaszewski wrote:
>>
>> śr., 3 kwi 2019 o 17:49 Adam Ford napisał(a):
>>>
>>> On Wed, Apr 3, 2019 at 7:50 AM Bartosz Golaszewski wrote:
>>>>
>>>> śr., 27 mar
On 25/03/19 6:38 PM, Arnd Bergmann wrote:
> On Mon, Mar 18, 2019 at 1:29 PM Bartosz Golaszewski wrote:
>>
>> From: Bartosz Golaszewski
>>
>> Add modifications necessary to make davinci part of the ARM v5
>> multiplatform build.
>>
>> Move the arch-specific configuration out of arch/arm/Kconfig
Hi Daniel, Thomas,
On 18/03/19 5:40 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> This series removes the legacy timer code from mach-davinci in favor of
> a new clocksource driver it introduces.
>
> Patch 1 adds a new clocksource driver for davinci.
>
> Patch 2 enables the
Hi Bart,
On 26/03/19 11:21 PM, Bartosz Golaszewski wrote:
> wt., 26 mar 2019 o 15:00 Adam Ford napisał(a):
>>
>> On Fri, Mar 22, 2019 at 8:31 AM Bartosz Golaszewski wrote:
>>>
>>> From: Bartosz Golaszewski
>>>
>>> The system_rev variable is never set on davinci and is always 0, so
>>> we're
On 18/02/19 7:49 PM, Marc Zyngier wrote:
> On Thu, 14 Feb 2019 15:51:54 +0100
> Bartosz Golaszewski wrote:
>
>> From: Bartosz Golaszewski
>>
>> This series ports the davinci platform to using SPARSE_IRQ, cleans up
>> the irqchip drivers and moves them over to drivers/irqchip.
>
> [...]
>
>
On 18/02/19 11:46 AM, Viresh Kumar wrote:
> Applied. Thanks.
Here is a belated ack from my side.
Acked-by: Sekhar Nori
Thanks,
Sekhar
Marc,
On 14/02/19 8:21 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> This series ports the davinci platform to using SPARSE_IRQ, cleans up
> the irqchip drivers and moves them over to drivers/irqchip.
>
> The series can be logically split into five parts. The first patch
>
+ Dmitry for his ack
On 12/02/19 4:07 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> The mach/ and asm/ includes are not needed in davinci_keyscan, but they
> will cause build problems once we make mach/irqs.h a private header for
> mach-davinci.
>
> Remove all unused header
On 14/02/19 4:27 PM, Marc Zyngier wrote:
> On Tue, 12 Feb 2019 10:38:18 +,
> Bartosz Golaszewski wrote:
>>
>> From: Bartosz Golaszewski
>>
>> I've been unable to figure out exactly why, but it seems that the
>> IRQ_TINT1_TINT34 interrupt for timer 1 needs to be handled as a
>> level irq, not
On 11/02/19 5:55 PM, Bartosz Golaszewski wrote:
> diff --git a/arch/arm/mach-davinci/usb.c b/arch/arm/mach-davinci/usb.c
> index 9d4a58a3113a..cde72ba35dc3 100644
> --- a/arch/arm/mach-davinci/usb.c
> +++ b/arch/arm/mach-davinci/usb.c
> @@ -5,13 +5,14 @@
> #include
> #include
> #include
> -
On 11/02/19 5:55 PM, Bartosz Golaszewski wrote:
> @@ -74,6 +75,7 @@ void __init davinci_irq_init(void)
> {
> unsigned i, j;
> const u8 *davinci_def_priorities = davinci_soc_info.intc_irq_prios;
> + int rv, irq_base;
>
> davinci_intc_type = DAVINCI_INTC_TYPE_AINTC;
>
On 11/02/19 5:55 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> NOTE: resending due to missing irqchip maintainers in Cc
>
> This series ports the davinci platform to using SPARSE_IRQ, cleans up
> the irqchip drivers and moves them over to drivers/irqchip.
>
> The series can be
On 05/02/19 6:11 PM, Linus Walleij wrote:
> On Tue, Feb 5, 2019 at 10:49 AM Bartosz Golaszewski wrote:
>> From: Bartosz Golaszewski
>>
>> In order to drop the hard-coded GPIO base values from the davinci GPIO
>> driver's platform data, we first need to get rid of all calls to the
>> legacy GPIO
On 11/02/19 4:06 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> There are two users upstream which register external callbacks for
> switching the port power on/off and overcurrent protection. Both
> users only use two GPIOs for that. Instead of having that functionality
> in the
On 11/02/19 6:30 PM, Marc Zyngier wrote:
> On 11/02/2019 12:25, Bartosz Golaszewski wrote:
>> +/*
>> + * Nobody knows why anymore, but this interrupt has been handled as
>> + * a level irq from the very beginning of davinci support in mainline
>> + * linux.
>> + */
>> +
+ Jason, Marc
Thomas, Jason, Marc,
On 08/02/19 11:04 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> This series ports the davinci platform to using SPARSE_IRQ, cleans up
> the irqchip drivers and moves them over to drivers/irqchip.
>
> The series can be logically split into
1 - 100 of 2392 matches
Mail list logo
