garding this. I dont'
think the patches are accepted yet as Rob has some reservations against
the clock parents.
https://lkml.org/lkml/2014/4/9/173
--
Tushar Behera
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.o
On 04/30/2014 11:33 PM, Mark Brown wrote:
> On Wed, Apr 30, 2014 at 05:30:39PM +0530, Tushar Behera wrote:
>
>> XCLKOUT mux register (0x10040a00) is not part of core clock SFR range,
>> rather it is part of pmu-system-controller node.
>
>> One option would be to add a
On 04/30/2014 11:33 PM, Mark Brown wrote:
On Wed, Apr 30, 2014 at 05:30:39PM +0530, Tushar Behera wrote:
XCLKOUT mux register (0x10040a00) is not part of core clock SFR range,
rather it is part of pmu-system-controller node.
One option would be to add a clock provider for XCLKOUT
as Rob has some reservations against
the clock parents.
https://lkml.org/lkml/2014/4/9/173
--
Tushar Behera
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
On 04/30/2014 03:59 AM, Mark Brown wrote:
> On Fri, Apr 25, 2014 at 09:46:11AM +0530, Tushar Behera wrote:
>> On 04/24/2014 07:09 PM, Mark Brown wrote:
>
>>> defined. Why is that? Also, why is the secondary I2S playback stream
>>> not supported (this may be a reas
On 04/30/2014 03:59 AM, Mark Brown wrote:
On Fri, Apr 25, 2014 at 09:46:11AM +0530, Tushar Behera wrote:
On 04/24/2014 07:09 PM, Mark Brown wrote:
defined. Why is that? Also, why is the secondary I2S playback stream
not supported (this may be a reason to restrict to only the one I2S
t this patch, getting following error.
sound/built-in.o: In function `iis_irq':
sound/soc/samsung/idma.c:277: undefined reference to `__aeabi_uldivmod'
Tested-by: Tushar Behera
> sound/soc/samsung/idma.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/soun
: alsa-de...@alsa-project.org
---
Tested with ARM_LPAE enabled. Without this patch, getting following error.
sound/built-in.o: In function `iis_irq':
sound/soc/samsung/idma.c:277: undefined reference to `__aeabi_uldivmod'
Tested-by: Tushar Behera tushar.beh...@linaro.org
sound/soc/samsung
> - sysmmu_restore_state(client->sysmmu);
> + sysmmu_restore_state(dev);
>
> if (cb)
> ret = cb(dev);
>
> if (ret)
> - sysmmu_save_state(client->sysmmu);
> + sysmmu_restore_state(dev);
>
client is now unused, remove t
(client-sysmmu);
+ sysmmu_restore_state(dev);
client is now unused, remove the variable.
--
Tushar Behera
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
Added machine driver to instantiate I2S based sound card on Snow
board. It has MAX98095 audio codec on board.
There are some other variants for Snow board which have MAX98090
audio codec. Hence support for MAX98090 is also added to this
driver.
Signed-off-by: Tushar Behera
---
Changes for V3:
1
Added machine driver to instantiate I2S based sound card on Snow
board. It has MAX98095 audio codec on board.
There are some other variants for Snow board which have MAX98090
audio codec. Hence support for MAX98090 is also added to this
driver.
Signed-off-by: Tushar Behera tushar.beh
? If this is for PMU
> perhaps make it more explicit and name it: samsung,pmu-syscon or
> samsung,pmureg ?
>
There are already a couple of nodes (watchdog and sata) using
samsung,syscon-phandle. IMHO, we should keep only property string for
syscon node. Either we keep syscon-phandl
;, "ref";
> + samsung,pmu-syscon = <_system_controller>;
Replace samsung,pmu-syscon by samsung,syscon-phandle ?
> + samsung,pmu-offset = <0x704>;
> + #phy-cells = <1>;
> + };
> +
> usb@1211 {
>
hy";
> + reg = <0x1250 0x100>;
> + clocks = < CLK_USBD301>, < CLK_SCLK_USBPHY301>;
> + clock-names = "phy", "ref";
> + samsung,pmu-syscon = <_system_controller>;
ditto
> +
= pmu_system_controller;
ditto
+ samsung,pmu-offset = 0x708;
+ #phy-cells = 1;
+ };
};
--
Tushar Behera
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
-syscon by samsung,syscon-phandle ?
+ samsung,pmu-offset = 0x704;
+ #phy-cells = 1;
+ };
+
usb@1211 {
compatible = samsung,exynos4210-ehci;
reg = 0x1211 0x100;
--
Tushar Behera
--
To unsubscribe from this list: send
/watchdog
driver to use the modified property name.
--
Tushar Behera
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
On 04/25/2014 11:13 AM, Chanwoo Choi wrote:
> Hi,
>
> On 04/25/2014 01:30 PM, Tushar Behera wrote:
>> On 04/25/2014 06:46 AM, Chanwoo Choi wrote:
>>> This patch fix the offset of CPU boot address and don't need to send smc
>>> call
>>> of SMC_CMD_CPU1B
html
>
> What specifically is this needed for? We *should* be able to use
> deferred probe for most things, but I know that not all subsystems are
> able to yet.
>
DRM-Exynos is one such sub-system right now that doesn't handle deferred
probe well. That is one of the reasons for this p
> arch/arm/boot/dts/exynos3250.dtsi | 405 +
> arch/arm/boot/dts/exynos4212-tizenw.dts | 926
> ++
exynos4412-tizenw.dts related changes are unrelated.
--
Tushar Behera
--
To unsubscribe from this list: send the line "
ddr(int cpu, unsigned long
> boot_addr)
> {
> void __iomem *boot_reg = S5P_VA_SYSRAM_NS + 0x1c;
>
> - if (!soc_is_exynos4212())
> + if (!soc_is_exynos4212() && !soc_is_exynos3250())
> boot_reg += 4*cpu;
>
> __raw_writel(boot_addr, boot_r
On 04/24/2014 07:09 PM, Mark Brown wrote:
> On Wed, Apr 23, 2014 at 02:31:45PM +0530, Tushar Behera wrote:
>
>> +Required properties:
>> +- compatible : Can be one of the following,
>> +"google,snow-audio-max98090" or
>> +
On 04/24/2014 04:18 PM, Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
>
> On Monday, April 14, 2014 11:08:15 AM Tushar Behera wrote:
>> Currently the threshold limits are updated in 2 stages, once for all
>> software trigger levels and again for hardware trip point.
>>
On 04/24/2014 04:18 PM, Bartlomiej Zolnierkiewicz wrote:
Hi,
On Monday, April 14, 2014 11:08:15 AM Tushar Behera wrote:
Currently the threshold limits are updated in 2 stages, once for all
software trigger levels and again for hardware trip point.
While updating the software trigger
On 04/24/2014 07:09 PM, Mark Brown wrote:
On Wed, Apr 23, 2014 at 02:31:45PM +0530, Tushar Behera wrote:
+Required properties:
+- compatible : Can be one of the following,
+google,snow-audio-max98090 or
+google,snow-audio-max98095
+- samsung,i2s
;
- if (!soc_is_exynos4212())
+ if (!soc_is_exynos4212() !soc_is_exynos3250())
boot_reg += 4*cpu;
__raw_writel(boot_addr, boot_reg);
--
Tushar Behera
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord
+++
arch/arm/boot/dts/exynos3250.dtsi | 405 +
arch/arm/boot/dts/exynos4212-tizenw.dts | 926
++
exynos4412-tizenw.dts related changes are unrelated.
--
Tushar Behera
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
* be able to use
deferred probe for most things, but I know that not all subsystems are
able to yet.
DRM-Exynos is one such sub-system right now that doesn't handle deferred
probe well. That is one of the reasons for this patch.
--
Tushar Behera
--
To unsubscribe from this list: send the line
On 04/25/2014 11:13 AM, Chanwoo Choi wrote:
Hi,
On 04/25/2014 01:30 PM, Tushar Behera wrote:
On 04/25/2014 06:46 AM, Chanwoo Choi wrote:
This patch fix the offset of CPU boot address and don't need to send smc
call
of SMC_CMD_CPU1BOOT command for secondary CPU boot because Exynos3250
On 04/14/2014 11:08 AM, Tushar Behera wrote:
> Currently the threshold limits are updated in 2 stages, once for all
> software trigger levels and again for hardware trip point.
>
> While updating the software trigger levels, it overwrites the threshold
> limit for hardware tri
Create an explicit of_match_table entry for MAX98095 codec. Also
add a binding Documentation for this compatible string.
Signed-off-by: Tushar Behera
---
.../devicetree/bindings/sound/max98095.txt | 16
sound/soc/codecs/max98095.c|7
Added machine driver to instantiate I2S based sound card on Snow
board. It has MAX98095 audio codec on board.
There are some other variants for Snow board which have MAX98090
audio codec. Hence support for MAX98090 is also added to this
driver.
Signed-off-by: Tushar Behera
---
Changes for V2
DAI probe.
If both these conditions are true, then I2S clock remains unconfigured
during audio playback. Fix this by removing the code to clear
rclk_srcrate in i2s_startup. Instead, reset this during DAI probe.
Signed-off-by: Tushar Behera
---
The patch is based on v3.15-rc2.
sound/soc/samsung
On 04/14/2014 11:08 AM, Tushar Behera wrote:
Currently the threshold limits are updated in 2 stages, once for all
software trigger levels and again for hardware trip point.
While updating the software trigger levels, it overwrites the threshold
limit for hardware trip point thereby forcing
DAI probe.
If both these conditions are true, then I2S clock remains unconfigured
during audio playback. Fix this by removing the code to clear
rclk_srcrate in i2s_startup. Instead, reset this during DAI probe.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
The patch is based on v3.15
Added machine driver to instantiate I2S based sound card on Snow
board. It has MAX98095 audio codec on board.
There are some other variants for Snow board which have MAX98090
audio codec. Hence support for MAX98090 is also added to this
driver.
Signed-off-by: Tushar Behera tushar.beh
Create an explicit of_match_table entry for MAX98095 codec. Also
add a binding Documentation for this compatible string.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
.../devicetree/bindings/sound/max98095.txt | 16
sound/soc/codecs/max98095.c
this list: send the line "unsubscribe linux-samsung-soc"
> in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Tushar Behera
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
info at http://vger.kernel.org/majordomo-info.html
--
Tushar Behera
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
.
Updating only the required fields in threshold register fixes this issue.
Signed-off-by: Tushar Behera
---
Based on v3.15-rc1.
drivers/thermal/samsung/exynos_tmu.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/thermal/samsung/exynos_tmu.c
b/drivers/thermal/samsung
.
Updating only the required fields in threshold register fixes this issue.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
Based on v3.15-rc1.
drivers/thermal/samsung/exynos_tmu.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/thermal/samsung/exynos_tmu.c
b/drivers
On 28 March 2014 15:52, Mark Brown wrote:
> On Fri, Mar 28, 2014 at 10:50:22AM +0530, Tushar Behera wrote:
>> Keep all regulators already enabled by bootloader on, even if no
>> driver has claimed them. This is useful for debug and development, but
>> should not be
On 28 March 2014 15:52, Mark Brown broo...@kernel.org wrote:
On Fri, Mar 28, 2014 at 10:50:22AM +0530, Tushar Behera wrote:
Keep all regulators already enabled by bootloader on, even if no
driver has claimed them. This is useful for debug and development, but
should not be needed on a platform
Keep all regulators already enabled by bootloader on, even if no
driver has claimed them. This is useful for debug and development, but
should not be needed on a platform with proper driver support.
Signed-off-by: Tushar Behera
CC: Mark Brown
---
Documentation/kernel-parameters.txt |8
These patches take inspiration from Olof's following patch.
1e435256d625 "clk: add clk_ignore_unused option to keep boot clocks on"
This options are solely for debug purposes to figure out whether
the issue at hand is because of improper shutdown of regulators or
power-domains.
Tushar
Keep all power-domains already enabled by bootloader on, even if no
driver has claimed them. This is useful for debug and development, but
should not be needed on a platform with proper driver support.
Signed-off-by: Tushar Behera
CC: "Rafael J. Wysocki"
CC: linux...@vger.
These patches take inspiration from Olof's following patch.
1e435256d625 clk: add clk_ignore_unused option to keep boot clocks on
This options are solely for debug purposes to figure out whether
the issue at hand is because of improper shutdown of regulators or
power-domains.
Tushar Behera (2
Keep all power-domains already enabled by bootloader on, even if no
driver has claimed them. This is useful for debug and development, but
should not be needed on a platform with proper driver support.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
CC: Rafael J. Wysocki r...@rjwysocki.net
Keep all regulators already enabled by bootloader on, even if no
driver has claimed them. This is useful for debug and development, but
should not be needed on a platform with proper driver support.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
CC: Mark Brown broo...@kernel.org
On 27 February 2014 02:41, Mike Turquette wrote:
> Quoting Tushar Behera (2014-02-18 22:24:34)
>> S5M8767 chip has 3 crystal oscillators which are operated in the same
>> as the crystal oscillators in S2MPS11. Extend s2mps11-clk driver to
>> support clocks in S5M87
On 27 February 2014 02:41, Mike Turquette mturque...@linaro.org wrote:
Quoting Tushar Behera (2014-02-18 22:24:34)
S5M8767 chip has 3 crystal oscillators which are operated in the same
as the crystal oscillators in S2MPS11. Extend s2mps11-clk driver to
support clocks in S5M8767.
The patches
Since clock operation within S2MPS11 and S5M8767 are similar, we can
support both the devices within a single driver.
Signed-off-by: Tushar Behera
Reviewed-by: Tomasz Figa
Reviewed-by: Yadwinder Singh Brar
---
drivers/clk/Kconfig |6 --
drivers/clk/clk-s2mps11.c |5 +
2
S5M8767 chip has 3 crystal oscillators which are operated in the same
as the crystal oscillators in S2MPS11. Extend s2mps11-clk driver to
support clocks in S5M8767.
The patches are rebased on top of next-20130218.
Tushar Behera (2):
clk: clk-s2mps11: Refactor for including support for other
The clocks in S2MPS11 and S5M8767 are managed in the same way, baring
a difference in the register offset. It would be better to update
existing S2MPS11 driver to support the clocks in S5M8767, rather than
to create an almost duplicate driver altogether.
Signed-off-by: Tushar Behera
Reviewed
S5M8767 chip has 3 crystal oscillators which are operated in the same
as the crystal oscillators in S2MPS11. Extend s2mps11-clk driver to
support clocks in S5M8767.
The patches are rebased on top of next-20130218.
Tushar Behera (2):
clk: clk-s2mps11: Refactor for including support for other
The clocks in S2MPS11 and S5M8767 are managed in the same way, baring
a difference in the register offset. It would be better to update
existing S2MPS11 driver to support the clocks in S5M8767, rather than
to create an almost duplicate driver altogether.
Signed-off-by: Tushar Behera tushar.beh
Since clock operation within S2MPS11 and S5M8767 are similar, we can
support both the devices within a single driver.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
Reviewed-by: Tomasz Figa t.f...@samsung.com
Reviewed-by: Yadwinder Singh Brar yadi.b...@samsung.com
---
drivers/clk/Kconfig
On 20 January 2014 15:35, Russell King - ARM Linux
wrote:
> On Mon, Jan 20, 2014 at 02:32:34PM +0530, Tushar Behera wrote:
>> uart_register_driver call binds the driver to a specific device
>> node through tty_register_driver call. This should typically happen
>> dur
if multiple serial drivers with same default major/minor numbers are
included in the kernel.
A typical case is observed with amba-pl011 and samsung-uart drivers.
Signed-off-by: Tushar Behera
---
drivers/tty/serial/samsung.c | 40 +++-
1 file changed, 11
if multiple serial drivers with same default major/minor numbers are
included in the kernel.
A typical case is observed with amba-pl011 and samsung-uart drivers.
Signed-off-by: Tushar Behera
---
drivers/tty/serial/amba-pl011.c | 21 -
1 file changed, 12 insertions(+), 9
because they were breaking userspace
interface.
Iteration 3:
uart_register_driver call binds the driver to a specific device
node through tty_driver_register call. This is moved to device probe call.
Tushar Behera (2):
serial: samsung: Move uart_register_driver call to device probe
serial: pl011
On 20 January 2014 15:35, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Mon, Jan 20, 2014 at 02:32:34PM +0530, Tushar Behera wrote:
uart_register_driver call binds the driver to a specific device
node through tty_register_driver call. This should typically happen
during device
because they were breaking userspace
interface.
Iteration 3:
uart_register_driver call binds the driver to a specific device
node through tty_driver_register call. This is moved to device probe call.
Tushar Behera (2):
serial: samsung: Move uart_register_driver call to device probe
serial: pl011
if multiple serial drivers with same default major/minor numbers are
included in the kernel.
A typical case is observed with amba-pl011 and samsung-uart drivers.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
drivers/tty/serial/samsung.c | 40 +++-
1
if multiple serial drivers with same default major/minor numbers are
included in the kernel.
A typical case is observed with amba-pl011 and samsung-uart drivers.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
drivers/tty/serial/amba-pl011.c | 21 -
1 file changed
;
Ok. I will prepare a patch with this approach for amba-pl011 and
samsung-uart drivers. If that works well, I will extend that to other
serial drivers.
Thanks to both of you for your time.
--
Tushar Behera
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
-pl011 and
samsung-uart drivers. If that works well, I will extend that to other
serial drivers.
Thanks to both of you for your time.
--
Tushar Behera
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info
of samsung-uart driver fails because the desired
node is busy.
The issue is fixed by adding a fallback in driver core, so that we can
use dynamic major number in case device node allocation fails for
hard-coded major/minor number.
Signed-off-by: Tushar Behera
---
Hi Greg,
This is my second attempt
of samsung-uart driver fails because the desired
node is busy.
The issue is fixed by adding a fallback in driver core, so that we can
use dynamic major number in case device node allocation fails for
hard-coded major/minor number.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
Hi Greg
xx.c:100:2: error: implicit declaration of
function ‘s3c_gpio_setpull’ [-Werror=implicit-function-declaration]
Signed-off-by: Tushar Behera
---
Changes for V2:
* Updated commit message
Bryan,
I should have been more explicit regarding this patch. This patch fixes
build error on linux-next after the a
On 3 January 2014 04:12, Bryan Wu wrote:
> On Mon, Dec 30, 2013 at 1:09 AM, Tushar Behera
> wrote:
>> Fixes following build error.
>> drivers/leds/leds-s3c24xx.c: In function ‘s3c24xx_led_probe’:
>> drivers/leds/leds-s3c24xx.c:100:2: error: implicit declaration of
>&
On 3 January 2014 04:12, Bryan Wu coolo...@gmail.com wrote:
On Mon, Dec 30, 2013 at 1:09 AM, Tushar Behera tushar.beh...@linaro.org
wrote:
Fixes following build error.
drivers/leds/leds-s3c24xx.c: In function ‘s3c24xx_led_probe’:
drivers/leds/leds-s3c24xx.c:100:2: error: implicit declaration
:100:2: error: implicit declaration of
function ‘s3c_gpio_setpull’ [-Werror=implicit-function-declaration]
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
Changes for V2:
* Updated commit message
Bryan,
I should have been more explicit regarding this patch. This patch fixes
build error
Fixes following build error.
drivers/leds/leds-s3c24xx.c: In function ‘s3c24xx_led_probe’:
drivers/leds/leds-s3c24xx.c:100:2: error: implicit declaration of
function ‘s3c_gpio_setpull’ [-Werror=implicit-function-declaration]
Signed-off-by: Tushar Behera
---
Tested at next-20131224.
drivers
Fixes following build error.
drivers/leds/leds-s3c24xx.c: In function ‘s3c24xx_led_probe’:
drivers/leds/leds-s3c24xx.c:100:2: error: implicit declaration of
function ‘s3c_gpio_setpull’ [-Werror=implicit-function-declaration]
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
Tested at next
On 30 December 2013 03:47, Mike Turquette wrote:
> Quoting Tushar Behera (2013-12-26 02:18:58)
>> The clocks in S2MPS11 and S5M8767 are managed in the same way, baring
>> a difference in the register offset. It would be better to update
>> existing S2MPS11 driver to support
On 30 December 2013 03:47, Mike Turquette mturque...@linaro.org wrote:
Quoting Tushar Behera (2013-12-26 02:18:58)
The clocks in S2MPS11 and S5M8767 are managed in the same way, baring
a difference in the register offset. It would be better to update
existing S2MPS11 driver to support
On 27 December 2013 12:08, Greg KH wrote:
> On Fri, Dec 27, 2013 at 12:00:20PM +0530, Tushar Behera wrote:
>> On 27 December 2013 10:48, Greg KH wrote:
>> > On Fri, Dec 27, 2013 at 10:37:28AM +0530, Tushar Behera wrote:
[ ... ]
>> >> @@ -951,8 +949,
On 27 December 2013 12:08, Greg KH gre...@linuxfoundation.org wrote:
On Fri, Dec 27, 2013 at 12:00:20PM +0530, Tushar Behera wrote:
On 27 December 2013 10:48, Greg KH gre...@linuxfoundation.org wrote:
On Fri, Dec 27, 2013 at 10:37:28AM +0530, Tushar Behera wrote:
[ ... ]
@@ -951,8 +949,6
On 27 December 2013 10:48, Greg KH wrote:
> On Fri, Dec 27, 2013 at 10:37:28AM +0530, Tushar Behera wrote:
>> The hard-coded values clash with the values set for amba-pl011 serial
>> driver. Because of this there is no serial output on Samsung boards
>> if amba-pl011 is enab
. This is required for multi-platform
development work on Exynos platform.
Signed-off-by: Tushar Behera
---
drivers/tty/serial/samsung.c |4
1 file changed, 4 deletions(-)
diff --git a/drivers/tty/serial/samsung.c b/drivers/tty/serial/samsung.c
index c1af04d..9c20543 100644
--- a/drivers/tty
No functional change, adding for uniformity.
Signed-off-by: Tushar Behera
---
drivers/irqchip/irq-s3c24xx.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/irqchip/irq-s3c24xx.c b/drivers/irqchip/irq-s3c24xx.c
index bbcc944..ee41ae2 100644
--- a/drivers
S5M8767 chip has 3 crystal oscillators which are operated in the same
as the crystal oscillators in S2MPS11. Extend s2mps11-clk driver to
support clocks in S5M8767.
The earlier set of patches no longer apply cleanly on linux-next, hence
rebased them on top of next-20131224.
Tushar Behera (4
The clocks in S2MPS11 and S5M8767 are managed in the same way, baring
a difference in the register offset. It would be better to update
existing S2MPS11 driver to support the clocks in S5M8767, rather than
creating an almost duplicate driver altogether.
Signed-off-by: Tushar Behera
Reviewed
S5M8767 chip has 3 crystal oscillators running at 32KHz. These are
supported by s2mps11-clk driver.
Signed-off-by: Tushar Behera
Reviewed-by: Tomasz Figa
CC: Lee Jones
---
drivers/mfd/sec-core.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/mfd/sec-core.c b
Signed-off-by: Tushar Behera
Reviewed-by: Tomasz Figa
---
arch/arm/boot/dts/exynos5250-arndale.dts |7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250-arndale.dts
b/arch/arm/boot/dts/exynos5250-arndale.dts
index b42e658..3bb730d 100644
--- a/arch/arm/boot
Since clock operation within S2MPS11 and S5M8767 are similar, we can
support both the devices within a single driver.
Signed-off-by: Tushar Behera
Reviewed-by: Tomasz Figa
Reviewed-by: Yadwinder Singh Brar
CC: Mike Turquette
---
drivers/clk/Kconfig |6 --
drivers/clk/clk
No functional change, adding for uniformity.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
drivers/irqchip/irq-s3c24xx.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/irqchip/irq-s3c24xx.c b/drivers/irqchip/irq-s3c24xx.c
index bbcc944..ee41ae2
. This is required for multi-platform
development work on Exynos platform.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
drivers/tty/serial/samsung.c |4
1 file changed, 4 deletions(-)
diff --git a/drivers/tty/serial/samsung.c b/drivers/tty/serial/samsung.c
index c1af04d..9c20543 100644
On 27 December 2013 10:48, Greg KH gre...@linuxfoundation.org wrote:
On Fri, Dec 27, 2013 at 10:37:28AM +0530, Tushar Behera wrote:
The hard-coded values clash with the values set for amba-pl011 serial
driver. Because of this there is no serial output on Samsung boards
if amba-pl011 is enabled
Since clock operation within S2MPS11 and S5M8767 are similar, we can
support both the devices within a single driver.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
Reviewed-by: Tomasz Figa t.f...@samsung.com
Reviewed-by: Yadwinder Singh Brar yadi.b...@samsung.com
CC: Mike Turquette
The clocks in S2MPS11 and S5M8767 are managed in the same way, baring
a difference in the register offset. It would be better to update
existing S2MPS11 driver to support the clocks in S5M8767, rather than
creating an almost duplicate driver altogether.
Signed-off-by: Tushar Behera tushar.beh
S5M8767 chip has 3 crystal oscillators running at 32KHz. These are
supported by s2mps11-clk driver.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
Reviewed-by: Tomasz Figa t.f...@samsung.com
CC: Lee Jones lee.jo...@linaro.org
---
drivers/mfd/sec-core.c |4 +++-
1 file changed, 3
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
Reviewed-by: Tomasz Figa t.f...@samsung.com
---
arch/arm/boot/dts/exynos5250-arndale.dts |7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250-arndale.dts
b/arch/arm/boot/dts/exynos5250-arndale.dts
index
S5M8767 chip has 3 crystal oscillators which are operated in the same
as the crystal oscillators in S2MPS11. Extend s2mps11-clk driver to
support clocks in S5M8767.
The earlier set of patches no longer apply cleanly on linux-next, hence
rebased them on top of next-20131224.
Tushar Behera (4
On 11 November 2013 08:28, Tushar Behera wrote:
> On 10 November 2013 18:04, Tomasz Figa wrote:
>> Hi Tushar,
>>
>> On Thursday 31 of October 2013 12:18:40 Tushar Behera wrote:
>>> S5M8767 chip has 3 crystal oscillators which are operated in the same
>>>
On 11 November 2013 08:28, Tushar Behera tushar.beh...@linaro.org wrote:
On 10 November 2013 18:04, Tomasz Figa tomasz.f...@gmail.com wrote:
Hi Tushar,
On Thursday 31 of October 2013 12:18:40 Tushar Behera wrote:
S5M8767 chip has 3 crystal oscillators which are operated in the same
On 10 November 2013 18:04, Tomasz Figa wrote:
> Hi Tushar,
>
> On Thursday 31 of October 2013 12:18:40 Tushar Behera wrote:
>> S5M8767 chip has 3 crystal oscillators which are operated in the same
>> as the crystal oscillators in S2MPS11. Extend s2mps11-clk driver to
>>
On 10 November 2013 18:04, Tomasz Figa tomasz.f...@gmail.com wrote:
Hi Tushar,
On Thursday 31 of October 2013 12:18:40 Tushar Behera wrote:
S5M8767 chip has 3 crystal oscillators which are operated in the same
as the crystal oscillators in S2MPS11. Extend s2mps11-clk driver to
support clocks
201 - 300 of 754 matches
Mail list logo
