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.
Hi,
On Thursday, September 11, 2014 1:52 AM, "Julius Werner"
wrote
right, use that to call phy_init() at the right time, then you need to
add a new ->calibrate() method which, likely, will only be used by you
;-)
so you mean, the xhci should itself call phy_init() at a time suitable,
s
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.
>
> [1]: http://permalink.gmane.org/gmane.linux.kernel.samsung-soc/37266
>
> I have
On Wed, Sep 10, 2014 at 01:31:30PM +0200, Javier Martinez Canillas wrote:
> The Peach Pi board has an Atmel maXTouch trackpad device.
> Add the needed Device Tree nodes to support it.
>
> This Device Tree change is based on the Chrome OS 3.8 tree
> but adapted to use the mainline Atmel maXTouch DT
On Wed, Sep 10, 2014 at 01:31:29PM +0200, Javier Martinez Canillas wrote:
> From: Sjoerd Simons
>
> The Peach Pit board has an Atmel maXTouch trackpad device.
> Add the needed Device Tree nodes to support it.
>
> This Device Tree change is based on the Chrome OS 3.8 tree
> but adapted to use the
>> right, use that to call phy_init() at the right time, then you need to
>> add a new ->calibrate() method which, likely, will only be used by you
>> ;-)
> so you mean, the xhci should itself call phy_init() at a time suitable,
> so that ->calibrate() is not required at all ?
I'm not sure if tha
Javier,
On Wed, Sep 10, 2014 at 3:19 AM, Javier Martinez Canillas
wrote:
> From: Vivek Gautam
>
> Enabled MAX77802 pmic for exynos systems.
> One config USB_ANNOUNCE_NEW_DEVICES to display device
> information on connect.
> Another config for I2C_CHARDEV to see i2c device nodes.
>
> Signed-off-b
Javier,
On Wed, Sep 10, 2014 at 3:19 AM, Javier Martinez Canillas
wrote:
> The downstream ChromeOS 3.8 kernel sets the clock frequency
> for the I2C bus 7 at 400kHz. Do the same change in mainline.
>
> Suggested-by: Doug Anderson
> Signed-off-by: Javier Martinez Canillas
> ---
> arch/arm/boot/
Mark,
On Wed, Sep 10, 2014 at 12:45 PM, Mark Brown wrote:
> On Wed, Sep 10, 2014 at 09:45:21AM -0700, Doug Anderson wrote:
>
>> Right now I know that clock disabling is supposed to be inhibited
>> during the early boot process. I think regulators too?
>
> No, for regulators we'll quite happily d
On Wed, Sep 10, 2014 at 09:45:21AM -0700, Doug Anderson wrote:
> Right now I know that clock disabling is supposed to be inhibited
> during the early boot process. I think regulators too?
No, for regulators we'll quite happily disable anything a consumer asks
us to at any point but we'll only do
not reliably reproducable and
> difficult to bisect. Here are a few boot logs from recent
> mainline/linux-next kernels that are failing:
FYI, I'm seeing the same periodic aborts. For example, here's my boot
of next-20140910:
http://images.armcloud.us/kernel-ci/next/next-201409
-gd030671:
http://armv7.com/scheduler/job/5770/log_file#L_193_277
mainline/v3.17-rc4-146-g619df5d:
http://armv7.com/scheduler/job/6014/log_file#L_124_0
next/20140908:
http://armv7.com/scheduler/job/5815/log_file#L_59_276
next/20140910:
http://armv7.com/scheduler/job/6161/log_file
On Wed, Sep 10, 2014 at 09:36:32AM -0700, Olof Johansson wrote:
> On Wed, Sep 10, 2014 at 7:31 AM, Mark Brown 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 stage that deals
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 the resource dependencies,
> takes ownership of the device (or userspace tells
Grant,
On Wed, Sep 10, 2014 at 9:29 AM, Grant Likely wrote:
> On Wed, Sep 10, 2014 at 4:39 PM, Mark Brown wrote:
>> On Wed, Sep 10, 2014 at 03:56:16PM +0100, Grant Likely wrote:
>>> On Wed, Sep 10, 2014 at 3:31 PM, Mark Brown wrote:
>>
>>> > As far as I can tell the problem here is coming from
The default mux and divider clocks are specified in device tree
so that the FIMC devices in Exynos4210 and Exynos4x12 SoCs are
clocked from recommended clock source and with maximum supported
frequency. If needed these settings could be overrode in board
specific dts files, however they are in prac
On Wed, Sep 10, 2014 at 7:31 AM, Mark Brown 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
>> wrote:
>
>> > Well, lets see... We've got a real user complaining about a platform
>> > that used to work on mainline, and no l
On Wed, Sep 10, 2014 at 4:39 PM, Mark Brown wrote:
> On Wed, Sep 10, 2014 at 03:56:16PM +0100, Grant Likely wrote:
>> On Wed, Sep 10, 2014 at 3:31 PM, Mark Brown wrote:
>
>> > As far as I can tell the problem here is coming from the decision to
>> > have simplefb use resources without knowing abo
On Wed, Sep 10, 2014 at 05:03:52PM +0100, Doug Anderson wrote:
> On Wed, Sep 10, 2014 at 4:17 AM, Will Deacon wrote:
> > On Mon, Sep 08, 2014 at 03:05:40PM +0100, Javier Martinez Canillas wrote:
> >> Since many folks don't agree that hacking different subsystems is the way
> >> forward I'll hold t
Will,
On Wed, Sep 10, 2014 at 4:17 AM, Will Deacon wrote:
> On Mon, Sep 08, 2014 at 03:05:40PM +0100, Javier Martinez Canillas wrote:
>> Hello Will,
>
> Hi Javier,
>
>> Since many folks don't agree that hacking different subsystems is the way
>> forward I'll hold the patches and don't post them.
On Wed, Sep 10, 2014 at 03:56:16PM +0100, Grant Likely wrote:
> On Wed, Sep 10, 2014 at 3:31 PM, Mark Brown wrote:
> > As far as I can tell the problem here is coming from the decision to
> > have simplefb use resources without knowing about them - can we agree
> > that this is a bad idea?
> No,
This ensures the core and the audio subsystem clocks are configured
properly, as expected by the sound machine driver. These bits are
missing to obtain proper audio sample rates in kernel v3.17, where
audio support for Odroid X2/U3 was first added.
Signed-off-by: Sylwester Nawrocki
---
It would b
On Wed, Sep 10, 2014 at 3:31 PM, Mark Brown 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
>> wrote:
>
>> > Well, lets see... We've got a real user complaining about a platform
>> > that used to work on mainline, and no l
This ensures the core and the audio subsystem clocks are configured
properly, as expected by the sound machine driver. These bits are
missing to obtain proper audio sample rates in kernel v3.17, where
audio support for Odroid X2/U3 was first added.
Signed-off-by: Sylwester Nawrocki
---
It would b
On Wed, Sep 10, 2014 at 06:06:46AM -0700, Olof Johansson wrote:
> On Mon, Sep 8, 2014 at 12:40 PM, Grant Likely
> wrote:
> > Well, lets see... We've got a real user complaining about a platform
> > that used to work on mainline, and no longer does. The only loophole
> > for ignoring breakage is
ping.
On Wed, Aug 27, 2014 at 7:59 PM, Ajay Kumar wrote:
> This series is based on master branch of Linus tree at:
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>
> I have tested this after adding few DT changes for exynos5250-snow and
> exynos5420-peach-pit boards.
>
> The V
Hi,
Been travelling I'm buried in email, so a bit slow at responding.
On Mon, Sep 8, 2014 at 12:40 PM, Grant Likely wrote:
> On Mon, Sep 8, 2014 at 4:58 PM, Doug Anderson wrote:
>> Grant,
>>
>> On Mon, Sep 8, 2014 at 5:20 AM, Grant Likely
>> wrote:
>>> On Mon, Sep 8, 2014 at 12:21 PM, Will De
The patch replaces separate calls to driver (de)registration by
loops over the array of drivers. As a result it significantly
decreases number of ifdefs. Additionally it moves device registration
related ifdefs to header file.
Signed-off-by: Andrzej Hajda
---
Hi Inki,
During testing your compone
Many Exynos based Chromebooks have an Atmel trackpad so enable
support for it by default will make easier for users.
Signed-off-by: Javier Martinez Canillas
---
Changes since v3: None
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/exynos_
From: Sjoerd Simons
The Peach Pit board has an Atmel maXTouch trackpad device.
Add the needed Device Tree nodes to support it.
This Device Tree change is based on the Chrome OS 3.8 tree
but adapted to use the mainline Atmel maXTouch DT binding.
Signed-off-by: Sjoerd Simons
Signed-off-by: Javie
The Peach Pi board has an Atmel maXTouch trackpad device.
Add the needed Device Tree nodes to support it.
This Device Tree change is based on the Chrome OS 3.8 tree
but adapted to use the mainline Atmel maXTouch DT binding.
Signed-off-by: Javier Martinez Canillas
---
Changes since v3: None, new
Hello Kukjin,
This is a fourth version of the series that adds support
for the Atmel trackpad found on the Exynos5420 Peach Pit
and Pi boards.
Support for Pi was included again even when the driver
does not support yet the T100 touchscreen objects used
by the Atmel mXT540S chip found on the Peach
On Mon, Sep 08, 2014 at 03:05:40PM +0100, Javier Martinez Canillas wrote:
> Hello Will,
Hi Javier,
> Since many folks don't agree that hacking different subsystems is the way
> forward I'll hold the patches and don't post them. The sunxi thread [0]
> already shows how different people have strong
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.
[1]: http://permalink.gmane.org/gmane.linux.kernel.samsung-soc/37266
I have tested successfully your patch with trats and universal_c210 b
From: Rahul Sharma
Adding regulators for HDMI for Peach-pi board.
Signed-off-by: Rahul Sharma
Reviewed-by: Javier Martinez Canillas
Signed-off-by: Javier Martinez Canillas
Reviewed-by: Doug Anderson
---
arch/arm/boot/dts/exynos5800-peach-pi.dts | 5 +
1 file changed, 5 insertions(+)
di
Hello Kukjin,
This is a third version of th series that adds max77802 support for
the Peach Pit and Pi boards. The series also have all the pending
patches that were posted but depended on this support. I've picked
all the patches I found and rebased them to be sure that they apply
cleanly on top
Exynos5420 based Peach Pit and Exynos5800 based Peach Pi boards
uses a Maxim 77802 power management IC to drive regulators and
its Real Time Clock. This patch adds support for this chip.
These are the device nodes and pinctrl configuration that
are present on the Peach pit DeviceTree source file i
From: Rahul Sharma
Adding regulators for hdmi for peach-pit board.
Signed-off-by: Rahul Sharma
Reviewed-by: Javier Martinez Canillas
Signed-off-by: Javier Martinez Canillas
Reviewed-by: Doug Anderson
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 5 +
1 file changed, 5 insertions(+)
The Exynos5420 based Peach Pit and the Exynos5800 based Peach Pi
machines have an i2c ISL29018 light sensor. This patch adds the
device nodes needed to support this device.
These DTS snippets were taken from the downstream Chrome OS 3.8
kernel Device Tree for Peach Pit and Pi boards.
Signed-off-b
The downstream ChromeOS 3.8 kernel sets the clock frequency
for the I2C bus 7 at 400kHz. Do the same change in mainline.
Suggested-by: Doug Anderson
Signed-off-by: Javier Martinez Canillas
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 1 +
arch/arm/boot/dts/exynos5800-peach-pi.dts | 1 +
2
From: Naveen Krishna Chatradhi
This patch creates a thermistor fragment carrying the NTC Thermistor
nodes as children of the IIO based ADC.
This fragment is included in exynos5420-peach-pit.dts and
exynos5800-peach-pi.dts.
Signed-off-by: Naveen Krishna Chatradhi
Signed-off-by: Javier Martinez
From: Vivek Gautam
Enabled MAX77802 pmic for exynos systems.
One config USB_ANNOUNCE_NEW_DEVICES to display device
information on connect.
Another config for I2C_CHARDEV to see i2c device nodes.
Signed-off-by: Vivek Gautam
Signed-off-by: Javier Martinez Canillas
---
arch/arm/configs/exynos_de
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 exposed to userspace is i2c: > type>, for the Maxtouch driver t
Hello Doug,
On 09/10/2014 06:52 AM, Doug Anderson wrote:
>
> I would note that the downstream dts file has this i2c bus at 400kHz.
> ...but that's not a problem with your patch. Perhaps you could submit
> that as a separate patch?
>
Indeed, I've to re-spin anyways so I'll include that on the ne
Hello Doug,
On 09/10/2014 06:45 AM, Doug Anderson wrote:
>>
>> Reviewed-by: Doug Anderson
>
> Meant to add this to the v2. Sorry for the spam...
>
No worries, I've to re-spin anyways to fix the issue you pointed on Patch #1
so I'll include your Reviewed-by tag.
Best regards,
Javier
--
To uns
Hello Doug,
On 09/10/2014 06:42 AM, Doug Anderson wrote:
>> +
>> + ldo35_reg: LDO35 {
>> + regulator-name = "ldo_35";
>> + regulator-min-microvolt = <120>;
>> + regulator-max-microvo
On 10.09.2014 07:56, Pankaj Dubey wrote:
From: Chander Kashyap
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
Signed-off-by: Chander Kashyap
---
drivers/clk/samsung/clk-exy
On Wed, Sep 10, 2014 at 10:53 AM, Vivek Gautam wrote:
> On Wed, Sep 10, 2014 at 10:23 AM, Felipe Balbi wrote:
>> On Wed, Sep 10, 2014 at 09:09:57AM +0530, Vivek Gautam wrote:
>>> On Wed, Sep 10, 2014 at 9:07 AM, Vivek Gautam
>>> wrote:
>>> > adding Julius here,
>>>
>>> i think i had missed addi
Hello Mike,
On 09/09/2014 10:57 PM, Mike Turquette wrote:
> Quoting Javier Martinez Canillas (2014-09-07 23:49:28)
>>
>> Since we are in 3.17-rc4 already, I'm afraid that this series may miss
>> 3.18 again, is there anything else you need from me to pick this
>> series? It will obviously conflict
49 matches
Mail list logo
