From: Arnd Bergmann <arnd@arndb.de> To: Pankaj Dubey <pankaj.dubey@samsung.com> Cc: linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org, kgene.kim@samsung.com, linux@arm.linux.org.uk, heiko@sntech.de, Linus Walleij <linus.walleij@linaro.org>, tomasz.figa@gmail.com, Rob Herring <robh+dt@kernel.org>, thomas.ab@samsung.com, Grant Likely <grant.likely@linaro.org> Subject: Re: [PATCH v4 1/2] soc: samsung: add exynos chipid driver support Date: Thu, 04 Dec 2014 10:12:24 +0100 [thread overview] Message-ID: <4074205.TGQpWxTihh@wuerfel> (raw) In-Reply-To: <547FEA74.1010900@samsung.com> On Thursday 04 December 2014 10:30:36 Pankaj Dubey wrote: > > > > On Wednesday 03 December 2014 13:47:37 Pankaj Dubey wrote: > > > >> + soc_dev_attr->soc_id = exynos_product_id_to_name(soc_product_id); > >> + > >> + soc_dev = soc_device_register(soc_dev_attr); > >> + if (IS_ERR(soc_dev)) > >> + goto free_rev; > >> + > >> + device_create_file(soc_device_to_device(soc_dev), &exynos_product_attr); > >> + device_create_file(soc_device_to_device(soc_dev), > >> + &exynos_main_rev_attr); > >> + device_create_file(soc_device_to_device(soc_dev), &exynos_sub_rev_attr); > >> + > > > > I don't like the idea of having three extra nonstandard properties here, > > especially when you are not using the machine field for anything useful. > > > > I did not get you here. Any suggestions how we can use 'machine' field > more useful way. For instance you could pass the exynos_product_id_to_name() result to the machine field instead of the soc_id field, and use the soc_id for a more fine-grained distinction. > > Also, all three of these just come from the same register, why expose > > them all as the machine and revision standard properties. > > > > Agreed. These properties are basically giving same information but with > small modification. > As you said these are getting exposed via standard properties as well, > so I have no issue to drop them. Just waiting for more review from > Samsung folks, will take care of this in next version. Ok. Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v4 1/2] soc: samsung: add exynos chipid driver support Date: Thu, 04 Dec 2014 10:12:24 +0100 [thread overview] Message-ID: <4074205.TGQpWxTihh@wuerfel> (raw) In-Reply-To: <547FEA74.1010900@samsung.com> On Thursday 04 December 2014 10:30:36 Pankaj Dubey wrote: > > > > On Wednesday 03 December 2014 13:47:37 Pankaj Dubey wrote: > > > >> + soc_dev_attr->soc_id = exynos_product_id_to_name(soc_product_id); > >> + > >> + soc_dev = soc_device_register(soc_dev_attr); > >> + if (IS_ERR(soc_dev)) > >> + goto free_rev; > >> + > >> + device_create_file(soc_device_to_device(soc_dev), &exynos_product_attr); > >> + device_create_file(soc_device_to_device(soc_dev), > >> + &exynos_main_rev_attr); > >> + device_create_file(soc_device_to_device(soc_dev), &exynos_sub_rev_attr); > >> + > > > > I don't like the idea of having three extra nonstandard properties here, > > especially when you are not using the machine field for anything useful. > > > > I did not get you here. Any suggestions how we can use 'machine' field > more useful way. For instance you could pass the exynos_product_id_to_name() result to the machine field instead of the soc_id field, and use the soc_id for a more fine-grained distinction. > > Also, all three of these just come from the same register, why expose > > them all as the machine and revision standard properties. > > > > Agreed. These properties are basically giving same information but with > small modification. > As you said these are getting exposed via standard properties as well, > so I have no issue to drop them. Just waiting for more review from > Samsung folks, will take care of this in next version. Ok. Arnd
next prev parent reply other threads:[~2014-12-04 9:13 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-03 8:17 [PATCH v4 0/2] Introducing Exynos ChipId driver Pankaj Dubey 2014-12-03 8:17 ` Pankaj Dubey 2014-12-03 8:17 ` [PATCH v4 1/2] soc: samsung: add exynos chipid driver support Pankaj Dubey 2014-12-03 8:17 ` Pankaj Dubey 2014-12-03 10:43 ` Arnd Bergmann 2014-12-03 10:43 ` Arnd Bergmann 2014-12-04 5:00 ` Pankaj Dubey 2014-12-04 5:00 ` Pankaj Dubey 2014-12-04 9:12 ` Arnd Bergmann [this message] 2014-12-04 9:12 ` Arnd Bergmann [not found] ` <CAKew6eVTpu0qWQqd_sxqmRJF6qNMxJp5Mn0_ta5vO+pHAv66ug@mail.gmail.com> 2014-12-11 3:00 ` Pankaj Dubey 2014-12-11 3:00 ` Pankaj Dubey 2014-12-03 8:17 ` [PATCH v4 2/2] ARM: EXYNOS: refactoring of mach-exynos to enable chipid driver Pankaj Dubey 2014-12-03 8:17 ` Pankaj Dubey
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=4074205.TGQpWxTihh@wuerfel \ --to=arnd@arndb.de \ --cc=grant.likely@linaro.org \ --cc=heiko@sntech.de \ --cc=kgene.kim@samsung.com \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=pankaj.dubey@samsung.com \ --cc=robh+dt@kernel.org \ --cc=thomas.ab@samsung.com \ --cc=tomasz.figa@gmail.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: linkBe 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.