From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Sangbeom Kim <sbkim73@samsung.com>,
Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org,
Kyungmin Park <kyungmin.park@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH 2/2] mfd: sec-core: Update sec_pmic documentation
Date: Fri, 18 Apr 2014 09:59:22 +0200 [thread overview]
Message-ID: <1397807962.29800.10.camel@AMDC1943> (raw)
In-Reply-To: <20140417083258.GH28725@lee--X1>
On czw, 2014-04-17 at 09:32 +0100, Lee Jones wrote:
> > Update the documentation for sec_pmic state container structure to
> > reflect current code.
> >
> > Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> > ---
> > include/linux/mfd/samsung/core.h | 29 +++++++++++++++++------------
> > 1 file changed, 17 insertions(+), 12 deletions(-)
> >
> > diff --git a/include/linux/mfd/samsung/core.h b/include/linux/mfd/samsung/core.h
> > index 2633083262ea..1923fe026c01 100644
> > --- a/include/linux/mfd/samsung/core.h
> > +++ b/include/linux/mfd/samsung/core.h
> > @@ -24,18 +24,23 @@ enum sec_device_type {
> > };
> >
> > /**
> > - * struct sec_pmic_dev - s5m87xx master device for sub-drivers
> > - * @dev: master device of the chip (can be used to access platform data)
> > - * @pdata: pointer to private data used to pass platform data to child
> > - * @i2c: i2c client private data for regulator
> > - * @iolock: mutex for serializing io access
> > - * @irqlock: mutex for buslock
> > - * @irq_base: base IRQ number for sec-pmic, required for IRQs
> > - * @irq: generic IRQ number for s5m87xx
> > - * @ono: power onoff IRQ number for s5m87xx
> > - * @irq_masks_cur: currently active value
> > - * @irq_masks_cache: cached hardware value
> > - * @type: indicate which s5m87xx "variant" is used
> > + * struct sec_pmic_dev - s2m/s5m master device for sub-drivers
> > + * @dev: Master device of the chip (can be used to access
> > + * platform data)
>
> Please remove the part in ()'s.
OK
>
> a) There's no need for it - we know what's in 'struct device' and b)
> if 'struct platform_data' is removed from 'struct device' this comment
> will become incorrect. Easy maintainability and all that ...
>
> > + * @pdata: Platform data from DTS or board files
>
> s/from/populated with data from
OK
>
> > + * @regmap_pmic: Regmap associated with PMIC's I2C address
> > + * @i2c: I2C client of the main driver
> > + * @device_type: Type of device, matches enum sec_device_type
> > + * @irq_base: Base IRQ number for device, required for IRQs
>
> Is there any reason for not using IRQ Domains?
No, I have it in my TODO list.
>
> > + * @irq: Generic IRQ number for device
> > + * @irq_data: Runtime data structure for IRQ controller
> > + * @ono: Power onoff IRQ number for s5m87xx
>
> Perhaps consider a better name for this in a future patch.
Actually I couldn't find usage of it so I plan to do some cleanup and
get rid of it.
Thanks for review.
Best regards,
Krzysztof
>
> > + * @wakeup: Whether or not this is a wakeup device
> > + * @wtsr_smpl: Whether or not to enable in RTC driver the Watchdog
> > + * Timer Software Reset (registers set to default value
> > + * after PWRHOLD falling) and Sudden Momentary Power Loss
> > + * (PMIC will enter power on sequence after short drop in
> > + * VBATT voltage).
> > */
> > struct sec_pmic_dev {
> > struct device *dev;
>
next prev parent reply other threads:[~2014-04-18 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 12:03 [PATCH 1/2] mfd: sec-core: Remove duplicated device type from sec_pmic Krzysztof Kozlowski
2014-04-14 12:03 ` [PATCH 2/2] mfd: sec-core: Update sec_pmic documentation Krzysztof Kozlowski
2014-04-17 8:32 ` Lee Jones
2014-04-18 7:59 ` Krzysztof Kozlowski [this message]
2014-04-17 8:26 ` [PATCH 1/2] mfd: sec-core: Remove duplicated device type from sec_pmic Lee Jones
2014-04-18 7:54 ` Krzysztof Kozlowski
2014-04-22 8:09 ` Lee Jones
2014-04-22 8:41 ` Krzysztof Kozlowski
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=1397807962.29800.10.camel@AMDC1943 \
--to=k.kozlowski@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=sameo@linux.intel.com \
--cc=sbkim73@samsung.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 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.