public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stotland, Inga" <inga.stotland@intel.com>
To: "michal.lowas-rzechonek@silvair.com" 
	<michal.lowas-rzechonek@silvair.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Cc: "Gix, Brian" <brian.gix@intel.com>
Subject: Re: [PATCH BlueZ v2] mesh: Set global bus earlier
Date: Fri, 29 Jul 2022 06:01:10 +0000	[thread overview]
Message-ID: <2e1acb1b01a42f4e6503cc12d5e866bf355655b5.camel@intel.com> (raw)
In-Reply-To: <20220725080549.4163484-1-michal.lowas-rzechonek@silvair.com>

Hi Michał,

On Mon, 2022-07-25 at 10:05 +0200, Michał Lowas-Rzechonek wrote:
> Some io implementations might want to either make calls to other D-
> Bus
> services, or provide additional objects/interfaces that allow
> applications to fine-tune their operation, so allow them to use the
> bus
> even before initializing mesh D-Bus interfaces.
> ---
>  mesh/dbus.c | 8 ++++++++
>  mesh/dbus.h | 1 +
>  mesh/main.c | 2 ++
>  3 files changed, 11 insertions(+)
> 
> diff --git a/mesh/dbus.c b/mesh/dbus.c
> index a7abdc428..6e62abd27 100644
> --- a/mesh/dbus.c
> +++ b/mesh/dbus.c
> @@ -75,6 +75,11 @@ struct l_dbus_message *dbus_error(struct
> l_dbus_message *msg, int err,
>                                 "%s", error_table[err].default_desc);
>  }
>  
> +void dbus_set_bus(struct l_dbus *bus)
> +{
> +       dbus = bus;
> +}
> +
>  struct l_dbus *dbus_get_bus(void)
>  {
>         return dbus;
> @@ -82,6 +87,9 @@ struct l_dbus *dbus_get_bus(void)
>  
>  bool dbus_init(struct l_dbus *bus)
>  {
> +       if (dbus != bus)
> +               return false;
> +


Since dbus_set_bus() is called prior to dbus_init(), wouldn't it make
sense  to eliminate an input parameter for dbus_init() and to perform a
check (dbus != NULL) and also eliminate 
"dbus = bus" statement at the end of dbus_init()?


>         /* Network interface */
>         if (!mesh_dbus_init(bus))
>                 return false;
> diff --git a/mesh/dbus.h b/mesh/dbus.h
> index 8f00434d6..ab8b0a2cc 100644
> --- a/mesh/dbus.h
> +++ b/mesh/dbus.h
> @@ -14,6 +14,7 @@
>  #define DEFAULT_DBUS_TIMEOUT   30
>  
>  bool dbus_init(struct l_dbus *dbus);
> +void dbus_set_bus(struct l_dbus *bus);
>  struct l_dbus *dbus_get_bus(void);
>  void dbus_append_byte_array(struct l_dbus_message_builder *builder,
>                                                 const uint8_t *data,
> int len);
> diff --git a/mesh/main.c b/mesh/main.c
> index dd99c3085..0180c3768 100644
> --- a/mesh/main.c
> +++ b/mesh/main.c
> @@ -278,6 +278,8 @@ int main(int argc, char *argv[])
>                 goto done;
>         }
>  
> +       dbus_set_bus(dbus);
> +

It is better to call dbus_set_bus from within ready_callback()

>         if (dbus_debug)
>                 l_dbus_set_debug(dbus, do_debug, "[DBUS] ", NULL);
>         l_dbus_set_ready_handler(dbus, ready_callback, dbus, NULL);

Best regards,

Inga

      parent reply	other threads:[~2022-07-29  6:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25  8:05 [PATCH BlueZ v2] mesh: Set global bus earlier Michał Lowas-Rzechonek
2022-07-25  9:09 ` [BlueZ,v2] " bluez.test.bot
2022-07-29  6:01 ` Stotland, Inga [this message]

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=2e1acb1b01a42f4e6503cc12d5e866bf355655b5.camel@intel.com \
    --to=inga.stotland@intel.com \
    --cc=brian.gix@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=michal.lowas-rzechonek@silvair.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox