Re: [PATCH 2/2] media: s5p-mfc: fix MMAP of mfc buffer during reqbufs

Hello Javier, On Saturday 25 February 2017 01:12 AM, Javier Martinez Canillas wrote: > Hello Pankaj, > > On 12/16/2016 08:48 AM, Pankaj Dubey wrote: >> From: Smitha T Murthy >> >> It has been observed on ARM64 based Exynos SoC, if IOMMU is not enabled >> and we try to use

Re: [PATCH 2/2] media: s5p-mfc: fix MMAP of mfc buffer during reqbufs

Hello Javier, On Saturday 25 February 2017 01:12 AM, Javier Martinez Canillas wrote: > Hello Pankaj, > > On 12/16/2016 08:48 AM, Pankaj Dubey wrote: >> From: Smitha T Murthy >> >> It has been observed on ARM64 based Exynos SoC, if IOMMU is not enabled >> and we try to use reserved memory for

Re: [PATCH 1/2] media: s5p-mfc: convert drivers to use the new vb2_queue dev field

xynos7880 based development board. Anyways FYI, This patch is series is superseded by patch [1] after review comments and suggestion from Marek. Patch [1] has been accepted and merged and working well for us. [1]: https://patchwork.kernel.org/patch/9482499/ Thanks, Pankaj Dubey >> Signed-off-b

Re: [PATCH 1/2] media: s5p-mfc: convert drivers to use the new vb2_queue dev field

h is series is superseded by patch [1] after review comments and suggestion from Marek. Patch [1] has been accepted and merged and working well for us. [1]: https://patchwork.kernel.org/patch/9482499/ Thanks, Pankaj Dubey >> Signed-off-by: Smitha T Murthy >> [pankaj.dubey: debugging is

Re: PCI: dwc: Add COMPILE_TEST to all designware based drivers

Hi Kishon, On Thursday 12 January 2017 03:13 PM, Kishon Vijay Abraham I wrote: > Add COMPILE_TEST to all designware based drivers so that it is possible > to perform compile test even when a particular architecture specific > config symbol is not set. > > Signed-off-by: Kishon Vijay Abraham I

Re: PCI: dwc: Add COMPILE_TEST to all designware based drivers

Hi Kishon, On Thursday 12 January 2017 03:13 PM, Kishon Vijay Abraham I wrote: > Add COMPILE_TEST to all designware based drivers so that it is possible > to perform compile test even when a particular architecture specific > config symbol is not set. > > Signed-off-by: Kishon Vijay Abraham I >

Re: [PATCH v2] PCI: exynos: refactor exynos pcie driver

Hello Jingoo, Bjorn, On Thursday 05 January 2017 09:47 AM, Jaehoon Chung wrote: > On 01/05/2017 12:53 PM, Pankaj Dubey wrote: >> From: Niyas Ahmed S T >> >> Currently Exynos PCIe driver is only supported for Exynos5440 SoC. >> This patch does refactoring of Exynos PCIe

Re: [PATCH v2] PCI: exynos: refactor exynos pcie driver

Hello Jingoo, Bjorn, On Thursday 05 January 2017 09:47 AM, Jaehoon Chung wrote: > On 01/05/2017 12:53 PM, Pankaj Dubey wrote: >> From: Niyas Ahmed S T >> >> Currently Exynos PCIe driver is only supported for Exynos5440 SoC. >> This patch does refactoring of Exynos PCIe driver to extend support

Re: [PATCH] arm64: dts: exynos: Remove address node from usb parent node

Hi Javier, On Wednesday 18 January 2017 09:06 PM, Javier Martinez Canillas wrote: > Hello, > > On 01/18/2017 04:04 AM, Chanwoo Choi wrote: >> Hi Pankaj, >> >> This issue already posted by Javier Martinez Canillas[1]. >> Maybe, he will post v2. >> > > That's correct, I didn't post a v2 since I

Re: [PATCH] arm64: dts: exynos: Remove address node from usb parent node

Hi Javier, On Wednesday 18 January 2017 09:06 PM, Javier Martinez Canillas wrote: > Hello, > > On 01/18/2017 04:04 AM, Chanwoo Choi wrote: >> Hi Pankaj, >> >> This issue already posted by Javier Martinez Canillas[1]. >> Maybe, he will post v2. >> > > That's correct, I didn't post a v2 since I

Re: [PATCH] usb: dwc3-exynos fix unspecified suspend clk error handling

Hi Krzysztof, On Tuesday 10 January 2017 11:55 PM, Krzysztof Kozlowski wrote: > On Tue, Jan 10, 2017 at 06:09:40PM +0100, Bartlomiej Zolnierkiewicz wrote: >> BTW What is interesting is that the Exynos7 dts patch [2] has never >> made it into upstream for some reason. In the meantime however >>

