All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: "adeos-main@gna.org" <adeos-main@gna.org>,
	"Mauerer, Wolfgang" <wolfgang.mauerer@domain.hid>
Subject: Re: [Adeos-main] [PATCH 1/2] ipipe: Pass NTP-corrected time information from Linux to higher domains
Date: Wed, 25 Aug 2010 11:19:30 +0200	[thread overview]
Message-ID: <4C74E022.8030105@domain.hid> (raw)
In-Reply-To: <1282727242.1709.26.camel@domain.hid>

Philippe Gerum wrote:
> On Wed, 2010-08-25 at 10:58 +0200, Jan Kiszka wrote:
>> Philippe Gerum wrote:
>>> On Wed, 2010-08-25 at 10:50 +0200, Jan Kiszka wrote:
>>>> Philippe Gerum wrote:
>>>>> On Fri, 2010-07-02 at 13:50 +0200, Wolfgang Mauerer wrote:
>>>>>
>>>>> <snip>
>>>>>
>>>>>> diff --git a/include/linux/ipipe_tickdev.h b/include/linux/ipipe_tickdev.h
>>>>>> index 4a1cb1b..86f13e0 100644
>>>>>> --- a/include/linux/ipipe_tickdev.h
>>>>>> +++ b/include/linux/ipipe_tickdev.h
>>>>>> @@ -25,6 +25,7 @@
>>>>>>  #if defined(CONFIG_IPIPE) && defined(CONFIG_GENERIC_CLOCKEVENTS)
>>>>> Since we should have CONFIG_HAVE_IPIPE_HOSTRT by now, let's use it.
>>>> Don't get yet how this fits here.
>>> arch-dep would define CONFIG_HAVE_IPIPE_HOSTRT [if IPIPE]
>>>
>> Still don't see the relation to the line you cited above.
>>
> 
> That is because you chose to have CONFIG_IPIPE_HOSTRT and
> CONFIG_HAVE_IPIPE_HOSTRT. I would have only defined the latter, the way
> you define the former. I'm looking for the hostrt support to be compiled
> in if CONFIG_HAVE_IPIPE_HOSTRT is available from the arch-dep section,
> so we don't need CONFIG_IPIPE_HOSTRT. Generic bits may depend on HAVE_*
> as well.

First of all, the code you cited _above_ is not changed by our patches,
so the context still puzzles me (but maybe you are referring to some
other place in fact).

Second, CONFIG_HAVE_IPIPE_HOSTRT is designed to be set independently of
CONFIG_IPIPE - it's a static arch feature like all the other
CONFIG_HAVE_* in arch/*/Kconfig. So it takes a second, generically
defined CONFIG switch if the generic support also depends on
CONFIG_IPIPE like in this case. That's a kernel convention we follow. If
you want us to do it I-pipe-specific, no problem, I just want to have
this pointed out.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux


  reply	other threads:[~2010-08-25  9:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02 11:49 [Adeos-main] [PATCH 0/2] Host realtime clock support Wolfgang Mauerer
2010-07-02 11:50 ` [Adeos-main] [PATCH 1/2] ipipe: Pass NTP-corrected time information from Linux to higher domains Wolfgang Mauerer
2010-08-25  8:44   ` Philippe Gerum
2010-08-25  8:50     ` Jan Kiszka
2010-08-25  8:53       ` Philippe Gerum
2010-08-25  8:58         ` Jan Kiszka
2010-08-25  9:07           ` Philippe Gerum
2010-08-25  9:19             ` Jan Kiszka [this message]
2010-08-25  9:27               ` Philippe Gerum
2010-08-25 10:25                 ` Jan Kiszka
2010-08-25 11:23                   ` Philippe Gerum
2010-08-26  9:38                     ` Jan Kiszka
2010-08-26 10:37                       ` Philippe Gerum
2010-08-26 10:47                         ` Jan Kiszka
2010-08-26 10:49                           ` Philippe Gerum
2010-07-02 11:50 ` [Adeos-main] [PATCH 2/2] ipipe: CLOCK_HOST_REALTIME: x86-specific part Wolfgang Mauerer
2010-07-02 13:40   ` Gilles Chanteperdrix
2010-08-25  8:52   ` Philippe Gerum
2010-08-25  8:58     ` Jan Kiszka
2010-08-25  9:20       ` Philippe Gerum
2010-08-25  9:32         ` Jan Kiszka
2010-08-25  9:38           ` Philippe Gerum
  -- strict thread matches above, loose matches on Subject: below --
2010-07-08 10:20 [Adeos-main] [PATCH v2 0/2] Host realtime clock support Wolfgang Mauerer
2010-07-08 10:20 ` [Adeos-main] [PATCH 1/2] ipipe: Pass NTP-corrected time information from Linux to higher domains Wolfgang Mauerer

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=4C74E022.8030105@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=rpm@xenomai.org \
    --cc=wolfgang.mauerer@domain.hid \
    /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.