Uri Mashiach writes:
> Device tree modifications:
> - Pinmux for SPI0 and WiFi GPIOs.
> - SPI0 node with wlcore as a child node.
>
> Cc: Tony Lindgren
> Signed-off-by: Uri Mashiach
> ---
> v1 -> v2: Replace interrupts
Hi Kalle Valo,
On 01/07/2016 11:02 AM, Kalle Valo wrote:
Uri Mashiach writes:
Device tree modifications:
- Pinmux for SPI0 and WiFi GPIOs.
- SPI0 node with wlcore as a child node.
Cc: Tony Lindgren
Signed-off-by: Uri Mashiach
Hi!
> On Thursday 07 January 2016 02:16 AM, Pavel Machek wrote:
> > Hi!
> >
> > In v4.1, both internal MMC and u-SD cards work ok.
> >
> > In v4.2, only the internal MMC is detected. In v4.3, not even internal
> > MMC works. In v4.4, only the internal MMC is detected.
> >
> > Does it work for
On Wednesday 06 January 2016 10:55:51 Ivaylo Dimitrov wrote:
>
>
> On 6.01.2016 00:49, Tony Lindgren wrote:
> >
> >Suggested fix below, please test and reply with your Tested-by's if
> >it solves the problem so we may still be able to get this into v4.4.
> >
> >Regards,
> >
> >Tony
> >
> >8<
On 6.01.2016 00:49, Tony Lindgren wrote:
Suggested fix below, please test and reply with your Tested-by's if
it solves the problem so we may still be able to get this into v4.4.
Regards,
Tony
8< ---
From: Tony Lindgren
Date: Tue, 5 Jan 2016 12:04:20 -0800
On Wed, Jan 06, 2016 at 04:19:53PM +0530, Kishon Vijay Abraham I wrote:
> Perform syscon configurations to get x2 mode to working in DRA74x and
> DRA72x. Also add a new compatible string to dfferentiate
> DRA72x and DRA74x, since b1c0 mask is different for both these platforms.
>
> Signed-off-by:
On Wed, Jan 06, 2016 at 04:29:08PM +0530, Kishon Vijay Abraham I wrote:
> DRA72 uses USB3 PHY for the 2nd lane of PCIE. The configuration
> required to make USB3 PHY used for the 2nd lane of PCIe is done
> here.
>
> Signed-off-by: Kishon Vijay Abraham I
> ---
>
On 01/06/2016 02:13 AM, Laxman Dewangan wrote:
>
> On Wednesday 06 January 2016 01:12 PM, H. Nikolaus Schaller wrote:
>> Hi,
>>
>> Am 06.01.2016 um 00:40 schrieb Nishanth Menon :
>>
>>> On 01/05/2016 06:01 AM, H. Nikolaus Schaller wrote:
+rtc {
+
On 01/06/2016 08:22 AM, Frank Jenner wrote:
> Hello,
>
> I am working on trying to enable power management features on a
> product that was based on the OMAP4430 SoC and the mainline 3.14
> kernel. In particular, I am interested in enabling Smart Reflex/AVS
> and frequency scaling (via cpufreq)
I dont' know if it helps, but I struggeled with this too.
With my DM3730 (OMAP 3630), I had to enable Device Drivers->Adaptive
Voltage Scaling Class Support which enables CONFIG_POWER_AVS, a
requirement for POWER_AVS_OMAP.
Once I did that, I was able to get AVS Class 3 working on my DM3730
using
On Wed, Jan 6, 2016 at 9:26 AM, Nishanth Menon wrote:
> On 01/06/2016 08:22 AM, Frank Jenner wrote:
>> Hello,
>>
>> I am working on trying to enable power management features on a
>> product that was based on the OMAP4430 SoC and the mainline 3.14
>> kernel. In particular, I am
On 01/06/2016 09:05 AM, Frank Jenner wrote:
> On Wed, Jan 6, 2016 at 9:26 AM, Nishanth Menon wrote:
>> On 01/06/2016 08:22 AM, Frank Jenner wrote:
>>> Hello,
>>>
>>> I am working on trying to enable power management features on a
>>> product that was based on the OMAP4430 SoC and the
Hi,
On Tue, Jan 05, 2016 at 02:49:29PM -0800, Tony Lindgren wrote:
> Commit 63aa945b1013 ("memory: omap-gpmc: Add Kconfig option for debug")
> unified the GPMC debug for the SoCs with GPMC. The commit also left
> out the option for HWMOD_INIT_NO_RESET as we now require proper timings
> for GPMC
mespace) from []
(kernel_init_freeable+0x178/0x1c4)
<4>[8.412963] [] (kernel_init_freeabme) from []
(kernel_init+0x8/0xe4)
<4>[8.426300] [] (kernel_init) from []
(ret_from_fork+0x14/0x3c)
P.S.
(Pali, sorry for not having time to read the kernel docs re e-mail
clients :) )
--
* Sebastian Reichel [160106 09:41]:
> Hi,
>
> On Tue, Jan 05, 2016 at 02:49:29PM -0800, Tony Lindgren wrote:
> > Commit 63aa945b1013 ("memory: omap-gpmc: Add Kconfig option for debug")
> > unified the GPMC debug for the SoCs with GPMC. The commit also left
> > out the option for
* Ivaylo Dimitrov [160106 10:01]:
>
> Unfortunately, it seems there is more to be fixed. It booted several times
> to the userspace, but after a couple of shutdowns, rootfs became corrupted
> again. I flashed, installed linux 4.4, but the same happened after the
Hi,
On 6.01.2016 20:26, Tony Lindgren wrote:
Hmm. Care to verify that your onenand really gets detected at 83 MHz like
your earlier logs show? Below is a patch that should show it.
before the corruption appeared, I looked a couple of times in syslog and
the freq there was 83MHz. Including
On 01/06/2016 10:02 AM, Adam Ford wrote:
> I dont' know if it helps, but I struggeled with this too.
>
> With my DM3730 (OMAP 3630), I had to enable Device Drivers->Adaptive
> Voltage Scaling Class Support which enables CONFIG_POWER_AVS, a
> requirement for POWER_AVS_OMAP.
>
> Once I did that, I
On Wed, Jan 6, 2016 at 8:36 AM, Nishanth Menon wrote:
> On 01/06/2016 02:13 AM, Laxman Dewangan wrote:
>>
>> On Wednesday 06 January 2016 01:12 PM, H. Nikolaus Schaller wrote:
>>> Hi,
>>>
>>> Am 06.01.2016 um 00:40 schrieb Nishanth Menon :
>>>
On 01/05/2016 06:01
Any chance you can define what you mean by 'issues' and 'old'?
Logic PD (my daytime employer) uses AVS 3 in their custom Linux
distribution. If that's going to be a problem, I would like to notify
some people there.
adam
On Wed, Jan 6, 2016 at 1:12 PM, Nishanth Menon
* Pali Rohár [160106 01:06]:
> On Wednesday 06 January 2016 10:55:51 Ivaylo Dimitrov wrote:
> > On 6.01.2016 00:49, Tony Lindgren wrote:
> > >
> > >Suggested fix below, please test and reply with your Tested-by's if
> > >it solves the problem so we may still be able to get
* H. Nikolaus Schaller [160106 08:48]:
> Hi Tony,
>
> Am 06.01.2016 um 17:41 schrieb Tony Lindgren :
>
> > Hi,
> >
> > * H. Nikolaus Schaller [160106 00:12]:
> >> Am 06.01.2016 um 02:00 schrieb Tony Lindgren :
> >>>
Hi,
* H. Nikolaus Schaller [160106 00:12]:
> Am 06.01.2016 um 02:00 schrieb Tony Lindgren :
> >
> > Also I'm not seeing just zeroes coming from RTC after typing hwclock
> > on omap5-uevm. It's working on x15 though.
> >
> > Nikolaus, is hwclock command
Hi,
On Tue, Jan 05, 2016 at 02:49:29PM -0800, Tony Lindgren wrote:
> From: Tony Lindgren
> Date: Tue, 5 Jan 2016 12:04:20 -0800
> Subject: [PATCH] ARM: OMAP2+: Fix onenand rate detection to avoid filesystem
> corruption
>
> Commit 63aa945b1013 ("memory: omap-gpmc: Add Kconfig
Hi Tony,
Am 06.01.2016 um 17:41 schrieb Tony Lindgren :
> Hi,
>
> * H. Nikolaus Schaller [160106 00:12]:
>> Am 06.01.2016 um 02:00 schrieb Tony Lindgren :
>>>
>>> Also I'm not seeing just zeroes coming from RTC after typing hwclock
>>>
Hi Tony,
Am 06.01.2016 um 02:00 schrieb Tony Lindgren :
> * Nishanth Menon [160105 15:40]:
>> On 01/05/2016 06:01 AM, H. Nikolaus Schaller wrote:
>>> tested on OMP5432 EVM
>>>
>>> Signed-off-by: H. Nikolaus Schaller
>>> ---
>>>
On Wednesday 06 January 2016 01:12 PM, H. Nikolaus Schaller wrote:
Hi,
Am 06.01.2016 um 00:40 schrieb Nishanth Menon :
On 01/05/2016 06:01 AM, H. Nikolaus Schaller wrote:
+ rtc {
+ compatible = "ti,palmas-rtc";
+
Hi Grygorii,
On Thu, Dec 10, 2015 at 09:18:20PM +0200, Grygorii Strashko wrote:
> On -RT and if kernel is booting with "threadirqs" cmd line parameter
> pcie/pci (msi) irq cascade handlers (like dra7xx_pcie_msi_irq_handler())
> will be forced threaded and, as result, will generate warnings like:
Hi,
On Thursday 07 January 2016 02:16 AM, Pavel Machek wrote:
> Hi!
>
> In v4.1, both internal MMC and u-SD cards work ok.
>
> In v4.2, only the internal MMC is detected. In v4.3, not even internal
> MMC works. In v4.4, only the internal MMC is detected.
>
> Does it work for you? Any patches?
Hi,
On Wednesday 06 January 2016 07:43 PM, Rob Herring wrote:
> On Wed, Jan 06, 2016 at 04:19:53PM +0530, Kishon Vijay Abraham I wrote:
>> Perform syscon configurations to get x2 mode to working in DRA74x and
>> DRA72x. Also add a new compatible string to dfferentiate
>> DRA72x and DRA74x, since
On 01/06/2016 01:44 PM, Adam Ford wrote:
> Any chance you can define what you mean by 'issues' and 'old'?
>
AVS class recommendation is AVS Class 1.5 for DM3730. If one does not
follow the recommendation, then the result will be that some devices may
not function OR fail in some unpredictable
On 01/06/2016 01:34 PM, Rob Herring wrote:
> On Wed, Jan 6, 2016 at 8:36 AM, Nishanth Menon wrote:
>> On 01/06/2016 02:13 AM, Laxman Dewangan wrote:
>>>
>>> On Wednesday 06 January 2016 01:12 PM, H. Nikolaus Schaller wrote:
Hi,
Am 06.01.2016 um 00:40 schrieb Nishanth
On Saturday 02 January 2016 09:06:57 Tony Lindgren wrote:
> Hi,
>
> * Pali Rohár [160102 06:46]:
> > --- a/drivers/media/rc/ir-rx51.c
> > +++ b/drivers/media/rc/ir-rx51.c
> > @@ -25,9 +25,9 @@
> > #include
> > #include
> > #include
> > +#include
> >
> > -#include
On Saturday 02 January 2016 14:38:36 Nishanth Menon wrote:
> On 01/02/2016 11:16 AM, Tony Lindgren wrote:
> > * Pali Rohár [160102 06:31]:
> >> Hello,
> >>
> >> MPU OPP table table (omap36xx_vddcore_volt_data) defined in
> >> opp3xxx_data.c does not match Nokia N900 phone.
On Monday 04 January 2016 20:13:56 Tony Lindgren wrote:
> * Ivaylo Dimitrov [160104 10:59]:
> > Hi,
> >
> > On 4.01.2016 19:40, Tony Lindgren wrote:
> > >>On Monday 04 January 2016 18:02:06 Tony Lindgren wrote:
> > >Care to boot with CONFIG_OMAP_GPMC_DEBUG=y
On Tue, Jan 05, 2016 at 10:50:42AM +0530, Vignesh R wrote:
> Hi Brian,
>
> On 12/11/2015 09:39 AM, Vignesh R wrote:
> > Changes since v4:
> > Use syscon to access system control module register in ti-qspi driver.
> >
>
> Gentle ping...
> Are you ok with MTD side changes of this patch series?
Hi,
Am 06.01.2016 um 00:40 schrieb Nishanth Menon :
> On 01/05/2016 06:01 AM, H. Nikolaus Schaller wrote:
>> tested on OMP5432 EVM
>>
>> Signed-off-by: H. Nikolaus Schaller
>> ---
>> arch/arm/boot/dts/omap5-board-common.dtsi | 8
>> 1 file changed, 8
* Pali Rohár [160105 00:50]:
> On Monday 04 January 2016 20:13:56 Tony Lindgren wrote:
> > * Ivaylo Dimitrov [160104 10:59]:
> > > Hi,
> > >
> > > On 4.01.2016 19:40, Tony Lindgren wrote:
> > > >>On Monday 04 January 2016 18:02:06 Tony
On Tuesday 05 January 2016 12:37:50 Pali Rohár wrote:
> On Monday 28 December 2015 23:27:17 Arnd Bergmann wrote:
> > On Monday 28 December 2015 13:01:22 Frank Rowand wrote:
> > >
> > > Patch 2/5 copies the value from ATAG_REVISION into the fdt "/revision"
> > > property.
> > >
> > > If the use
On Thursday 31 December 2015 09:38:45 Eduardo Valentin wrote:
> > +
> > + bandgap {
> > + reg = <0x48002524 0x4>;
> > + compatible = "ti,omap36xx-bandgap";
>
> Can you please already add on both cases
>
> #thermal-sensor-cells = <0>;
> ?
>
> This
On Monday 28 December 2015 23:27:17 Arnd Bergmann wrote:
> On Monday 28 December 2015 13:01:22 Frank Rowand wrote:
> >
> > Patch 2/5 copies the value from ATAG_REVISION into the fdt "/revision"
> > property.
> >
> > If the use of /revision is limited to being a location to hold an ATAG
> > value
* Nishanth Menon [160105 15:40]:
> On 01/05/2016 06:01 AM, H. Nikolaus Schaller wrote:
> > tested on OMP5432 EVM
> >
> > Signed-off-by: H. Nikolaus Schaller
> > ---
> > arch/arm/boot/dts/omap5-board-common.dtsi | 8
> > 1 file changed, 8 insertions(+)
* Pali Rohár [160105 02:19]:
> On Saturday 02 January 2016 09:06:57 Tony Lindgren wrote:
> >
> > Yup please take a look at thread "[PATCH 0/3] pwm: omap: Add PWM support
> > using dual-mode timers". Chances are we still need to set up the dmtimer
> > code to provide also
On Tue, Jan 5, 2016 at 4:48 AM, Rafael J. Wysocki wrote:
> On Monday, January 04, 2016 06:27:18 PM Derek Basehore wrote:
>> On Mon, Nov 02, 2015 at 02:50:40AM +0100, Rafael J. Wysocki wrote:
>> >
>> > I've queued up this series for the second half of the v4.4 merge window.
>>
On 01/05/2016 06:01 AM, H. Nikolaus Schaller wrote:
> tested on OMP5432 EVM
>
> Signed-off-by: H. Nikolaus Schaller
> ---
> arch/arm/boot/dts/omap5-board-common.dtsi | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm/boot/dts/omap5-board-common.dtsi
On Monday, January 04, 2016 06:27:18 PM Derek Basehore wrote:
> On Mon, Nov 02, 2015 at 02:50:40AM +0100, Rafael J. Wysocki wrote:
> >
> > I've queued up this series for the second half of the v4.4 merge window.
> >
> > Thanks,
> > Rafael
> >
> >
> >
On 01/04/2016 06:37 PM, Tony Lindgren wrote:
* Russell King - ARM Linux [160104 06:43]:
On Mon, Jan 04, 2016 at 03:27:57PM +0200, Tero Kristo wrote:
On 01/04/2016 12:21 PM, Geert Uytterhoeven wrote:
FWIW, there are small loops with just a cpu_relax() in various clock
Hi,
On 4.01.2016 19:40, Tony Lindgren wrote:
On Monday 04 January 2016 18:02:06 Tony Lindgren wrote:
> >Care to boot with CONFIG_OMAP_GPMC_DEBUG=y and post the gpmc related
> >dmesg output?
Here it is, including the pre-gpmc log, keep in mind this is with
restored HWMOD_INIT_NO_RESET flag
Hi Tero,
On Mon, Jan 4, 2016 at 8:36 AM, Tero Kristo wrote:
> On 01/01/2016 07:48 AM, Michael Turquette wrote:
>> Quoting Tero Kristo (2015-12-18 05:58:58)
>>> +static int _omap4_hwmod_clk_enable(struct clk_hw *hw)
>>> +{
>>> + struct clk_hw_omap *clk = to_clk_hw_omap(hw);
Hi,
On 01/01/16 14:01, Pali Rohár wrote:
> Hi Tomi! Can you review this patch? It is waiting here for two years!
>
> On Thursday 26 December 2013 00:12:39 Ivaylo Dimitrov wrote:
>> From: Ivaylo Dimitrov
>>
>> On memory limited devices, CMA fails easily when asked to
Hi Thomas,
On Tuesday 15 December 2015 08:58 PM, Tony Lindgren wrote:
> * Sekhar Nori [151215 06:26]:
>> Under some conditions, irq sorting procedure used
>> by INTC can go wrong resulting in a spurious irq
>> getting reported.
>>
>> If this condition is not handled, it results
On Tuesday 04 August 2015 09:02:39 Peter Ujfalusi wrote:
> On 08/03/2015 09:48 PM, Jarkko Nikula wrote:
> > It is well possible that some regression got introduced to
> > TPA6130A2 I2C communication over the years without nobody than you
> > now notices. We used to do QA back in Meego N900 days
Quoting Tero Kristo (2016-01-04 11:15:36)
> On 01/04/2016 06:37 PM, Tony Lindgren wrote:
> > * Russell King - ARM Linux [160104 06:43]:
> >> On Mon, Jan 04, 2016 at 03:27:57PM +0200, Tero Kristo wrote:
> >>> On 01/04/2016 12:21 PM, Geert Uytterhoeven wrote:
> FWIW,
On Mon, Nov 02, 2015 at 02:50:40AM +0100, Rafael J. Wysocki wrote:
>
> I've queued up this series for the second half of the v4.4 merge window.
>
> Thanks,
> Rafael
>
>
> ___
> linux-arm-kernel mailing list
> linux-arm-ker...@lists.infradead.org
>
* Ivaylo Dimitrov [160104 10:59]:
> Hi,
>
> On 4.01.2016 19:40, Tony Lindgren wrote:
> >>On Monday 04 January 2016 18:02:06 Tony Lindgren wrote:
> >Care to boot with CONFIG_OMAP_GPMC_DEBUG=y and post the gpmc related
> >dmesg output?
>
> Here it is,
Quoting Tero Kristo (2016-01-03 23:36:05)
> On 01/01/2016 07:48 AM, Michael Turquette wrote:
> > Hi Tero,
> >
> > Quoting Tero Kristo (2015-12-18 05:58:58)
> >> Previously, hwmod core has been used for controlling the hwmod level
> >> clocks. This has certain drawbacks, like being unable to share
Hi Tomi,
On 4.01.2016 13:37, Tomi Valkeinen wrote:
We probably need exactly the same for omapdrm, as omapfb is on the way
to being deprecated. And sounds to me that we probably need similar for
other devices which try to do large allocations (camera? video decoders?).
Re omapdrm - I guess
On 01/04/2016 12:21 PM, Geert Uytterhoeven wrote:
Hi Tero,
On Mon, Jan 4, 2016 at 8:36 AM, Tero Kristo wrote:
On 01/01/2016 07:48 AM, Michael Turquette wrote:
Quoting Tero Kristo (2015-12-18 05:58:58)
+static int _omap4_hwmod_clk_enable(struct clk_hw *hw)
+{
+ struct
Hi Brian,
On 12/11/2015 09:39 AM, Vignesh R wrote:
> Changes since v4:
> Use syscon to access system control module register in ti-qspi driver.
>
Gentle ping...
Are you ok with MTD side changes of this patch series?
> Changes since v3:
> Rework to introduce spi_flash_read_message struct.
>
On Mon, Jan 04, 2016 at 03:27:57PM +0200, Tero Kristo wrote:
> On 01/04/2016 12:21 PM, Geert Uytterhoeven wrote:
> >FWIW, there are small loops with just a cpu_relax() in various clock drivers
> >under drivers/clk/shmobile/.
>
> Just did a quick profiling round, and the clk_enable/disable delay
* Russell King - ARM Linux [160104 06:43]:
> On Mon, Jan 04, 2016 at 03:27:57PM +0200, Tero Kristo wrote:
> > On 01/04/2016 12:21 PM, Geert Uytterhoeven wrote:
> > >FWIW, there are small loops with just a cpu_relax() in various clock
> > >drivers
> > >under
* Pali Rohár [160104 09:35]:
> On Monday 04 January 2016 18:02:06 Tony Lindgren wrote:
> > Care to boot with CONFIG_OMAP_GPMC_DEBUG=y and post the gpmc related
> > dmesg output?
>
> Hi Tony. We do not have serial console for N900 and so when kernel is
> not fully bootable
On Monday 04 January 2016 18:02:06 Tony Lindgren wrote:
> Care to boot with CONFIG_OMAP_GPMC_DEBUG=y and post the gpmc related
> dmesg output?
Hi Tony. We do not have serial console for N900 and so when kernel is
not fully bootable to userspace we cannot provide dmesg for you :-(
Maybe
* Pali Rohár [160102 13:39]:
> On Saturday 02 January 2016 18:14:31 Tony Lindgren wrote:
>
> > The n900 specific code was based on something before the TI generic
> > values were available I think. And the last time I looked at it I
> > came to the conclusion the n900
* Ivaylo Dimitrov [160101 03:29]:
> Hi Tony,
>
> On 21.05.2015 00:21, Tony Lindgren wrote:
> >We support decoding the bootloader values if DEBUG is defined.
> >But we also need to change the struct omap_hwmod flags to have
> >HWMOD_INIT_NO_RESET to avoid the GPMC
On 01/01/2016 07:48 AM, Michael Turquette wrote:
Hi Tero,
Quoting Tero Kristo (2015-12-18 05:58:58)
Previously, hwmod core has been used for controlling the hwmod level
clocks. This has certain drawbacks, like being unable to share the
clocks for multiple users, missing usecounting and
Le jeudi 31 décembre 2015 à 22:14 +, Mark Brown a écrit :
> On Thu, Dec 31, 2015 at 10:59:06PM +0100, Paul Kocialkowski wrote:
>
> > I understand, thanks for pointing this out. Well, for my use case, there
> > is no use in disabling the chip at any point as it powers the external
> > mmc.
>
* Pali Rohár [160102 06:31]:
> Hello,
>
> MPU OPP table table (omap36xx_vddcore_volt_data) defined in
> opp3xxx_data.c does not match Nokia N900 phone. For a long time we have
> dirty patch in linux-n900 tree for it, see:
>
>
Hi,
* Pali Rohár [160102 06:46]:
> --- a/drivers/media/rc/ir-rx51.c
> +++ b/drivers/media/rc/ir-rx51.c
> @@ -25,9 +25,9 @@
> #include
> #include
> #include
> +#include
>
> -#include
> -#include
> +#include "../../../arch/arm/plat-omap/include/plat/dmtimer.h"
On Monday 28 December 2015 15:55:28 Arnd Bergmann wrote:
> On Monday 28 December 2015 15:54:35 Pali Rohár wrote:
> > On Monday 28 December 2015 15:41:01 Arnd Bergmann wrote:
> > > On Monday 28 December 2015 15:28:48 Pali Rohár wrote:
> > > > On Monday 28 December 2015 15:14:50 Arnd Bergmann wrote:
* Pali Rohár [160102 06:14]:
> Hello,
>
> now I'm looking at differences between legacy board code and DTS file
> for Nokia N900 and I see some inconsistency for twl4030-power driver.
>
> In board code are defined more twl4030 power scripts which override
> defaults
On Saturday 02 January 2016 16:22:03 Pali Rohár wrote:
> On Monday 28 December 2015 15:55:28 Arnd Bergmann wrote:
> > On Monday 28 December 2015 15:54:35 Pali Rohár wrote:
> > > >
> > > > I mean you can add the platform data to the omap_auxdata_lookup[]
> > > > table for this board.
> > >
> > >
On 01/02/2016 11:16 AM, Tony Lindgren wrote:
> * Pali Rohár [160102 06:31]:
>> Hello,
>>
>> MPU OPP table table (omap36xx_vddcore_volt_data) defined in
>> opp3xxx_data.c does not match Nokia N900 phone. For a long time we have
>> dirty patch in linux-n900 tree for it, see:
On 01/02/2016 03:26 PM, Pali Rohár wrote:
Hello,
due to this Daniel Lezcano commit (ARM: OMAP3: cpuidle - remove rx51
cpuidle parameters table)
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=231900afba52d6faddfb480cde4132d4edc089bc
we need patch cpuidle34xx.c code
On Saturday 02 January 2016 23:57:47 Arnd Bergmann wrote:
> On Saturday 02 January 2016 16:22:03 Pali Rohár wrote:
> > On Monday 28 December 2015 15:55:28 Arnd Bergmann wrote:
> > > On Monday 28 December 2015 15:54:35 Pali Rohár wrote:
> > > > > I mean you can add the platform data to the
> > > >
On Sunday 03 January 2016 00:03:54 Pali Rohár wrote:
> On Saturday 02 January 2016 23:57:47 Arnd Bergmann wrote:
> > On Saturday 02 January 2016 16:22:03 Pali Rohár wrote:
> > > On Monday 28 December 2015 15:55:28 Arnd Bergmann wrote:
> > > > On Monday 28 December 2015 15:54:35 Pali Rohár wrote:
>
On Saturday 02 January 2016 18:14:31 Tony Lindgren wrote:
> * Pali Rohár [160102 06:14]:
> > Hello,
> >
> > now I'm looking at differences between legacy board code and DTS
> > file for Nokia N900 and I see some inconsistency for twl4030-power
> > driver.
> >
> > In board
Hi, Grygorii
Thanks fot your reply.
On 12/28/15 at 02:15pm, Grygorii Strashko wrote:
> On 12/28/2015 09:18 AM, Dave Young wrote:
> > On 12/27/15 at 03:38pm, Dave Young wrote:
> >> Here is what I get when I test kdump on Beagle bone black:
> >>
> >> Added a printk line at the begin of function
Hi Tony,
On 21.05.2015 00:21, Tony Lindgren wrote:
We support decoding the bootloader values if DEBUG is defined.
But we also need to change the struct omap_hwmod flags to have
HWMOD_INIT_NO_RESET to avoid the GPMC being reset during the
boot. Otherwise just the default timings will be
Hi,
On 24.12.2015 20:56, Tony Lindgren wrote:
Maybe update the description to say "This fixes a regression with
device tree based booting compared to legacy booting for n900 to
make the n900 legacy user space to also work with device tree based
booting".
OK, will do.
It would be nice to
Hi Tomi! Can you review this patch? It is waiting here for two years!
On Thursday 26 December 2013 00:12:39 Ivaylo Dimitrov wrote:
> From: Ivaylo Dimitrov
>
> On memory limited devices, CMA fails easily when asked to allocate
> big chunks of memory like framebuffer memory
On 29.12.2015 09:46, Tomi Valkeinen wrote:
Oh, I'm sorry, I must have forgotten about that. Please, send a new patch.
Tomi
Actually it is me to be sorry for making noise, I've missed
0eb0dafb674cd6bfac2e3204b2f8b907e26b1138 with all those patches moving
files around.
Ivo
--
To
On Tuesday 22 December 2015 17:44:46 Tony Lindgren wrote:
> Add minimal SoC support for dra62x also known as j5eco. As it's closely
> related to dm814x, we can treat it as a dm814x variant for now and do
> rest of the configuration with DTS just files. And let's add hwmod
> support for MMC and USB
On Tuesday 22 December 2015 17:44:47 Tony Lindgren wrote:
> Add minimal device tree support for dra62x also known j5eco. It is
> related to dm814x, just the clocks are a bit different and it has a
> different set of integrated devices. And let's get some basic dm814x
> and dra62x devices working
On Tuesday 22 December 2015 17:44:45 Tony Lindgren wrote:
> Here are reworked pull requests to separate the dts changes as requested
> by Olof.
>
> The pull request below, and the third pull request in this series,
> still depend on the earlier branch omap-for-v4.5/81xx-fixes-signed.
> The pull
can we have a shorter title?
On Tue, Dec 29, 2015 at 02:46:49PM +0530, Keerthy wrote:
> Hi Nishanth,
>
> >
> >I am not sure if this #ifdeffery is even needed.
> >
> >
> >Eduardo, Rui: If this is not the suggested technique, maybe you guys
> >could suggest how we could handle a case where
On 12/31/2015 12:20 PM, Eduardo Valentin wrote:
> On Thu, Dec 31, 2015 at 11:47:57AM -0600, Nishanth Menon wrote:
>> On 12/31/2015 11:29 AM, Eduardo Valentin wrote:
>>> can we have a shorter title?
>>>
>>>
>>> Orderly power off is supposed to take care of this. Looking at the code,
>>> it will
On Mon, Dec 21, 2015 at 11:16:18AM +0530, Keerthy wrote:
> In few rare conditions like during boot up the orderly_poweroff
> function might not be able to complete fully leaving the device
> running at dangerously high temperatures. Hence adding a backup
> workqueue to act after a known period of
On Thu, Dec 31, 2015 at 11:47:57AM -0600, Nishanth Menon wrote:
> On 12/31/2015 11:29 AM, Eduardo Valentin wrote:
> > can we have a shorter title?
> >
> >
> > Orderly power off is supposed to take care of this. Looking at the code,
> > it will force a shutdown in case execution of userland
Hello,
On Sat, Dec 26, 2015 at 12:32:25AM +0100, Pali Rohár wrote:
> Driver for omap3 with documentation is there since v4.4-rc1.
>
> Signed-off-by: Pali Rohár
> ---
> arch/arm/boot/dts/omap34xx.dtsi |5 +
> arch/arm/boot/dts/omap36xx.dtsi |5 +
> 2
On 12/31/2015 11:29 AM, Eduardo Valentin wrote:
> can we have a shorter title?
>
> On Tue, Dec 29, 2015 at 02:46:49PM +0530, Keerthy wrote:
>> Hi Nishanth,
>>
>
>
>>>
>>> I am not sure if this #ifdeffery is even needed.
>>>
>>>
>>> Eduardo, Rui: If this is not the suggested technique, maybe
On Thu, Dec 31, 2015 at 10:59:06PM +0100, Paul Kocialkowski wrote:
> I understand, thanks for pointing this out. Well, for my use case, there
> is no use in disabling the chip at any point as it powers the external
> mmc.
Presumably someone might decide not to use the MMC in some case (perhaps
Le jeudi 31 décembre 2015 à 21:40 +, Mark Brown a écrit :
> On Wed, Dec 30, 2015 at 07:37:19PM +0100, Paul Kocialkowski wrote:
> > Le mercredi 30 décembre 2015 à 16:33 +, Mark Brown a écrit :
> > > On Wed, Dec 30, 2015 at 09:35:21AM +0100, Paul Kocialkowski wrote:
>
> > > > In my opinion,
On Wed, Dec 30, 2015 at 07:37:19PM +0100, Paul Kocialkowski wrote:
> Le mercredi 30 décembre 2015 à 16:33 +, Mark Brown a écrit :
> > On Wed, Dec 30, 2015 at 09:35:21AM +0100, Paul Kocialkowski wrote:
> > > In my opinion, it would be more elegant to adapt the core regulator
> > > framework to
Hi Tero,
Quoting Tero Kristo (2015-12-18 05:58:58)
> Previously, hwmod core has been used for controlling the hwmod level
> clocks. This has certain drawbacks, like being unable to share the
> clocks for multiple users, missing usecounting and generally being
> totally incompatible with common
Felipe,
On Tue, 29 Dec 2015, Felipe Balbi wrote:
> Anyway, the interesting part is that PRUSS has 64 events (on current
> incarnations at least) and PRUSS has 10 physical IRQ lines to the ARM
> land. Each of these 64 events can be routed to any of these 10 IRQ
> lines. This might not be very
On Wed, Dec 23, 2015 at 10:35:43AM +0200, Uri Mashiach wrote:
> Add DT support for the wl1271 SPI WiFi.
>
> Add documentation file for the wl1271 SPI WiFi.
>
> Signed-off-by: Uri Mashiach
> Acked-by: Igor Grinberg
> ---
>
On Wed, Dec 30, 2015 at 09:35:21AM +0100, Paul Kocialkowski wrote:
> In my opinion, it would be more elegant to adapt the core regulator
> framework to first enable the GPIO and then call the regulator enable
> ops callback instead of handling the GPIO in the driver.
Why would we want to
Le mercredi 30 décembre 2015 à 16:33 +, Mark Brown a écrit :
> On Wed, Dec 30, 2015 at 09:35:21AM +0100, Paul Kocialkowski wrote:
>
> > In my opinion, it would be more elegant to adapt the core regulator
> > framework to first enable the GPIO and then call the regulator enable
> > ops
Felipe,
On Wed, 30 Dec 2015, Felipe Balbi wrote:
> Thomas Gleixner writes:
> > - Is there a "mapping" block between PRUSS and the host interrupt
> > controller
> >or is this "mapping" block part of PRUSS?
>
> The description in TRM is a bit "poor", but from what I can
1 - 100 of 72025 matches
Mail list logo