Re: [PATCH] usb: dwc3-exynos fix unspecified suspend clk error handling

Hi Krzysztof, On Tuesday 10 January 2017 11:55 PM, Krzysztof Kozlowski wrote: > On Tue, Jan 10, 2017 at 06:09:40PM +0100, Bartlomiej Zolnierkiewicz wrote: >> BTW What is interesting is that the Exynos7 dts patch [2] has never >> made it into upstream for some reason. In the meantime however >>

Re: [PATCH V2 4/5] PCI: exynos: support the using PHY generic framework

Hi Jaehoon, On Wednesday 04 January 2017 06:04 PM, Jaehoon Chung wrote: > This patch is for using PHY generic framework. > To maintain backward compatibility, check whether phy is supported or > not with 'using_phy'. > > And if someone use the old dt-file, display the "deprecated" message. > But

Re: [PATCH V2 4/5] PCI: exynos: support the using PHY generic framework

Hi Jaehoon, On Wednesday 04 January 2017 06:04 PM, Jaehoon Chung wrote: > This patch is for using PHY generic framework. > To maintain backward compatibility, check whether phy is supported or > not with 'using_phy'. > > And if someone use the old dt-file, display the "deprecated" message. > But

Re: [PATCH V2 5/5] ARM: dts: exynos5440: support the phy-pcie node for pcie

Hi Jaehoon, On Wednesday 04 January 2017 06:04 PM, Jaehoon Chung wrote: > Add phy-pcie node for using Exynos5440 pcie. > And use the reg-names as "elbi" and "config". > Because the getting configuratioin space address from ranges is old way. > It also is helpful to distinguish more clearly. > >

Re: [PATCH V2 5/5] ARM: dts: exynos5440: support the phy-pcie node for pcie

Hi Jaehoon, On Wednesday 04 January 2017 06:04 PM, Jaehoon Chung wrote: > Add phy-pcie node for using Exynos5440 pcie. > And use the reg-names as "elbi" and "config". > Because the getting configuratioin space address from ranges is old way. > It also is helpful to distinguish more clearly. > >

Re: [PATCH V2 3/5] Documetation: binding: modify the exynos5440 pcie binding

Hi Jaehoon, On Wednesday 04 January 2017 06:04 PM, Jaehoon Chung wrote: > According to using PHY framework, updates the exynos5440-pcie binding. > For maintaining backward compatibility, leaves the current dt-binding. > (It should be deprecated.) > > Recommends to use the Phy Framework and

Re: [PATCH V2 3/5] Documetation: binding: modify the exynos5440 pcie binding

Hi Jaehoon, On Wednesday 04 January 2017 06:04 PM, Jaehoon Chung wrote: > According to using PHY framework, updates the exynos5440-pcie binding. > For maintaining backward compatibility, leaves the current dt-binding. > (It should be deprecated.) > > Recommends to use the Phy Framework and

Re: [PATCH V2 2/5] phy: phy-exynos-pcie: Add support for Exynos PCIe phy

Hi Jaehoon, On Wednesday 04 January 2017 06:04 PM, Jaehoon Chung wrote: > This patch supports to use Generic Phy framework for Exynos PCIe phy. > When Exynos that supported the pcie want to use the PCIe, > it needs to control the phy resgister. > But it should be more complex to control in their

Re: [PATCH V2 2/5] phy: phy-exynos-pcie: Add support for Exynos PCIe phy

Hi Jaehoon, On Wednesday 04 January 2017 06:04 PM, Jaehoon Chung wrote: > This patch supports to use Generic Phy framework for Exynos PCIe phy. > When Exynos that supported the pcie want to use the PCIe, > it needs to control the phy resgister. > But it should be more complex to control in their

Re: [PATCH V2 1/5] Documetation: samsung-phy: add the exynos-pcie-phy binding

Hi, On Thursday 05 January 2017 09:46 AM, Alim Akhtar wrote: > Hi Jaehoon, > > On 01/04/2017 06:04 PM, Jaehoon Chung wrote: >> Adds the exynos-pcie-phy binding for Exynos PCIe PHY. >> This is for using generic PHY framework. >> >> Signed-off-by: Jaehoon Chung >> --- >>

Re: [PATCH V2 1/5] Documetation: samsung-phy: add the exynos-pcie-phy binding

Hi, On Thursday 05 January 2017 09:46 AM, Alim Akhtar wrote: > Hi Jaehoon, > > On 01/04/2017 06:04 PM, Jaehoon Chung wrote: >> Adds the exynos-pcie-phy binding for Exynos PCIe PHY. >> This is for using generic PHY framework. >> >> Signed-off-by: Jaehoon Chung >> --- >> Changelog on V2: >> -

