From: Guenter Roeck <linux@roeck-us.net>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@stlinux.com,
rtc-linux@googlegroups.com, wim@iguana.be,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
david.paris@st.com
Subject: Re: [PATCH v2 6/9] watchdog: st_wdt: Add new driver for ST's LPC Watchdog
Date: Thu, 22 Jan 2015 11:31:45 -0800 [thread overview]
Message-ID: <54C15021.4060907@roeck-us.net> (raw)
In-Reply-To: <20150122172100.GF9129@x1>
On 01/22/2015 09:21 AM, Lee Jones wrote:
> On Thu, 22 Jan 2015, Guenter Roeck wrote:
>
>> On 01/22/2015 03:56 AM, Lee Jones wrote:
>>> Signed-off-by: David Paris <david.paris@st.com>
>>> Signed-off-by: Lee Jones <lee.jones@linaro.org>
>>> ---
>>> drivers/watchdog/Kconfig | 13 ++
>>> drivers/watchdog/Makefile | 1 +
>>> drivers/watchdog/st_lpc_wdt.c | 335 ++++++++++++++++++++++++++++++++++++++++++
>>> 3 files changed, 349 insertions(+)
>>> create mode 100644 drivers/watchdog/st_lpc_wdt.c
>
> [...]
>
>>> +struct st_wdog_syscfg {
>>> + struct regmap *regmap;
>>
>> Hi David & Lee,
>>
>> Why did you add the regmap pointer to this structure and not to st_wdog ?
>> It is not a configuration value, after all, and it is always dereferenced
>> through wt_wdog->syscfg. So all it does is to make the code more complicated.
>>
>> Am I missing something ?
>
> I guess it was just to group it all together, as it will all be used
> at the same time:
>
> regmap_update_bits(st_wdog->syscfg->regmap,
> st_wdog->syscfg->reset_type_reg,
> st_wdog->syscfg->reset_type_mask,
> st_wdog->warm_reset);
>
> It really doesn't matter to me either way.
>
Having it in syscfg means it is stored in the static configuration data instead
of the allocated data, which is at least conceptually wrong. So I think it should
be in st_wdog.
Thanks,
Guenter
next prev parent reply other threads:[~2015-01-22 19:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 11:55 [PATCH v2 0/9] mfd: watchdog: rtc: New driver for ST's LPC IP Lee Jones
2015-01-22 11:55 ` [PATCH v2 1/9] mfd: dt-bindings: Provide human readable defines for LPC mode choosing Lee Jones
2015-01-22 11:56 ` [PATCH v2 2/9] ARM: multi_v7_defconfig: Enable support for ST's LPC Watchdog Lee Jones
2015-01-22 11:56 ` [PATCH v2 3/9] ARM: multi_v7_defconfig: Enable support for ST's LPC RTC Lee Jones
2015-01-22 11:56 ` [PATCH v2 4/9] ARM: STi: DT: STiH407: Add Device Tree node for the LPC Lee Jones
2015-01-23 8:39 ` David Paris
2015-01-23 9:43 ` Lee Jones
2015-02-18 9:34 ` Lee Jones
2015-01-22 11:56 ` [PATCH v2 5/9] watchdog: bindings: Provide ST bindings for ST's LPC Watchdog device Lee Jones
2015-01-22 11:56 ` [PATCH v2 6/9] watchdog: st_wdt: Add new driver for ST's LPC Watchdog Lee Jones
2015-01-22 17:10 ` Guenter Roeck
2015-01-22 17:21 ` Lee Jones
2015-01-22 19:31 ` Guenter Roeck [this message]
2015-01-22 11:56 ` [PATCH v2 7/9] rtc: bindings: Provide ST bindings for ST's LPC RTC device Lee Jones
2015-01-22 11:56 ` [PATCH v2 8/9] rtc: st: add new driver for ST's LPC RTC Lee Jones
2015-01-22 11:56 ` [PATCH v2 9/9] MAINTAINERS: Add Watchdog and RTC files to STI's maintainer entry Lee Jones
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=54C15021.4060907@roeck-us.net \
--to=linux@roeck-us.net \
--cc=david.paris@st.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@stlinux.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=wim@iguana.be \
/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