From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753053AbbHEOCZ (ORCPT ); Wed, 5 Aug 2015 10:02:25 -0400 Received: from mga09.intel.com ([134.134.136.24]:57224 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751269AbbHEOCX (ORCPT ); Wed, 5 Aug 2015 10:02:23 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,617,1432623600"; d="scan'208";a="762486738" Message-ID: <1438783338.29746.172.camel@linux.intel.com> Subject: Re: [PATCH 1/5] device property: helper macros for property entry creation From: Andy Shevchenko To: Heikki Krogerus , Johannes Berg Cc: "Rafael J. Wysocki" , Mika Westerberg , linux-wireless@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org Date: Wed, 05 Aug 2015 17:02:18 +0300 In-Reply-To: <1438781947-7952-2-git-send-email-heikki.krogerus@linux.intel.com> References: <1438781947-7952-1-git-send-email-heikki.krogerus@linux.intel.com> <1438781947-7952-2-git-send-email-heikki.krogerus@linux.intel.com> Organization: Intel Finland Oy Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.3-1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2015-08-05 at 16:39 +0300, Heikki Krogerus wrote: > Marcos for easier creation of build-in property entries. > > Signed-off-by: Heikki Krogerus > --- > include/linux/property.h | 35 +++++++++++++++++++++++++++++++++++ > 1 file changed, 35 insertions(+) > > diff --git a/include/linux/property.h b/include/linux/property.h > index 76ebde9..204d899 100644 > --- a/include/linux/property.h > +++ b/include/linux/property.h > @@ -152,6 +152,41 @@ struct property_entry { > } value; > }; > > +#define PROP_ENTRY_U8(_name_, _val_) { \ PROP_ prefix is too generic. Maybe DEVPROP_ ? At least for the latter no records in the current sources. > + .name = _name_, \ > + .type = DEV_PROP_U8, \ > + .nval = 1, \ > + .value.u8_data = _val_, \ > +} > + > +#define PROP_ENTRY_U16(_name_, _val_) { \ > + .name = _name_, \ > + .type = DEV_PROP_U16, \ > + .nval = 1, \ > + .value.u16_data = _val_, \ > +} > + > +#define PROP_ENTRY_U32(_name_, _val_) { \ > + .name = _name_, \ > + .type = DEV_PROP_U32, \ > + .nval = 1, \ > + .value.u32_data = _val_, \ > +} > + > +#define PROP_ENTRY_U64(_name_, _val_) { \ > + .name = _name_, \ > + .type = DEV_PROP_U64, \ > + .nval = 1, \ > + .value.u64_data = _val_, \ > +} > + > +#define PROP_ENTRY_STRING(_name_, _val_) { \ …_STRING_ARRAY I can notice. > + .name = _name_, \ > + .type = DEV_PROP_STRING, \ > + .nval = 1, \ > + .value.str = (const char **)_val_, \ > +} > + > /** > * struct property_set - Collection of "built-in" device properties. > * @fwnode: Handle to be pointed to by the fwnode field of struct > device. -- Andy Shevchenko Intel Finland Oy