Quoting Tushar Behera (2013-06-20 03:47:16)
> cpufreq driver for EXYNOS4 based SoCs are not platform drivers, hence
> we cannot currently pass the clock names through a device tree node.
> Instead, we need to make them available through global alias.
>
> The patches are based on next-20130618.
>
Quoting Tomasz Figa (2013-06-21 00:09:27)
> On Friday 21 of June 2013 10:18:01 Vikas Sajjan wrote:
> > Hi Mr. Kim,
> >
> > On Thu, Jun 20, 2013 at 3:37 PM, Yadwinder Singh Brar
> >
> > wrote:
> > > Hi Tomasz,
> > >
> > > On Thu, Jun 20, 2013 at 3:30 PM, Tomasz Figa
> wrote:
> > >> Hi Yadwinde
On Fri, Jun 21, 2013 at 8:49 PM, amit daniel kachhap
wrote:
> Hi,
>
> On Thu, Jun 20, 2013 at 7:48 AM, Eduardo Valentin
> wrote:
>> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>>> This patch adds configuration data for exynos5440 soc. Also register
>>> definations for the controller are added
Hi,
On Thu, Jun 20, 2013 at 7:48 AM, Eduardo Valentin
wrote:
> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>> This patch adds configuration data for exynos5440 soc. Also register
>> definations for the controller are added.
>>
>> Acked-by: Jonghwa Lee
>> Acked-by: Kukjin Kim
>> Signed-off-b
Hi Eduardo,
On Thu, Jun 20, 2013 at 7:36 AM, Eduardo Valentin
wrote:
> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>> This patch modifies TMU controller to add changes needed to work with
>> exynos5440 platform. This sensor registers 3 instance of the tmu controller
>> with the thermal zone a
On Fri, Jun 21, 2013 at 02:33:37PM +0200, Tomasz Figa wrote:
> + - EN32KHz AP: 32KHz clock output for application processor
> + - EN32KHz CP: 32KHz clock output for call processor
The clocks should be supported using the clock API not the regulator
API, they shouldn't be present in the DT
On Fri, Jun 21, 2013 at 02:33:36PM +0200, Tomasz Figa wrote:
> This patch modifies the platform data of max8998 to use arrays for
> specifying predefined voltages of buck1 and buck2 instead of separate
> field for each voltage.
>
> This allows to simplify the code a bit and will help in adding sup
On 21-06-2013 08:30, amit daniel kachhap wrote:
> Hi
>
> On Thu, Jun 20, 2013 at 4:33 AM, Eduardo Valentin
> wrote:
>> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>>> This code simplifies the zone handling to use the trip information passed
>>> by the TMU driver and not the hardcoded macros.
On Thu, Jun 20, 2013 at 5:15 AM, Eduardo Valentin
wrote:
> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>> From: Lukasz Majewski
>>
>> Proper description for Exynos4 bindings added to Documentation/devicetree/
>> bindings
>>
>> Acked-by: Jonghwa Lee
>> Signed-off-by: Lukasz Majewski
>> Signe
On 20-06-2013 22:01, amit daniel kachhap wrote:
> Hi Eduardo,
>
> On Thu, Jun 20, 2013 at 1:25 AM, Eduardo Valentin
> wrote:
>> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>>> This patch adds some extra register bitfield definations and cleans
>>> up the code to prepare for moving register ma
On Fri, Jun 21, 2013 at 02:33:35PM +0200, Tomasz Figa wrote:
> The reverse mapping method used is linear mapping since the sub-drivers
> of max8998 such as regulator and charger drivers can use the max8998
> irq_domain to get the virtual irq number for max8998 interrupts.
> All uses of irq_base i
On 20-06-2013 21:50, amit daniel kachhap wrote:
> On Thu, Jun 20, 2013 at 12:15 AM, Eduardo Valentin
> wrote:
>> Amit,
>>
>> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>>> This code bifurcates exynos thermal implementation into common and sensor
>>> specific parts. The common thermal code int
On 21-06-2013 08:46, amit daniel kachhap wrote:
> Hi Eduardo,
>
> On Thu, Jun 20, 2013 at 4:57 AM, Eduardo Valentin
> wrote:
>> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>>> This patch adds support to handle multiple instances of the TMU controllers.
>>> This is done by removing the static
On 21-06-2013 04:50, amit daniel kachhap wrote:
> Hi,
>
> On Thu, Jun 20, 2013 at 2:22 AM, Eduardo Valentin
> wrote:
>> On 19-06-2013 16:19, Eduardo Valentin wrote:
>>> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
This patch adds entries min_efuse_value, max_efuse_value,
default_tem
On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
> This code bifurcates exynos thermal implementation into common and sensor
> specific parts. The common thermal code interacts with core thermal layer and
> core cpufreq cooling parts and is independent of SOC specific driver. This
> change is needed
Tomasz Figa writes:
> All uses of irq_base in platform data and max8997 driver private data
> are removed.
>
[...]
> +static int max8998_irq_domain_map(struct irq_domain *d, unsigned int irq,
> + irq_hw_number_t hw)
> +{
> + struct max8997_dev *max8998 = d-
On Friday 21 June 2013, Jason Cooper wrote:
> On Fri, Jun 21, 2013 at 10:30:47AM +0200, Arnd Bergmann wrote:
> > On Friday 21 June 2013, Thomas Petazzoni wrote:
> > > I am by far not an expert on how to solve merge strategies and so on,
> > > but to avoid conflicts at Linus's level while merging th
On Fri, Jun 21, 2013 at 10:30:47AM +0200, Arnd Bergmann wrote:
> On Friday 21 June 2013, Thomas Petazzoni wrote:
> > I am by far not an expert on how to solve merge strategies and so on,
> > but to avoid conflicts at Linus's level while merging the arm-soc and
> > pci trees, it would be better if t
On Friday 21 June 2013, Tomasz Figa wrote:
> > To me, this new hook is strictly equivalent to init_irq. What do we gain
> > exactly? I didn't think init_irq was going away...
> >
> > I know init_irq is not pretty, and we tend to overload it with other
> > stuff, but I don't really see the point o
On Friday 21 June 2013, Tomasz Figa wrote:
> Since we now have a proper Samsung PWM clocksource driver in place,
> we can proceed with further cleanup of PWM timers support on Samsung SoCs.
>
> This series attempts to achieve this goal by:
> 1) moving remaining Samsung platforms to the new clocks
This change is mainly to update the driver's path changed from
drivers/media/platform/s5p-fimc to drivers/media/platform/exynos4-is/.
While at it, remove non-existent files rule, move the whole entry to
the Samsung drivers section and add the patch tracking system URL
and git repository details.
S
On Tuesday 18 June 2013, Kukjin Kim wrote:
> The following changes since commit 79d743c177f99d6854e152d9e7fac5bbbeb7c25e:
>
>clk: exynos5250: Add enum entries for divider clock of i2s1 and i2s2
> (2013-06-19 03:28:43 +0900)
>
> are available in the git repository at:
>
>git://git.kernel
This patch enables the front camera using the internal
camera ISP (FIMC-IS).
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
arch/arm/boot/dts/exynos4412-trats2.dts | 91 +++
1 file changed, 91 insertions(+)
diff --git a/arch/arm/boot/dts/exynos
From: Jacek Anaszewski
This patch adds AK8975 magnetometer node and corresponding
i2c-gpio bus node for TRATS2 board.
Signed-off-by: Jacek Anaszewski
Signed-off-by: Kyungmin Park
Signed-off-by: Sylwester Nawrocki
---
arch/arm/boot/dts/exynos4412-trats2.dts | 15 +++
1 file chan
The ISP power domain is a common power domain for FIMC-LITE
and FIMC-IS (camera ISP) devices.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
arch/arm/boot/dts/exynos4x12.dtsi |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4x12.dtsi
b/arc
Add common camera node and Exynos4212/4412 specific nodes for
FIMC, MIPI-CSIS, FIMC-LITE and FIMC-IS devices.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
arch/arm/boot/dts/exynos4x12.dtsi | 118 +
1 file changed, 118 insertions(+)
dif
Add pinctrl nodes for the ISP I2C0, ISP I2C1 and ISP UART devices.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
arch/arm/boot/dts/exynos4x12-pinctrl.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4x12-pinctrl.dtsi
This patch adds common FIMC and MIPI CSIS device nodes for Exynos4 SoCs.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park ;
};
+ camera {
+ compatible = "samsung,fimc", "simple-bus";
+ status = "disabled";
+ #address-cells =
The Exynos4 SPI controller uses the PL330 DMA controller which has
migrated to the generic DMA bindings since commit b5be04d35dbb2e00
"spi: s3c64xx: Modify SPI driver to use generic DMA DT support".
Use the generic bindings to specify the corresponding DMA to make
the SPI usable again on Exynos4x12
Add separate nodes for the CAMCLK pin and turn off pull-up on camera
ports A, B. The video bus pins and the clock output (CAMCLK) pin need
separate nodes since full camera port is not used in some configurations,
e.g. for MIPI CSI-2 bus only CAMCLK is required and data/clock signal
use separate ded
This patch series includes some fixes and extensions to the Exynos
dts files to add the camera and barometer sensor support for TRATS2
board. It depends on a patch from Tomasz adding initial TRATS2
board dts file [1].
[1] http://www.spinics.net/lists/arm-kernel/msg253184.html
Jacek Anaszewski (1)
Hi Eduardo,
On Thu, Jun 20, 2013 at 4:57 AM, Eduardo Valentin
wrote:
> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>> This patch adds support to handle multiple instances of the TMU controllers.
>> This is done by removing the static structure to register with the core
>> thermal
>> and crea
This patch modifies the platform data of max8998 to use arrays for
specifying predefined voltages of buck1 and buck2 instead of separate
field for each voltage.
This allows to simplify the code a bit and will help in adding support
for Device Tree, which will be introduced in further patch.
Signe
This patch adds irq domain support for max8998 interrupts.
The reverse mapping method used is linear mapping since the sub-drivers
of max8998 such as regulator and charger drivers can use the max8998
irq_domain to get the virtual irq number for max8998 interrupts.
All uses of irq_base in platform
This patch adds Device Tree support to max8998 driver.
Signed-off-by: Tomasz Figa
Signed-off-by: Kyungmin Park
---
Documentation/devicetree/bindings/mfd/max8998.txt | 111 +++
drivers/mfd/max8998.c | 75 +-
drivers/regulator/max8998.c
This series adds Device Tree support to max8998 MFD driver.
First patch reworks max8998-irq driver to use IRQ domains. Second patch
prepares platform data structure to ease generating it at runtime from
data parsed from device tree. Third patch implements Device Tree
binding and adds necessary doc
Hi
On Thu, Jun 20, 2013 at 4:33 AM, Eduardo Valentin
wrote:
> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>> This code simplifies the zone handling to use the trip information passed
>> by the TMU driver and not the hardcoded macros. This also helps in adding
>> more zone support.
>>
>> Acked
Hi Marc,
On Friday 21 of June 2013 11:24:52 Marc Zyngier wrote:
> On 21/06/13 01:35, Tomasz Figa wrote:
>
> Hi Tomasz,
>
> > Most ARM platforms have parts that should be initialized as early as
> > possible, which usually means as soon as memory management (kmalloc,
> > ioremap) starts to work,
On 21/06/13 01:35, Tomasz Figa wrote:
Hi Tomasz,
> Most ARM platforms have parts that should be initialized as early as
> possible, which usually means as soon as memory management (kmalloc,
> ioremap) starts to work,
>
> However, currently there is no appropriate callback in machine_desc
> stru
On Thu, Jun 20, 2013 at 02:14:53PM +0300, Phil Carmody wrote:
> With my language-lawyer hat on, I'd suggest ``(get_signal)'' to prevent the
> macro expansion:
Right, which the patch I posted in the mail was doing IIRC.
> However, it's more tempting (i.e. sensible) to just rename the
> one with
Hi,
On Thu, Jun 20, 2013 at 2:22 AM, Eduardo Valentin
wrote:
> On 19-06-2013 16:19, Eduardo Valentin wrote:
>> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>>> This patch adds entries min_efuse_value, max_efuse_value,
>>> default_temp_offset,
>>> trigger_type, cal_type, trim_first_point, trim
On Friday 21 June 2013, Thomas Petazzoni wrote:
> I am by far not an expert on how to solve merge strategies and so on,
> but to avoid conflicts at Linus's level while merging the arm-soc and
> pci trees, it would be better if this Samsung PCIe driver could go
> through arm-soc (with Bjorn ACK, of
Dear Arnd Bergmann,
On Fri, 21 Jun 2013 09:31:58 +0200, Arnd Bergmann wrote:
> Bjorn, are you still considering to merge this for 3.11 or have you
> closed your tree for the merge window? I think it would be good to get
> it in.
Note that the of/pci changes needed for this driver are merged thro
On Friday 21 June 2013, Kukjin Kim wrote:
> > I'll probably have to create a next/soc2 branch, but
> > will first try to merge the Renesas pull requests, which may have
> > similar problems.
> >
> > If it's possible to rebase this one not to have any dependencies
> > other than the branches merged
On Friday 21 June 2013, Jingoo Han wrote:
> Changes between v9 and v10:
> * Changed the file name from 'pci-designware.c' to 'pcie-designware.c'
> guided by Pratyush Anand, because synopsis pcie and pci controllers
> are different.
> * Fixed the typos of document, reported by Sachin Kam
Exynos5440 has two PCIe controllers which can be used as root complex
for PCIe interface.
Signed-off-by: Jingoo Han
Acked-by: Arnd Bergmann
---
arch/arm/boot/dts/exynos5440.dtsi | 38 +
1 file changed, 38 insertions(+)
diff --git a/arch/arm/boot/dts/exynos
This patch adds pcie controller node for exynos5440-ssdk5440,
and also adds a phandle for pin controller node.
Signed-off-by: Jingoo Han
Acked-by: Arnd Bergmann
---
arch/arm/boot/dts/exynos5440-ssdk5440.dts |8
arch/arm/boot/dts/exynos5440.dtsi |2 +-
2 files changed, 9
Enable PCIe support for Exynos5440 which has two PCIe controllers.
Signed-off-by: Jingoo Han
---
arch/arm/Kconfig |1 +
arch/arm/mach-exynos/Kconfig |2 ++
2 files changed, 3 insertions(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index ca30d75..421ce68 100644
--- a/a
Exynos5440 has a PCIe controller which can be used as Root Complex.
This driver supports a PCIe controller as Root Complex mode.
Signed-off-by: Surendranath Gurivireddy Balla
Signed-off-by: Siva Reddy Kallam
Signed-off-by: Jingoo Han
Acked-by: Arnd Bergmann
---
.../devicetree/bindings/pci/des
Hi,
This series of patches introduces PCIe support for Samsung Exynos5440,
and is based on the latest 'linux-next' tree (20130620).
These patches was tested with Intel e1000e LAN card on Exynos5440.
This PATCH v10 follows:
* PATCH v9, sent on June, 21st 2013
* PATCH v8, sent on June, 20th 2013
Hi Sylwester,
On Fri, Jun 21, 2013 at 4:16 AM, Sylwester Nawrocki
wrote:
> Guys, I was wondering how difficult would be to make a common driver
> for the Exynos4 and Exynos5 FIMC-IS ? My feeling is that it would allow
> to save significant amount of code, since the hardware has many
> similaritie
On Friday 21 of June 2013 10:18:01 Vikas Sajjan wrote:
> Hi Mr. Kim,
>
> On Thu, Jun 20, 2013 at 3:37 PM, Yadwinder Singh Brar
>
> wrote:
> > Hi Tomasz,
> >
> > On Thu, Jun 20, 2013 at 3:30 PM, Tomasz Figa
wrote:
> >> Hi Yadwinder, Vikas,
> >>
> >> On Tuesday 11 of June 2013 15:01:05 Yadwind
52 matches
Mail list logo