Re: [4/4] PCI: exynos: remove the duplicated codes

Hi Jaehoon, On Monday 19 December 2016 01:47 PM, Jaehoon Chung wrote: > Removed the duplicated codes. > It can use the more simply than now. > > Signed-off-by: Jaehoon Chung > --- > drivers/pci/host/pci-exynos.c | 22 -- > 1 file changed, 8

Re: [4/4] PCI: exynos: remove the duplicated codes

Hi Jaehoon, On Monday 19 December 2016 01:47 PM, Jaehoon Chung wrote: > Removed the duplicated codes. > It can use the more simply than now. > > Signed-off-by: Jaehoon Chung > --- > drivers/pci/host/pci-exynos.c | 22 -- > 1 file changed, 8 insertions(+), 14 deletions(-) >

Re: [3/4] PCI: exynos: Use the bitops API to operate the bit shifting

Hi Jaehoon, On Monday 19 December 2016 01:47 PM, Jaehoon Chung wrote: > Just use the bitops api to operate the bit. > > Signed-off-by: Jaehoon Chung > --- > drivers/pci/host/pci-exynos.c | 24 > 1 file changed, 12 insertions(+), 12 deletions(-)

Re: [3/4] PCI: exynos: Use the bitops API to operate the bit shifting

Hi Jaehoon, On Monday 19 December 2016 01:47 PM, Jaehoon Chung wrote: > Just use the bitops api to operate the bit. > > Signed-off-by: Jaehoon Chung > --- > drivers/pci/host/pci-exynos.c | 24 > 1 file changed, 12 insertions(+), 12 deletions(-) > Reviewed-by: Pankaj

Re: [2/4] PCI: exynos: Remove the unnecessary variables

Hi Jaehoon, On Monday 19 December 2016 01:47 PM, Jaehoon Chung wrote: > Remove the unnecessary variables(elbi/phy/block_base). > It needs one resource structure for assigning each resource. > So it replaces with one 'res' variable. > > Signed-off-by: Jaehoon Chung > ---

Re: [2/4] PCI: exynos: Remove the unnecessary variables

Hi Jaehoon, On Monday 19 December 2016 01:47 PM, Jaehoon Chung wrote: > Remove the unnecessary variables(elbi/phy/block_base). > It needs one resource structure for assigning each resource. > So it replaces with one 'res' variable. > > Signed-off-by: Jaehoon Chung > --- >

Re: [1/4] PCI: exynos: replace to one register accessor from each accessors

Hi Jaehoon, On Monday 19 December 2016 01:47 PM, Jaehoon Chung wrote: > There is no reason to maintain *_blk/phy/elbi_* as register accessors. > It can be replaced to one register accessor. > > Signed-off-by: Jaehoon Chung > --- Looks fine. Nice cleanup :) Reviewed-by:

Re: [1/4] PCI: exynos: replace to one register accessor from each accessors

Hi Jaehoon, On Monday 19 December 2016 01:47 PM, Jaehoon Chung wrote: > There is no reason to maintain *_blk/phy/elbi_* as register accessors. > It can be replaced to one register accessor. > > Signed-off-by: Jaehoon Chung > --- Looks fine. Nice cleanup :) Reviewed-by: Pankaj Dubey

Re: [PATCH 0/2] s5p-mfc fix for using reserved memory

Hi Marek, On Tuesday 20 December 2016 05:28 PM, Marek Szyprowski wrote: > Hi Pankaj > > > On 2016-12-16 12:48, Pankaj Dubey wrote: >> It has been observed on ARM64 based Exynos SoC, if IOMMU is not enabled >> and we try to use reserved memory for MFC, reqbufs fails with below >> mentioned error

Re: [PATCH 0/2] s5p-mfc fix for using reserved memory

Hi Marek, On Tuesday 20 December 2016 05:28 PM, Marek Szyprowski wrote: > Hi Pankaj > > > On 2016-12-16 12:48, Pankaj Dubey wrote: >> It has been observed on ARM64 based Exynos SoC, if IOMMU is not enabled >> and we try to use reserved memory for MFC, reqbufs fails with below >> mentioned error

Re: [PATCH 01/16] ARM: scu: Provide support for parsing SCU device node to enable SCU

On Thursday 17 November 2016 10:33 PM, Arnd Bergmann wrote: > On Thursday, November 17, 2016 9:50:27 AM CET pankaj.dubey wrote: >> >>>>> of_scu_enable() which _only_ looks up the SCU address in DT and enables >>>>> it if it finds it, otherwise returning fai

Re: [PATCH 01/16] ARM: scu: Provide support for parsing SCU device node to enable SCU

On Thursday 17 November 2016 10:33 PM, Arnd Bergmann wrote: > On Thursday, November 17, 2016 9:50:27 AM CET pankaj.dubey wrote: >> >>>>> of_scu_enable() which _only_ looks up the SCU address in DT and enables >>>>> it if it finds it, otherwise returning fai

