All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Andrew Chew <AChew-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: Peter De Schrijver
	<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Prashant Gaikwad
	<pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Mike Turquette
	<mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] clk: tegra: provide dummy cpu car ops
Date: Wed, 06 Mar 2013 17:04:33 -0700	[thread overview]
Message-ID: <5137D991.7080808@wwwdotorg.org> (raw)
In-Reply-To: <643E69AA4436674C8F39DCC2C05F7638629CA50CC0-lR+7xdUAJVNDw2glCA4ptUEOCMrvLtNR@public.gmane.org>

On 03/06/2013 04:59 PM, Andrew Chew wrote:
>> From: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org [mailto:linux-tegra-
>> owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org] On Behalf Of Stephen Warren
>> Sent: Wednesday, March 06, 2013 3:43 PM
>> To: Andrew Chew
>> Cc: Peter De Schrijver; linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; linux-arm-
>> kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org; Stephen Warren; Prashant Gaikwad; Mike
>> Turquette; linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> Subject: Re: [PATCH] clk: tegra: provide dummy cpu car ops
>>
>> On 03/06/2013 04:20 PM, Andrew Chew wrote:
>>>> Subject: [PATCH] clk: tegra: provide dummy cpu car ops
>>>>
>>>> tegra_boot_secondary() relies on some of the car ops. This means
>>>> having an uninitialized tegra_cpu_car_ops will lead to an early boot panic.
>>>> Providing a dummy struct avoids this and makes adding Tegra114 clock
>>>> support in a bisectable way a lot easier.
>>>>
>>>> --
>>>>
>>>> Stephen,
>>>>
>>>> Should this be a separate patch or should I make this part of new
>>>> release of the Tegra114 clock series?
>>
>> I'm not sure if I answered this. Peter, I intend to apply this patch to a branch
>> right before the CCF, so there's no explicit need to include it in the series,
>> although if you do, that's fine.
>>
>>>> diff --git a/drivers/clk/tegra/clk.c b/drivers/clk/tegra/clk.c index
>>
>>>>  /* Global data of Tegra CPU CAR ops */ -struct tegra_cpu_car_ops
>>>> *tegra_cpu_car_ops;
>>>
>>> Sorry for bringing this up so late...
>>> Shouldn't the above be "struct tegra_cpu_car_ops tegra_cpu_car_ops;"?
>>>
>>>> +static struct tegra_cpu_car_ops *dummy_car_ops; struct
>>>> +tegra_cpu_car_ops *tegra_cpu_car_ops = &dummy_car_ops;
>>
>> No, the value is used as a pointer in include/linux/clk/tegra.h, e.g.:
>>
>> tegra_cpu_car_ops->wait_for_reset(cpu);
> 
> Yeah, I get that tegra_cpu_car_ops is a pointer to an ops table.  It seems
> to me that what's happening above is that tegra_cpu_car_ops is getting
> assigned a pointer to a pointer that's supposed to point to an instance of
> struct tegra_cpu_car_ops (but it really points to NULL as far as I can tell).
> In any case, dummy_car_ops never actually gets instantiated.
> 
> I assume the intention is for dummy_car_ops to be an instance of
> struct tegra_cpu_car_ops, but with all of its members zero'd.

Oh right, I guess your comment was about the line after where you wrote
it rather than the line before.

So, you mean:

static struct tegra_cpu_car_ops *dummy_car_ops;
struct tegra_cpu_car_ops *tegra_cpu_car_ops = &dummy_car_ops;

should be instead:

static struct tegra_cpu_car_ops dummy_car_ops;
struct tegra_cpu_car_ops *tegra_cpu_car_ops = &dummy_car_ops;

Yes, you're right.

WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: tegra: provide dummy cpu car ops
Date: Wed, 06 Mar 2013 17:04:33 -0700	[thread overview]
Message-ID: <5137D991.7080808@wwwdotorg.org> (raw)
In-Reply-To: <643E69AA4436674C8F39DCC2C05F7638629CA50CC0@HQMAIL03.nvidia.com>

