From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2 1/3] software node: implement reference properties
Date: Sat, 7 Sep 2019 09:32:40 -0700 [thread overview]
Message-ID: <20190907163240.GA27112@dtor-ws> (raw)
In-Reply-To: <20190907160819.GH2680@smile.fi.intel.com>
On Sat, Sep 07, 2019 at 07:08:19PM +0300, Andy Shevchenko wrote:
> On Fri, Sep 06, 2019 at 03:26:09PM -0700, Dmitry Torokhov wrote:
> > It is possible to store references to software nodes in the same fashion as
> > other static properties, so that users do not need to define separate
> > structures:
> >
> > static const struct software_node gpio_bank_b_node = {
> > .name = "B",
> > };
> >
> > static const struct property_entry simone_key_enter_props[] = {
> > PROPERTY_ENTRY_U32("linux,code", KEY_ENTER),
> > PROPERTY_ENTRY_STRING("label", "enter"),
> > PROPERTY_ENTRY_REF("gpios", &gpio_bank_b_node, 123, GPIO_ACTIVE_LOW),
> > { }
> > };
> >
>
> Thanks for an update, my comments below.
>
> > + } else if (src->type == DEV_PROP_REF) {
> > + /* All reference properties must be arrays */
> > + return -EINVAL;
>
> Hmm... What about to duplicate pointer under value union and use is_array to
> distinguish which one to use? Because...
Then we have to special-case copying this entry, similar to the pains we
are going with the strings.
>
>
> > @@ -240,6 +254,7 @@ struct property_entry {
> > const u32 *u32_data;
> > const u64 *u64_data;
> > const char * const *str;
> > + const struct software_node_ref_args *ref;
> > } pointer;
>
> > +#define PROPERTY_ENTRY_REF(_name_, _ref_, ...) \
> > +(struct property_entry) { \
> > + .name = _name_, \
>
> > + .length = sizeof(struct software_node_ref_args), \
>
> Is it correct?
Yes, we length is element size * number of elements.
>
> > + .type = DEV_PROP_REF, \
>
> > + .is_array = true, \
>
> I really don't like this "cheating".
This is not cheating. Any single value can be represented as an array of
one element. Actually, the only reason we have this "is_array" business
is because for scalar values and short strings it is much cheaper to
store single value in-line instead of out of line + pointer, especially
on 64 bit arches.
If you want we can change is_array into is_inline.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2019-09-07 16:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 22:26 [PATCH v2 1/3] software node: implement reference properties Dmitry Torokhov
2019-09-06 22:26 ` [PATCH v2 2/3] platform/x86: intel_cht_int33fe: use inline " Dmitry Torokhov
2019-09-07 16:12 ` Andy Shevchenko
2019-09-06 22:26 ` [PATCH v2 3/3] software node: remove separate handling of references Dmitry Torokhov
2019-09-07 16:13 ` Andy Shevchenko
2019-09-07 16:08 ` [PATCH v2 1/3] software node: implement reference properties Andy Shevchenko
2019-09-07 16:32 ` Dmitry Torokhov [this message]
2019-09-07 17:12 ` Andy Shevchenko
2019-09-07 17:37 ` Dmitry Torokhov
2019-09-07 18:03 ` Andy Shevchenko
2019-09-07 18:23 ` Dmitry Torokhov
2019-09-09 10:09 ` Andy Shevchenko
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=20190907163240.GA27112@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.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.