Re: [PATCH 01/16] ARM: scu: Provide support for parsing SCU device node to enable SCU

rnd Bergmann wrote: >>>> On Monday, November 14, 2016 2:10:16 PM CET pankaj.dubey wrote: >>>>>>> +scu_base = of_iomap(np, 0); >>>>>>> +of_node_put(np); >>>>>>> +if (!scu_base) { >>>>>>> +

Re: [PATCH 01/16] ARM: scu: Provide support for parsing SCU device node to enable SCU

rnd Bergmann wrote: >>>> On Monday, November 14, 2016 2:10:16 PM CET pankaj.dubey wrote: >>>>>>> +scu_base = of_iomap(np, 0); >>>>>>> +of_node_put(np); >>>>>>> +if (!scu_base) { >>>>>>> +

Re: [PATCH 12/16] ARM: imx: use generic API for enabling SCU

Hi Shawn, On Monday 14 November 2016 07:56 PM, Shawn Guo wrote: > On Mon, Nov 14, 2016 at 10:32:07AM +0530, Pankaj Dubey wrote: >> Now as we have of_scu_enable which takes care of mapping >> scu base from DT, lets use it. >> >> At the same time this patch cleans up mach-imx platform files by >>

Re: [PATCH 12/16] ARM: imx: use generic API for enabling SCU

Hi Shawn, On Monday 14 November 2016 07:56 PM, Shawn Guo wrote: > On Mon, Nov 14, 2016 at 10:32:07AM +0530, Pankaj Dubey wrote: >> Now as we have of_scu_enable which takes care of mapping >> scu base from DT, lets use it. >> >> At the same time this patch cleans up mach-imx platform files by >>

Re: [PATCH 01/16] ARM: scu: Provide support for parsing SCU device node to enable SCU

Hi Russell, On Monday 14 November 2016 07:18 PM, Russell King - ARM Linux wrote: > This should be sent _to_ me because it's touching generic ARM code. > Thanks. > Sorry for this. I had included your email in CC for this patch, but looks like my email client had some issue and this patch could

Re: [PATCH 01/16] ARM: scu: Provide support for parsing SCU device node to enable SCU

Hi Russell, On Monday 14 November 2016 07:18 PM, Russell King - ARM Linux wrote: > This should be sent _to_ me because it's touching generic ARM code. > Thanks. > Sorry for this. I had included your email in CC for this patch, but looks like my email client had some issue and this patch could

Re: [PATCH 02/16] ARM: EXYNOS: use generic API to enable SCU

Hi Krzysztof, On Wednesday 16 November 2016 12:29 AM, Krzysztof Kozlowski wrote: > On Mon, Nov 14, 2016 at 10:31:57AM +0530, Pankaj Dubey wrote: >> Now as we have of_scu_enable which takes care of mapping >> scu base from DT, lets use it. >> >> This patch also fixes build failure in case !SMP

Re: [PATCH 02/16] ARM: EXYNOS: use generic API to enable SCU

Hi Krzysztof, On Wednesday 16 November 2016 12:29 AM, Krzysztof Kozlowski wrote: > On Mon, Nov 14, 2016 at 10:31:57AM +0530, Pankaj Dubey wrote: >> Now as we have of_scu_enable which takes care of mapping >> scu base from DT, lets use it. >> >> This patch also fixes build failure in case !SMP

Re: [PATCH 08/16] ARM: vexpress: use generic API for enabling SCU

Hi Sudeep, On Wednesday 16 November 2016 08:04 PM, Sudeep Holla wrote: > > > On 14/11/16 05:02, Pankaj Dubey wrote: >> Now as we have of_scu_enable which takes care of mapping >> scu base from DT, lets use it. >> >> CC: Liviu Dudau >> CC: Sudeep Holla

Re: [PATCH 08/16] ARM: vexpress: use generic API for enabling SCU

Hi Sudeep, On Wednesday 16 November 2016 08:04 PM, Sudeep Holla wrote: > > > On 14/11/16 05:02, Pankaj Dubey wrote: >> Now as we have of_scu_enable which takes care of mapping >> scu base from DT, lets use it. >> >> CC: Liviu Dudau >> CC: Sudeep Holla > > I assume you will take this series

Re: [PATCH 04/16] ARM: realview: use generic API for enabling SCU

On Monday 14 November 2016 05:26 PM, Arnd Bergmann wrote: > On Monday, November 14, 2016 10:31:59 AM CET Pankaj Dubey wrote: >> static const struct of_device_id realview_scu_match[] = { >> { .compatible = "arm,arm11mp-scu", }, >> - { .compatible = "arm,cortex-a9-scu", }, >> -

Re: [PATCH 04/16] ARM: realview: use generic API for enabling SCU

On Monday 14 November 2016 05:26 PM, Arnd Bergmann wrote: > On Monday, November 14, 2016 10:31:59 AM CET Pankaj Dubey wrote: >> static const struct of_device_id realview_scu_match[] = { >> { .compatible = "arm,arm11mp-scu", }, >> - { .compatible = "arm,cortex-a9-scu", }, >> -

Re: [PATCH 01/16] ARM: scu: Provide support for parsing SCU device node to enable SCU

Hi Jisheng, On Monday 14 November 2016 12:24 PM, Jisheng Zhang wrote: > > On Mon, 14 Nov 2016 14:12:51 +0800 Jisheng Zhang wrote: > >> Hi Pankaj, >> >>> + * Helper API to get SCU base address >>> + * In case platform DT do not have SCU node, or iomap fails >>> + * this call will fallback and

Re: [PATCH 01/16] ARM: scu: Provide support for parsing SCU device node to enable SCU

Hi Jisheng, On Monday 14 November 2016 12:24 PM, Jisheng Zhang wrote: > > On Mon, 14 Nov 2016 14:12:51 +0800 Jisheng Zhang wrote: > >> Hi Pankaj, >> >>> + * Helper API to get SCU base address >>> + * In case platform DT do not have SCU node, or iomap fails >>> + * this call will fallback and

Re: [PATCH 01/16] ARM: scu: Provide support for parsing SCU device node to enable SCU

Hi Jisheng, On Monday 14 November 2016 11:42 AM, Jisheng Zhang wrote: > Hi Pankaj, > > On Mon, 14 Nov 2016 10:31:56 +0530 Pankaj Dubey wrote: >> + >> +np = of_find_matching_node(NULL, scu_match); > > could we check np before calling of_iomap()? > of_iomap takes care of that, and will

Re: [PATCH 01/16] ARM: scu: Provide support for parsing SCU device node to enable SCU

Hi Jisheng, On Monday 14 November 2016 11:42 AM, Jisheng Zhang wrote: > Hi Pankaj, > > On Mon, 14 Nov 2016 10:31:56 +0530 Pankaj Dubey wrote: >> + >> +np = of_find_matching_node(NULL, scu_match); > > could we check np before calling of_iomap()? > of_iomap takes care of that, and will

Re: [RFC PATCH 2/2] rtc: s3c: Add s3c_rtc_{enable/disable}_clk in s3c_rtc_setfreq()

Hi Alim, On Tuesday 05 July 2016 02:22 PM, Alim Akhtar wrote: > > > On 07/05/2016 01:46 PM, Krzysztof Kozlowski wrote: >> On 07/04/2016 01:03 PM, Alim Akhtar wrote: >>> As per code flow it is possible that s3c_rtc_setfreq() might get called >>> with rtc clock disabled and in set_freq we perform

Re: [RFC PATCH 2/2] rtc: s3c: Add s3c_rtc_{enable/disable}_clk in s3c_rtc_setfreq()

Hi Alim, On Tuesday 05 July 2016 02:22 PM, Alim Akhtar wrote: > > > On 07/05/2016 01:46 PM, Krzysztof Kozlowski wrote: >> On 07/04/2016 01:03 PM, Alim Akhtar wrote: >>> As per code flow it is possible that s3c_rtc_setfreq() might get called >>> with rtc clock disabled and in set_freq we perform

Re: [RFC PATCH 2/2] rtc: s3c: Add s3c_rtc_{enable/disable}_clk in s3c_rtc_setfreq()

Hi Alim, On Tuesday 05 July 2016 02:26 PM, Krzysztof Kozlowski wrote: > On 07/05/2016 10:52 AM, Alim Akhtar wrote: >> >> >> On 07/05/2016 01:46 PM, Krzysztof Kozlowski wrote: >>> On 07/04/2016 01:03 PM, Alim Akhtar wrote: As per code flow it is possible that s3c_rtc_setfreq() might get

Re: [RFC PATCH 2/2] rtc: s3c: Add s3c_rtc_{enable/disable}_clk in s3c_rtc_setfreq()

Hi Alim, On Tuesday 05 July 2016 02:26 PM, Krzysztof Kozlowski wrote: > On 07/05/2016 10:52 AM, Alim Akhtar wrote: >> >> >> On 07/05/2016 01:46 PM, Krzysztof Kozlowski wrote: >>> On 07/04/2016 01:03 PM, Alim Akhtar wrote: As per code flow it is possible that s3c_rtc_setfreq() might get

Re: ARM: dts: exynos: Add MFC memory banks for Peach boards

Hi Javier, On Thursday 26 May 2016 01:15 PM, Javier Martinez Canillas wrote: > [adding Kevin and Sjoerd who also noticed issues with this patch] > > Hi Pankaj, > > On 05/25/2016 11:43 PM, pankaj.dubey wrote: >> Hi Javier, >> >> On Wednesday 25 May 2016 08:32 P

Re: ARM: dts: exynos: Add MFC memory banks for Peach boards

Hi Javier, On Thursday 26 May 2016 01:15 PM, Javier Martinez Canillas wrote: > [adding Kevin and Sjoerd who also noticed issues with this patch] > > Hi Pankaj, > > On 05/25/2016 11:43 PM, pankaj.dubey wrote: >> Hi Javier, >> >> On Wednesday 25 May 2016 08:32 P

Re: ARM: dts: exynos: Add MFC memory banks for Peach boards

Hi Javier, On Wednesday 25 May 2016 08:32 PM, Javier Martinez Canillas wrote: > Hello Pankaj, > > On 05/25/2016 04:33 AM, pankaj.dubey wrote: >> Hi Javier, >> >>> Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com> >> >> Just no

Re: ARM: dts: exynos: Add MFC memory banks for Peach boards

Hi Javier, On Wednesday 25 May 2016 08:32 PM, Javier Martinez Canillas wrote: > Hello Pankaj, > > On 05/25/2016 04:33 AM, pankaj.dubey wrote: >> Hi Javier, >> >>> Signed-off-by: Javier Martinez Canillas >> >> Just noticed that, current krzk/for-

Re: ARM: dts: exynos: Add MFC memory banks for Peach boards

Hi Javier, On Friday 29 April 2016 12:51 AM, Javier Martinez Canillas wrote: > The MFC nodes with the memory regions reserved for memory allocations > are missing in the Exynos5420 Peach Pit and Exynos5800 Peach Pi DTS. > > This causes the s5p-mfc driver probe to fail with the following error: >

Re: ARM: dts: exynos: Add MFC memory banks for Peach boards

Hi Javier, On Friday 29 April 2016 12:51 AM, Javier Martinez Canillas wrote: > The MFC nodes with the memory regions reserved for memory allocations > are missing in the Exynos5420 Peach Pit and Exynos5800 Peach Pi DTS. > > This causes the s5p-mfc driver probe to fail with the following error: >

Re: [RESPIN 1/6] dt-bindings: EXYNOS: Add exynos-srom device tree binding

On Saturday 05 March 2016 11:48 AM, pankaj.dubey wrote: > Hi > > On Wednesday 02 March 2016 11:23 PM, Rob Herring wrote: >> On Thu, Feb 25, 2016 at 02:03:37PM +0530, Pankaj Dubey wrote: >>> This patch adds exynos-srom binding information for SROM Controller >>>

Re: [RESPIN 1/6] dt-bindings: EXYNOS: Add exynos-srom device tree binding

On Saturday 05 March 2016 11:48 AM, pankaj.dubey wrote: > Hi > > On Wednesday 02 March 2016 11:23 PM, Rob Herring wrote: >> On Thu, Feb 25, 2016 at 02:03:37PM +0530, Pankaj Dubey wrote: >>> This patch adds exynos-srom binding information for SROM Controller >>>

Re: [RESPIN 1/6] dt-bindings: EXYNOS: Add exynos-srom device tree binding

Hi On Wednesday 02 March 2016 11:23 PM, Rob Herring wrote: > On Thu, Feb 25, 2016 at 02:03:37PM +0530, Pankaj Dubey wrote: >> This patch adds exynos-srom binding information for SROM Controller >> driver on Exynos SoCs. >> >> CC: Rob Herring >> CC: Mark Rutland

Re: [RESPIN 1/6] dt-bindings: EXYNOS: Add exynos-srom device tree binding

Hi On Wednesday 02 March 2016 11:23 PM, Rob Herring wrote: > On Thu, Feb 25, 2016 at 02:03:37PM +0530, Pankaj Dubey wrote: >> This patch adds exynos-srom binding information for SROM Controller >> driver on Exynos SoCs. >> >> CC: Rob Herring >> CC: Mark Rutland >> CC: Ian Campbell >> CC:

Re: [RESPIN 5/6] dt-bindings: EXYNOS: Describe SROMc configuration

Hi, On Wednesday 02 March 2016 11:27 PM, Rob Herring wrote: > On Thu, Feb 25, 2016 at 02:03:41PM +0530, Pankaj Dubey wrote: >> From: Pavel Fedin >> >> Add documentation for new subnode properties, allowing bank configuration. >> Based on u-boot implementation, but heavily

Re: [RESPIN 5/6] dt-bindings: EXYNOS: Describe SROMc configuration

Hi, On Wednesday 02 March 2016 11:27 PM, Rob Herring wrote: > On Thu, Feb 25, 2016 at 02:03:41PM +0530, Pankaj Dubey wrote: >> From: Pavel Fedin >> >> Add documentation for new subnode properties, allowing bank configuration. >> Based on u-boot implementation, but heavily reworked. >> >> Also,

Re: [RESPIN 1/6] dt-bindings: EXYNOS: Add exynos-srom device tree binding

Hi, On Wednesday 02 March 2016 11:23 PM, Rob Herring wrote: > On Thu, Feb 25, 2016 at 02:03:37PM +0530, Pankaj Dubey wrote: >> This patch adds exynos-srom binding information for SROM Controller >> driver on Exynos SoCs. >> >> CC: Rob Herring >> CC: Mark Rutland

Re: [RESPIN 1/6] dt-bindings: EXYNOS: Add exynos-srom device tree binding

Hi, On Wednesday 02 March 2016 11:23 PM, Rob Herring wrote: > On Thu, Feb 25, 2016 at 02:03:37PM +0530, Pankaj Dubey wrote: >> This patch adds exynos-srom binding information for SROM Controller >> driver on Exynos SoCs. >> >> CC: Rob Herring >> CC: Mark Rutland >> CC: Ian Campbell >> CC:

Re: [GIT PULL 3/7] drivers: soc: EXYNOS drivers for v4.6

Hi Krzysztof, On Thursday 25 February 2016 06:13 AM, Krzysztof Kozlowski wrote: > On 25.02.2016 07:22, Olof Johansson wrote: >> On Mon, Feb 15, 2016 at 09:34:02AM +0900, Krzysztof Kozlowski wrote: >>> Hi Arnd, Kevin and Olof, >>> >>> This finally moves SROM controller and PMU code to separate >>>

Re: [GIT PULL 3/7] drivers: soc: EXYNOS drivers for v4.6

Hi Krzysztof, On Thursday 25 February 2016 06:13 AM, Krzysztof Kozlowski wrote: > On 25.02.2016 07:22, Olof Johansson wrote: >> On Mon, Feb 15, 2016 at 09:34:02AM +0900, Krzysztof Kozlowski wrote: >>> Hi Arnd, Kevin and Olof, >>> >>> This finally moves SROM controller and PMU code to separate >>>

Re: [PATCH] arm64: dts: Add tmu node for exynos7

Hi Krzysztof, On Thursday 25 February 2016 09:36 AM, Krzysztof Kozlowski wrote: > On 25.02.2016 12:27, Pankaj Dubey wrote: >> From: Alim Akhtar >> >> This patch adds tmu node, related temprature sensor and triping >> point data for Atlas cpu core found on exynos7 SoC. >>

Re: [PATCH] arm64: dts: Add tmu node for exynos7

Hi Krzysztof, On Thursday 25 February 2016 09:36 AM, Krzysztof Kozlowski wrote: > On 25.02.2016 12:27, Pankaj Dubey wrote: >> From: Alim Akhtar >> >> This patch adds tmu node, related temprature sensor and triping >> point data for Atlas cpu core found on exynos7 SoC. >> >> Signed-off-by: Alim

Re: [PATCH v7 0/6] samsung: pmu: split up SoC specific PMU data

Hi Krzysztof, On Friday 18 December 2015 09:57 AM, Krzysztof Kozlowski wrote: > On 18.12.2015 12:32, Pankaj Dubey wrote: >> In this series I am splitting up SoC specific PMU configuration data into >> mach-exynos folder itself, before moving all of them under >> drivers/soc/samsung/. Also instead

Re: [PATCH v7 0/6] samsung: pmu: split up SoC specific PMU data

Hi Krzysztof, On Friday 18 December 2015 09:57 AM, Krzysztof Kozlowski wrote: > On 18.12.2015 12:32, Pankaj Dubey wrote: >> In this series I am splitting up SoC specific PMU configuration data into >> mach-exynos folder itself, before moving all of them under >> drivers/soc/samsung/. Also instead

Re: [PATCH v6 0/9] samsung: pmu: split up SoC specific PMU data

Hi Krzysztof, On Thursday 17 December 2015 11:01 AM, Krzysztof Kozlowski wrote: > On 17.11.2015 15:05, Pankaj Dubey wrote: >> In this series I am splitting up SoC specific PMU configuration data into >> mach-exynos folder itself, before moving all of them under >> drivers/soc/samsung/. Also

Re: [RESEND PATCH v5 0/8] Add support for Exynos SROM Controller driver

Hi Krzysztof, On Thursday 17 December 2015 10:44 AM, Krzysztof Kozlowski wrote: > On 12.12.2015 16:43, Pankaj Dubey wrote: >> THIS IS A RESEND OF ONCE MERGED INTO kgene/for-next AND LOST PATCHES >> >> Series v5 got merged in kgene/for-next but due to last moment change before >> pull >> these

Re: [RESEND PATCH v5 0/8] Add support for Exynos SROM Controller driver

Hi Krzysztof, On Thursday 17 December 2015 10:44 AM, Krzysztof Kozlowski wrote: > On 12.12.2015 16:43, Pankaj Dubey wrote: >> THIS IS A RESEND OF ONCE MERGED INTO kgene/for-next AND LOST PATCHES >> >> Series v5 got merged in kgene/for-next but due to last moment change before >> pull >> these

Re: [PATCH v6 0/9] samsung: pmu: split up SoC specific PMU data

Hi Krzysztof, On Thursday 17 December 2015 11:01 AM, Krzysztof Kozlowski wrote: > On 17.11.2015 15:05, Pankaj Dubey wrote: >> In this series I am splitting up SoC specific PMU configuration data into >> mach-exynos folder itself, before moving all of them under >> drivers/soc/samsung/. Also

Re: [PATCH v5 0/8] Add support for Exynos SROM Controller driver

Hi Kukjin On Friday 23 October 2015 11:48 PM, Kukjin Kim wrote: > On 10/23/15 18:49, Pavel Fedin wrote: >> Hello! >> This patchset, I have tested on Peach-Pi (Exynos5880) based chromebook for boot and S2R functionality. >>> >>> Entire patchset tested on Trats2 (Exynos4412)

Re: [PATCH 1/2] clk: samsung: Don't build ARMv8 clock drivers on ARMv7

On Monday 16 November 2015 07:06 AM, Krzysztof Kozlowski wrote: > Currently the Exynos5433 (ARMv8 SoC) clock driver depends on ARCH_EXYNOS > so it is built also on ARMv7. This does not bring any kind of benefit. > There won't be a single kernel image for ARMv7 and ARMv8 SoCs (like > multi_v7 for

Re: [PATCH 2/2] arm64: EXYNOS: Consolidate ARCH_EXYNOS7 symbol into ARCH_EXYNOS

On Monday 16 November 2015 07:06 AM, Krzysztof Kozlowski wrote: > The ARMv8 Exynos family SoCs in Linux kernel are currently: > - Exynos5433 (controlled by ARCH_EXYNOS), > - Exynos7 (controlled by ARCH_EXYNOS7). > > It duplicates Kconfig symbols unnecessarily, so consolidate them into > one

Re: [PATCH v5 9/9] drivers: soc: Add support for Exynos PMU driver

On Saturday 14 November 2015 05:00 PM, Krzysztof Kozlowski wrote: W dniu 14.11.2015 o 00:36, Pankaj Dubey pisze: On 13 November 2015 at 15:58, Krzysztof Kozlowski wrote: On 13.11.2015 18:29, Pankaj Dubey wrote: This patch moves Exynos PMU driver implementation from "arm/mach-exynos" to

Re: [PATCH 2/2] arm64: EXYNOS: Consolidate ARCH_EXYNOS7 symbol into ARCH_EXYNOS

On Monday 16 November 2015 07:06 AM, Krzysztof Kozlowski wrote: > The ARMv8 Exynos family SoCs in Linux kernel are currently: > - Exynos5433 (controlled by ARCH_EXYNOS), > - Exynos7 (controlled by ARCH_EXYNOS7). > > It duplicates Kconfig symbols unnecessarily, so consolidate them into > one

Re: [PATCH 1/2] clk: samsung: Don't build ARMv8 clock drivers on ARMv7

On Monday 16 November 2015 07:06 AM, Krzysztof Kozlowski wrote: > Currently the Exynos5433 (ARMv8 SoC) clock driver depends on ARCH_EXYNOS > so it is built also on ARMv7. This does not bring any kind of benefit. > There won't be a single kernel image for ARMv7 and ARMv8 SoCs (like > multi_v7 for

Re: [PATCH v5 0/8] Add support for Exynos SROM Controller driver

Hi Kukjin On Friday 23 October 2015 11:48 PM, Kukjin Kim wrote: > On 10/23/15 18:49, Pavel Fedin wrote: >> Hello! >> This patchset, I have tested on Peach-Pi (Exynos5880) based chromebook for boot and S2R functionality. >>> >>> Entire patchset tested on Trats2 (Exynos4412)

Re: [PATCH v5 9/9] drivers: soc: Add support for Exynos PMU driver

On Saturday 14 November 2015 05:00 PM, Krzysztof Kozlowski wrote: W dniu 14.11.2015 o 00:36, Pankaj Dubey pisze: On 13 November 2015 at 15:58, Krzysztof Kozlowski wrote: On 13.11.2015 18:29, Pankaj Dubey wrote: This patch moves Exynos PMU driver implementation