On 03/06/2013 04:59 PM, Andrew Chew wrote:
>> From: linux-tegra-owner at vger.kernel.org [mailto:linux-tegra-
>> owner at vger.kernel.org] On Behalf Of Stephen Warren
>> Sent: Wednesday, March 06, 2013 3:43 PM
>> To: Andrew Chew
>> Cc: Peter De Schrijver; linux-tegra at vger.kernel.org; linux-arm-
>> kernel at lists.infradead.org; Stephen Warren; Prashant Gaikwad; Mike
>> Turquette; linux-kernel at vger.kernel.org
>> Subject: Re: [PATCH] clk: tegra: provide dummy cpu car ops
>>
>> On 03/06/2013 04:20 PM, Andrew Chew wrote:
>>>> Subject: [PATCH] clk: tegra: provide dummy cpu car ops
>>>>
>>>> tegra_boot_secondary() relies on some of the car ops. This means
>>>> having an uninitialized tegra_cpu_car_ops will lead to an early boot panic.
>>>> Providing a dummy struct avoids this and makes adding Tegra114 clock
>>>> support in a bisectable way a lot easier.
>>>>
>>>> --
>>>>
>>>> Stephen,
>>>>
>>>> Should this be a separate patch or should I make this part of new
>>>> release of the Tegra114 clock series?
>>
>> I'm not sure if I answered this. Peter, I intend to apply this patch to a branch
>> right before the CCF, so there's no explicit need to include it in the series,
>> although if you do, that's fine.
>>
>>>> diff --git a/drivers/clk/tegra/clk.c b/drivers/clk/tegra/clk.c index
>>
>>>>  /* Global data of Tegra CPU CAR ops */ -struct tegra_cpu_car_ops
>>>> *tegra_cpu_car_ops;
>>>
>>> Sorry for bringing this up so late...
>>> Shouldn't the above be "struct tegra_cpu_car_ops tegra_cpu_car_ops;"?
>>>
>>>> +static struct tegra_cpu_car_ops *dummy_car_ops; struct
>>>> +tegra_cpu_car_ops *tegra_cpu_car_ops = &dummy_car_ops;
>>
>> No, the value is used as a pointer in include/linux/clk/tegra.h, e.g.:
>>
>> tegra_cpu_car_ops->wait_for_reset(cpu);
> 
> Yeah, I get that tegra_cpu_car_ops is a pointer to an ops table.  It seems
> to me that what's happening above is that tegra_cpu_car_ops is getting
> assigned a pointer to a pointer that's supposed to point to an instance of
> struct tegra_cpu_car_ops (but it really points to NULL as far as I can tell).
> In any case, dummy_car_ops never actually gets instantiated.
> 
> I assume the intention is for dummy_car_ops to be an instance of
> struct tegra_cpu_car_ops, but with all of its members zero'd.

Oh right, I guess your comment was about the line after where you wrote
it rather than the line before.

So, you mean:

static struct tegra_cpu_car_ops *dummy_car_ops;
struct tegra_cpu_car_ops *tegra_cpu_car_ops = &dummy_car_ops;

should be instead:

static struct tegra_cpu_car_ops dummy_car_ops;
struct tegra_cpu_car_ops *tegra_cpu_car_ops = &dummy_car_ops;

Yes, you're right.

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Andrew Chew <AChew@nvidia.com>
Cc: Peter De Schrijver <pdeschrijver@nvidia.com>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Stephen Warren <swarren@nvidia.com>,
	Prashant Gaikwad <pgaikwad@nvidia.com>,
	Mike Turquette <mturquette@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clk: tegra: provide dummy cpu car ops
Date: Wed, 06 Mar 2013 17:04:33 -0700	[thread overview]
Message-ID: <5137D991.7080808@wwwdotorg.org> (raw)
In-Reply-To: <643E69AA4436674C8F39DCC2C05F7638629CA50CC0@HQMAIL03.nvidia.com>

On 03/06/2013 04:59 PM, Andrew Chew wrote:
>> From: linux-tegra-owner@vger.kernel.org [mailto:linux-tegra-
>> owner@vger.kernel.org] On Behalf Of Stephen Warren
>> Sent: Wednesday, March 06, 2013 3:43 PM
>> To: Andrew Chew
>> Cc: Peter De Schrijver; linux-tegra@vger.kernel.org; linux-arm-
>> kernel@lists.infradead.org; Stephen Warren; Prashant Gaikwad; Mike
>> Turquette; linux-kernel@vger.kernel.org
>> Subject: Re: [PATCH] clk: tegra: provide dummy cpu car ops
>>
>> On 03/06/2013 04:20 PM, Andrew Chew wrote:
>>>> Subject: [PATCH] clk: tegra: provide dummy cpu car ops
>>>>
>>>> tegra_boot_secondary() relies on some of the car ops. This means
>>>> having an uninitialized tegra_cpu_car_ops will lead to an early boot panic.
>>>> Providing a dummy struct avoids this and makes adding Tegra114 clock
>>>> support in a bisectable way a lot easier.
>>>>
>>>> --
>>>>
>>>> Stephen,
>>>>
>>>> Should this be a separate patch or should I make this part of new
>>>> release of the Tegra114 clock series?
>>
>> I'm not sure if I answered this. Peter, I intend to apply this patch to a branch
>> right before the CCF, so there's no explicit need to include it in the series,
>> although if you do, that's fine.
>>
>>>> diff --git a/drivers/clk/tegra/clk.c b/drivers/clk/tegra/clk.c index
>>
>>>>  /* Global data of Tegra CPU CAR ops */ -struct tegra_cpu_car_ops
>>>> *tegra_cpu_car_ops;
>>>
>>> Sorry for bringing this up so late...
>>> Shouldn't the above be "struct tegra_cpu_car_ops tegra_cpu_car_ops;"?
>>>
>>>> +static struct tegra_cpu_car_ops *dummy_car_ops; struct
>>>> +tegra_cpu_car_ops *tegra_cpu_car_ops = &dummy_car_ops;
>>
>> No, the value is used as a pointer in include/linux/clk/tegra.h, e.g.:
>>
>> tegra_cpu_car_ops->wait_for_reset(cpu);
> 
> Yeah, I get that tegra_cpu_car_ops is a pointer to an ops table.  It seems
> to me that what's happening above is that tegra_cpu_car_ops is getting
> assigned a pointer to a pointer that's supposed to point to an instance of
> struct tegra_cpu_car_ops (but it really points to NULL as far as I can tell).
> In any case, dummy_car_ops never actually gets instantiated.
> 
> I assume the intention is for dummy_car_ops to be an instance of
> struct tegra_cpu_car_ops, but with all of its members zero'd.

Oh right, I guess your comment was about the line after where you wrote
it rather than the line before.

So, you mean:

static struct tegra_cpu_car_ops *dummy_car_ops;
struct tegra_cpu_car_ops *tegra_cpu_car_ops = &dummy_car_ops;

should be instead:

static struct tegra_cpu_car_ops dummy_car_ops;
struct tegra_cpu_car_ops *tegra_cpu_car_ops = &dummy_car_ops;

Yes, you're right.

  parent reply	other threads:[~2013-03-07  0:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 14:52 [PATCH] clk: tegra: provide dummy cpu car ops Peter De Schrijver
2013-02-14 14:52 ` Peter De Schrijver
2013-02-14 14:52 ` Peter De Schrijver
2013-02-14 17:43 ` Stephen Warren
2013-02-14 17:43   ` Stephen Warren
2013-03-06 23:20 ` Andrew Chew
2013-03-06 23:20   ` Andrew Chew
2013-03-06 23:20   ` Andrew Chew
     [not found]   ` <643E69AA4436674C8F39DCC2C05F7638629CA50C97-lR+7xdUAJVNDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2013-03-06 23:42     ` Stephen Warren
2013-03-06 23:42       ` Stephen Warren
2013-03-06 23:42       ` Stephen Warren
     [not found]       ` <5137D47D.6030105-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-03-06 23:59         ` Andrew Chew
2013-03-06 23:59           ` Andrew Chew
2013-03-06 23:59           ` Andrew Chew
     [not found]           ` <643E69AA4436674C8F39DCC2C05F7638629CA50CC0-lR+7xdUAJVNDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2013-03-07  0:04             ` Stephen Warren [this message]
2013-03-07  0:04               ` Stephen Warren
2013-03-07  0:04               ` Stephen Warren

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=5137D991.7080808@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=AChew-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    /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.