On 2014년 09월 10일 19:24, Andrzej Hajda wrote:
Hi Inki,
To test it properly I have to fix init/remove bugs [1].
Of course these bugs were not introduced by this patch,
but they prevented some basic tests.
I had tested my patch with trats2 board, and works well without below
patch set. hm.. it
On 09/11/2014 08:37 AM, Inki Dae wrote:
On 2014년 09월 10일 19:24, Andrzej Hajda wrote:
Hi Inki,
To test it properly I have to fix init/remove bugs [1].
Of course these bugs were not introduced by this patch,
but they prevented some basic tests.
I had tested my patch with trats2 board, and
Hey Lee,
On Wed, 2014-09-10 at 10:28 +0100, Lee Jones wrote:
On Tue, 09 Sep 2014, Javier Martinez Canillas wrote:
[adding Lee Jones to cc list since I'm referring on a series he posted]
Hello Sjoerd,
On 09/09/2014 09:52 AM, Sjoerd Simons wrote:
For i2c devices in OF the modalias
Hello Lee,
On 09/11/2014 10:00 AM, Sjoerd Simons wrote:
-static const struct of_device_id mxt_of_match[] = {
-{ .compatible = atmel,maxtouch, },
-{},
-};
-MODULE_DEVICE_TABLE(of, mxt_of_match);
-
static const struct i2c_device_id mxt_id[] = {
On 9 September 2014 08:58, kg...@kernel.org wrote:
Naveen Krishna Chatradhi wrote:
Add initial device tree nodes for EXYNOS7 SoC and board dts file
to support Espresso board based on Exynos7 SoC.
Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
Cc: Rob Herring r...@kernel.org
On Wed, 10 Sep 2014 15:31:44 +0100, Mark Brown broo...@kernel.org wrote:
On Wed, Sep 10, 2014 at 06:06:46AM -0700, Olof Johansson wrote:
On Mon, Sep 8, 2014 at 12:40 PM, Grant Likely grant.lik...@secretlab.ca
wrote:
Well, lets see... We've got a real user complaining about a platform
On 11/09/14 09:38, Javier Martinez Canillas wrote:
To expand on what Sjoerd already said and just to be sure everyone is on the
same page.
The problem is that right now the driver reports the following modalias:
# cat /sys/class/i2c-adapter/i2c-8/8-004b/modalias
i2c:maxtouch
but if you
On Wed, 10 Sep 2014 17:57:23 +0100, Mark Brown broo...@kernel.org wrote:
On Wed, Sep 10, 2014 at 05:29:32PM +0100, Grant Likely wrote:
What we can do is have an inhibit flag for
simplefb/simpleuart/simplewhatever that holds off PM. When a real
driver, or a stub that understands parsing
From: Andrew Bresticker abres...@chromium.org
Instead of having users of the ChromeOS EC call the interface-specific
cmd_xfer() callback directly, introduce a central cros_ec_cmd_xfer()
to use instead. This will allow us to put all the locking and retry
logic in one place instead of duplicating
From: Andrew Bresticker abres...@chromium.org
When an EC command returns EC_RES_IN_PROGRESS, we need to query
the state of the EC until it indicates that it is no longer busy.
Do this in cros_ec_cmd_xfer() under the EC's mutex so that other
commands (e.g. keyboard, I2C passtru) aren't issued to
From: Todd Broch tbr...@chromium.org
If the EC device tree node has sub-nodes, try to instantiate them as
MFD sub-devices. We can configure the EC features provided by the board.
Signed-off-by: Todd Broch tbr...@chromium.org
Signed-off-by: Javier Martinez Canillas
Hello,
This is a second batch of cleanups patches for the mfd cros_ec
driver and its subdevices drivers. The first batch of cleanups
was posted by Doug Anderson [0] and have already been merged.
The patches were picked from the ChromeOS 3.8 kernel and after
these no cleanups patches for cros_ec
From: Derek Basehore dbaseh...@chromium.org
Since the i2c bus can get wedged on the EC sometimes, set the number of retries
to 3. Since we un-wedge the bus immediately after the wedge happens, this is the
correct fix since only one transfer will fail.
Signed-off-by: Derek Basehore
From: Andrew Bresticker abres...@chromium.org
Now that there's a central cros_ec_cmd_xfer(), move the locking
out of the SPI driver.
Signed-off-by: Andrew Bresticker abres...@chromium.org
Reviewed-by: Simon Glass s...@chromium.org
Signed-off-by: Javier Martinez Canillas
From: Doug Anderson diand...@chromium.org
If someone sends a EC_CMD_REBOOT_EC to the EC, the EC will likely be
unresponsive for quite a while. Add a delay to the end of the command
to prevent random failures of future commands.
NOTES:
* This could be optimized a bit by simply delaying the next
Hello Dmitry,
On 09/11/2014 12:25 AM, Dmitry Torokhov wrote:
+hsi2c_8 {
+status = okay;
+clock-frequency = 333000;
+
+/* Atmel mXT336S */
+trackpad@4b {
+compatible = atmel,maxtouch;
+reg = 0x4b;
+interrupt-parent = gpx1;
+
Hello Nick,
On 09/11/2014 11:19 AM, Nick Dyer wrote:
Thanks for the clear explanation.
The i2c aliases are a bit confusing. The original device the driver was
written for was called qt602240, which was renamed by Atmel to mXT224 when
the chip series was called maXTouch. The driver now
From: Alim Akhtar alim.akh...@samsung.com
This patch adds the necessary Kconfig entries to enable
support for the ARMv8 based Exynos7 SoC.
Signed-off-by: Alim Akhtar alim.akh...@samsung.com
Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
Cc: Rob Herring r...@kernel.org
Cc: Catalin
While adding clock support for Exynos5260, the infrastructure to
register multiple clock controllers was introduced. Factor out the
support for registering multiple clock controller from Exynos5260
clock code to common samsung clock code so that it can be used by
other Exynos SoC which have
This patchset supports new Exynos7 Samsung SoC based on Cortex-A57.
Exynos7 is a System-On-Chip (SoC) that is based on 64-bit
ARMv8 RISC processor.
The following patches are tested based on Kgene's for-next tree.
https://git.kernel.org/cgit/linux/kernel/git/kgene/linux-samsung.git/log/?h=for-next
Add initial clock support for Exynos7 SoC which is required
to bring up platforms based on Exynos7.
Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
Cc: Tomasz Figa tomasz.f...@gmail.com
Cc: Mike Turquette mturque...@linaro.org
---
.../devicetree/bindings/clock/exynos7-clock.txt
Add initial device tree nodes for EXYNOS7 SoC and board dts file
to support Espresso board based on Exynos7 SoC.
Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
Cc: Rob Herring r...@kernel.org
Cc: Catalin Marinas catalin.mari...@arm.com
---
arch/arm64/boot/dts/Makefile
From: Pankaj Dubey pankaj.du...@samsung.com
Add symlink to include/dt-bindings from arch/arm64/boot/dts/include/ to
match the ones in ARM architectures so that preprocessed device
tree files can include various useful constant definitions.
See commit c58299aa8754 (kbuild: create an include
Add the fields fixed_factor_clks and nr_fixed_factor_clks to
struct exynos_cmu_info to allow registering of fixed factor
clocks as well with exynos_cmu_register_one().
Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
Cc: Tomasz Figa tomasz.f...@gmail.com
Cc: Mike Turquette
PLL145xx is similar to PLL35xx and PLL1460x is almost similar
to PLL46xx with minor differences in bit positions. Hence,
reuse the functions defined for pll_35xx and pll_46xx to
support 145xx and 1460x PLLs respectively.
Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
Cc: Tomasz
Allow Samsung serial driver to be usable on Exynos 64-bit SoC based
platforms.
Signed-off-by: Pankaj Dubey pankaj.du...@samsung.com
Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
Cc: Greg Kroah-Hartman gre...@linuxfoundation.org
---
drivers/tty/serial/Kconfig |2 +-
1 file
On Thursday 11 September 2014 15:50:49 Naveen Krishna Chatradhi wrote:
+ aliases {
+ serial0 = serial_0;
+ serial1 = serial_1;
+ serial2 = serial_2;
+ serial3 = serial_3;
+ };
+
Please move the aliases from the
Funny timing. I am just reviewing the series from Lee and also stumbled
over modaliases, too...
On Thu, Sep 11, 2014 at 10:19:54AM +0100, Nick Dyer wrote:
On 11/09/14 09:38, Javier Martinez Canillas wrote:
To expand on what Sjoerd already said and just to be sure everyone is on the
same
Hello Wolfram,
On 09/11/2014 01:08 PM, Wolfram Sang wrote:
Funny timing. I am just reviewing the series from Lee and also stumbled
over modaliases, too...
On Thu, Sep 11, 2014 at 10:19:54AM +0100, Nick Dyer wrote:
On 11/09/14 09:38, Javier Martinez Canillas wrote:
To expand on what
This is a workaround. It would make sense, however, to add it because we
want to support i2c_board_info structures.
I think it really depends if an IP block can be used on non-DT platforms
(which I think is true for this trackpad) but if a driver is for an IP block
that can only be
Hello Wolfram,
On 09/11/2014 01:35 PM, Wolfram Sang wrote:
This is a workaround. It would make sense, however, to add it because we
want to support i2c_board_info structures.
I think it really depends if an IP block can be used on non-DT platforms
(which I think is true for this
On 11 September 2014 16:11, Arnd Bergmann a...@arndb.de wrote:
On Thursday 11 September 2014 15:50:49 Naveen Krishna Chatradhi wrote:
+ aliases {
+ serial0 = serial_0;
+ serial1 = serial_1;
+ serial2 = serial_2;
+ serial3 =
On 11/09/14 12:41, Javier Martinez Canillas wrote:
On 09/11/2014 01:35 PM, Wolfram Sang wrote:
This is a workaround. It would make sense, however, to add it because we
want to support i2c_board_info structures.
I think it really depends if an IP block can be used on non-DT platforms
(which
On 2014년 08월 28일 18:07, Andrzej Hajda wrote:
This set of patches contains various improvement and fixes
for exynos_drm ipp framework.
The patchset is based on exynos-drm-next branch.
IPP framework was tested for regressions on exynos4210-trats target.
In the 2nd version of the series I
Update Exynos's DRM driver to use component match support rater than
add_components.
Changelog v2:
- release devices and drivers if failed.
- change compare_of to compare_dev.
Signed-off-by: Inki Dae inki@samsung.com
---
drivers/gpu/drm/exynos/exynos_drm_drv.c | 44
In exynos5260_tmu_registers tmu_ctrl entry is erroneously
assigned twice. The second assignment (to EXYNOS_TMU_REG_CONTROL1
define which represents 0x24 value) overrides the first one
(to EXYNOS_TMU_REG_CONTROL define which represents 0x20 value)
which results in the wrong (according to the
On 15/08/14 17:13, Stephen Warren wrote:
Any comments on this? I would really appreciate if you can expand on how
this DT property is supposed to be used so I can re-spin the atmel support
patch for Peach boards.
The below patch improves the documentation for the gpio-property.
That patch
On 09/11/2014 02:57 PM, Inki Dae wrote:
Update Exynos's DRM driver to use component match support rater than
add_components.
Changelog v2:
- release devices and drivers if failed.
- change compare_of to compare_dev.
Signed-off-by: Inki Dae inki@samsung.com
Modulo fixes I have posted
Hi,
On Wednesday 10 September 2014 01:26 PM, Vivek Gautam wrote:
On Wed, Sep 10, 2014 at 10:53 AM, Vivek Gautam gautam.vi...@samsung.com
wrote:
On Wed, Sep 10, 2014 at 10:23 AM, Felipe Balbi ba...@ti.com wrote:
On Wed, Sep 10, 2014 at 09:09:57AM +0530, Vivek Gautam wrote:
On Wed, Sep 10,
On Thu, Sep 11, 2014 at 10:06:08AM +0100, Grant Likely wrote:
On Wed, 10 Sep 2014 15:31:44 +0100, Mark Brown broo...@kernel.org wrote:
As well as the regulators we'll also need to fix the clocks. If we're
going to start adding these fixups perhaps we want to consider having a
wrapper
Hi,
On Thu, Sep 11, 2014 at 09:10:21PM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Wednesday 10 September 2014 01:26 PM, Vivek Gautam wrote:
On Wed, Sep 10, 2014 at 10:53 AM, Vivek Gautam gautam.vi...@samsung.com
wrote:
On Wed, Sep 10, 2014 at 10:23 AM, Felipe Balbi ba...@ti.com wrote:
On Thu, Sep 11, 2014 at 03:52:46PM +0100, Nick Dyer wrote:
On 15/08/14 17:13, Stephen Warren wrote:
Any comments on this? I would really appreciate if you can expand on how
this DT property is supposed to be used so I can re-spin the atmel support
patch for Peach boards.
The below patch
On Thu, Sep 11, 2014 at 10:22:32AM +0100, Grant Likely wrote:
On Wed, 10 Sep 2014 17:57:23 +0100, Mark Brown broo...@kernel.org wrote:
It's not quite as simple as just disabling PM - for example in the
clocks case we've also got to worry about what happens with rate changes
(which is going
The statement
static const char *name[];
defines a modifiable array of pointers to constant chars. That is
*name[0] = 'f';
is forbidden, but
name[0] = f;
is not. So marking an array that is defined as above with __initconst is
wrong. Either an additional const must be
[adding Sylwester and removing my samsung.com e-mail which is no longer
valid]
On 11.09.2014 23:04, Uwe Kleine-König wrote:
The statement
static const char *name[];
defines a modifiable array of pointers to constant chars. That is
*name[0] = 'f';
is forbidden, but
Hello,
On Thu, Sep 11, 2014 at 11:04:31PM +0200, Uwe Kleine-König wrote:
/* Mux parent lists. */
-static const char *fin_pll_p[] __initconst = {
+static const char *fin_pll_p[] __initdata = {
xxti,
xusbxti
};
As discussed with Tomasz on irc: The sad thing here is that for this
Hi,
On Thu, Sep 11, 2014 at 11:03 AM, Mark Brown broo...@kernel.org wrote:
On Thu, Sep 11, 2014 at 10:22:32AM +0100, Grant Likely wrote:
On Wed, 10 Sep 2014 17:57:23 +0100, Mark Brown broo...@kernel.org wrote:
It's not quite as simple as just disabling PM - for example in the
clocks case
Hi Pankaj,
On 10.09.2014 07:56, Pankaj Dubey wrote:
From: Chander Kashyap k.chan...@samsung.com
The parent name added in parent list as
mout_phyclk_mipi_dphy_4l_m_txbyte_clkhs_p, is different
than the defined parent due to typo.
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
Just curious if anyone is working on upstream DTS for the odroid-xu3?
It's booting fine with mainline using exynos5420-smdk5420.dts, but would
like to see more devices added.
I found the DTS files in the hardkernel v3.10.y branch which can be used
as a starting point, but wanted to know if
Hi Tomasz,
On Friday, September 12, 2014, Tomasz Figa wrote,
To: Pankaj Dubey; linux-arm-ker...@lists.infradead.org; linux-samsung-
s...@vger.kernel.org; linux-ker...@vger.kernel.org
Cc: kgene@samsung.com; s.nawro...@samsung.com; mturque...@linaro.org;
Chander Kashyap; Abhilash Kesavan
50 matches
Mail list logo
