All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Tero Kristo <t-kristo@ti.com>,
	"H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
	devicetree@vger.kernel.org,
	"Discussions about the Letux Kernel"
	<letux-kernel@openphoenux.org>,
	"Russell King" <linux@arm.linux.org.uk>,
	"Pawel Moll" <pawel.moll@arm.com>,
	"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
	"Tony Lindgren" <tony@atomide.com>,
	kernel@pyra-handheld.com, LKML <linux-kernel@vger.kernel.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Laxman Dewangan" <ldewangan@nvidia.com>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	"Kumar Gala" <galak@codeaurora.org>,
	"Marek Belisko" <marek@goldelico.com>,
	linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [Kernel] [PATCH v2 4/5] ARM: dts: omap5: describe control for ckobuffer
Date: Mon, 9 May 2016 18:28:12 +0300	[thread overview]
Message-ID: <6c0e639c-31b9-b8af-85d6-187d3706595b@ti.com> (raw)
In-Reply-To: <57309A08.10704@ti.com>

On 05/09/2016 05:09 PM, Tero Kristo wrote:
>>> Applying Tero's alone makes the board not to boot, so something there... I can
>>> not see anything even with low-level debugging enabled :( I can not debug it
>>> further today, will look at this tomorrow.
>>
>> The crash is in arch/arm/mach-omap2/control.c:omap_control_init()
>>
>> the syscon_node_to_regmap() returns with error for the new
>> omap5_scm_wkup_pad_conf node. The other syscon was OK, but becasue of the
>> return PTR_ERR(syscon) the board will not boot...
>>
>> Tero: any idea?
> 
> I can check this tomorrow at my end.

Aargh, I think I know why, I have placed the omap5_scm_wkup_pad_conf node to a
wrong place. The inline patch did not applied so I did it by hand...
I can boot test it tomorrow.

> 
> -Tero
> 
>>
>>>> In any case I have attached the 3 patches I have for this, including Tero's
>>>> ported to linux-next.
>>>>
>>>> Patch 3 might need to be done per board probably, but this should be good for
>>>> testing.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Kernel mailing list
>>>> Kernel@pyra-handheld.com
>>>> http://pyra-handheld.com/cgi-bin/mailman/listinfo/kernel
>>>>
>>>
>>>
>>
>>
> 


-- 
Péter

WARNING: multiple messages have this Message-ID (diff)
From: Peter Ujfalusi <peter.ujfalusi-l0cyMroinI0@public.gmane.org>
To: Tero Kristo <t-kristo-l0cyMroinI0@public.gmane.org>,
	"H. Nikolaus Schaller"
	<hns-xXXSsgcRVICgSpxsJD1C4w@public.gmane.org>
Cc: "Mark Rutland" <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	"Discussions about the Letux Kernel"
	<letux-kernel-S0jZdbWzriLCfDggNXIi3w@public.gmane.org>,
	"Russell King" <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
	"Pawel Moll" <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
	"Ian Campbell"
	<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
	"Tony Lindgren" <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
	kernel-Jl6IXVxNIMRxAtABVqVhTwC/G2K4zDHf@public.gmane.org,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"Rob Herring" <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	"Laxman Dewangan"
	<ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	"Benoît Cousson"
	<bcousson-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
	"Kumar Gala" <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
	"Marek Belisko" <marek-xXXSsgcRVICgSpxsJD1C4w@public.gmane.org>,
	linux-omap <linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [Kernel] [PATCH v2 4/5] ARM: dts: omap5: describe control for ckobuffer
Date: Mon, 9 May 2016 18:28:12 +0300	[thread overview]
Message-ID: <6c0e639c-31b9-b8af-85d6-187d3706595b@ti.com> (raw)
In-Reply-To: <57309A08.10704-l0cyMroinI0@public.gmane.org>

On 05/09/2016 05:09 PM, Tero Kristo wrote:
>>> Applying Tero's alone makes the board not to boot, so something there... I can
>>> not see anything even with low-level debugging enabled :( I can not debug it
>>> further today, will look at this tomorrow.
>>
>> The crash is in arch/arm/mach-omap2/control.c:omap_control_init()
>>
>> the syscon_node_to_regmap() returns with error for the new
>> omap5_scm_wkup_pad_conf node. The other syscon was OK, but becasue of the
>> return PTR_ERR(syscon) the board will not boot...
>>
>> Tero: any idea?
> 
> I can check this tomorrow at my end.

Aargh, I think I know why, I have placed the omap5_scm_wkup_pad_conf node to a
wrong place. The inline patch did not applied so I did it by hand...
I can boot test it tomorrow.

> 
> -Tero
> 
>>
>>>> In any case I have attached the 3 patches I have for this, including Tero's
>>>> ported to linux-next.
>>>>
>>>> Patch 3 might need to be done per board probably, but this should be good for
>>>> testing.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Kernel mailing list
>>>> Kernel-Jl6IXVxNIMRxAtABVqVhTwC/G2K4zDHf@public.gmane.org
>>>> http://pyra-handheld.com/cgi-bin/mailman/listinfo/kernel
>>>>
>>>
>>>
>>
>>
> 


-- 
Péter
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-05-09 15:29 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 18:20 [PATCH v2 0/5] DT Fixes for OMAP4 and OMAP5 boards H. Nikolaus Schaller
2016-04-18 18:20 ` [PATCH v2 1/5] ARM: dts: twl6030: describe gpadc H. Nikolaus Schaller
2016-04-26 17:26   ` Tony Lindgren
2016-04-26 17:26     ` Tony Lindgren
2016-04-18 18:20 ` [PATCH v2 2/5] ARM: dts: omap5-board-common: describe gpadc for Palmas H. Nikolaus Schaller
2016-04-18 18:20 ` [PATCH v2 3/5] ARM: dts: omap5: fix range of permitted wakeup pinmux registers H. Nikolaus Schaller
2016-04-26 17:23   ` Tony Lindgren
2016-04-18 18:21 ` [PATCH v2 4/5] ARM: dts: omap5: describe control for ckobuffer H. Nikolaus Schaller
2016-04-26 17:27   ` Tony Lindgren
2016-04-26 17:27     ` Tony Lindgren
2016-04-27  6:04     ` H. Nikolaus Schaller
2016-04-27  6:04       ` H. Nikolaus Schaller
2016-04-27 12:31       ` Tero Kristo
2016-04-27 13:10         ` H. Nikolaus Schaller
2016-04-27 14:10           ` Tero Kristo
2016-04-27 14:10             ` Tero Kristo
2016-04-27 14:23             ` Peter Ujfalusi
2016-04-27 14:35               ` H. Nikolaus Schaller
2016-04-28  8:03                 ` Tero Kristo
2016-04-28  9:12                   ` H. Nikolaus Schaller
2016-04-28 13:23                     ` Tero Kristo
2016-05-09 11:18                       ` H. Nikolaus Schaller
2016-05-09 11:18                         ` H. Nikolaus Schaller
2016-05-09 11:52                         ` Tero Kristo
2016-05-09 11:52                           ` Tero Kristo
2016-05-09 12:10                           ` Peter Ujfalusi
2016-05-09 12:32                             ` [Kernel] " Peter Ujfalusi
2016-05-09 12:46                               ` Peter Ujfalusi
2016-05-09 13:52                                 ` Peter Ujfalusi
2016-05-09 14:09                                   ` Tero Kristo
2016-05-09 14:09                                     ` Tero Kristo
2016-05-09 15:28                                     ` Peter Ujfalusi [this message]
2016-05-09 15:28                                       ` Peter Ujfalusi
2016-05-09 19:44                               ` Peter Ujfalusi
2016-05-09 19:44                                 ` Peter Ujfalusi
2016-05-10  5:45                           ` H. Nikolaus Schaller
2016-05-10  5:45                             ` H. Nikolaus Schaller
2016-04-18 18:21 ` [PATCH v2 5/5] ARM: dts: omap5-board-common: set up ckobuffer for twl6040 H. Nikolaus Schaller
2016-04-18 18:21   ` H. Nikolaus Schaller
2016-04-26 15:00 ` [PATCH v2 0/5] DT Fixes for OMAP4 and OMAP5 boards H. Nikolaus Schaller
2016-04-26 15:00   ` H. Nikolaus Schaller
2016-04-26 17:28   ` Tony Lindgren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6c0e639c-31b9-b8af-85d6-187d3706595b@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=hns@goldelico.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kernel@pyra-handheld.com \
    --cc=ldewangan@nvidia.com \
    --cc=letux-kernel@openphoenux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=marek@goldelico.com \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=t-kristo@ti.com \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.