public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <robert.hancock@calian.com>
To: "mike.looijmans@topic.nl" <mike.looijmans@topic.nl>,
	"mturquette@baylibre.com" <mturquette@baylibre.com>,
	"sboyd@kernel.org" <sboyd@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Subject: Re: [PATCH 8/9] clk: si5341: Add silabs,iovdd-33 property
Date: Fri, 12 Mar 2021 15:39:31 +0000	[thread overview]
Message-ID: <c49900a1b9179e081be4a36e605abc61d2ac6bf7.camel@calian.com> (raw)
In-Reply-To: <81e8670c-d302-ff20-1767-4a6befe34a0e@topic.nl>

On Fri, 2021-03-12 at 07:44 +0100, Mike Looijmans wrote:
> Met vriendelijke groet / kind regards,
> 
> Mike Looijmans
> System Expert
> 
> 
> TOPIC Embedded Products B.V.
> Materiaalweg 4, 5681 RJ Best
> The Netherlands
> 
> T: +31 (0) 499 33 69 69
> E: mike.looijmans@topicproducts.com
> W: 
> https://urldefense.com/v3/__http://www.topicproducts.com__;!!IOGos0k!1ZKoWVwv09fDC-o4jRw92NZvHBl_3MOcBIPl8DLLDN0szJlo9IH0GC-6qH0-Pq1W-PA$
>  
> 
> Please consider the environment before printing this e-mail
> On 11-03-2021 23:24, Robert Hancock wrote:
> > Add a property to allow specifying that the external I2C IO pins are using
> > 3.3V voltage thresholds rather than 1.8V.
> > 
> > Signed-off-by: Robert Hancock <robert.hancock@calian.com>
> > ---
> >   drivers/clk/clk-si5341.c | 10 +++++++++-
> >   1 file changed, 9 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/clk/clk-si5341.c b/drivers/clk/clk-si5341.c
> > index 11740855bcde..4cd80ef389d2 100644
> > --- a/drivers/clk/clk-si5341.c
> > +++ b/drivers/clk/clk-si5341.c
> > @@ -81,6 +81,7 @@ struct clk_si5341 {
> >   	u8 num_synth;
> >   	u16 chip_id;
> >   	bool xaxb_ext_clk;
> > +	bool iovdd_33;
> >   };
> >   #define to_clk_si5341(_hw)	container_of(_hw, struct clk_si5341,
> > hw)
> >   
> > @@ -103,6 +104,7 @@ struct clk_si5341_output_config {
> >   #define SI5341_IN_SEL		0x0021
> >   #define SI5341_DEVICE_READY	0x00FE
> >   #define SI5341_XAXB_CFG		0x090E
> > +#define SI5341_IO_VDD_SEL	0x0943
> >   #define SI5341_IN_EN		0x0949
> >   #define SI5341_INX_TO_PFD_EN	0x094A
> >   
> > @@ -351,7 +353,6 @@ static const struct si5341_reg_default
> > si5341_reg_defaults[] = {
> >   	{ 0x0804, 0x00 }, /* Not in datasheet */
> >   	{ 0x090E, 0x02 }, /* XAXB_EXTCLK_EN=0 XAXB_PDNB=1 (use XTAL) */
> >   	{ 0x091C, 0x04 }, /* ZDM_EN=4 (Normal mode) */
> > -	{ 0x0943, 0x00 }, /* IO_VDD_SEL=0 (0=1v8, use 1=3v3) */
> >   	{ 0x0949, 0x00 }, /* IN_EN (disable input clocks) */
> >   	{ 0x094A, 0x00 }, /* INx_TO_PFD_EN (disabled) */
> >   	{ 0x0A02, 0x00 }, /* Not in datasheet */
> > @@ -1160,6 +1161,11 @@ static int si5341_finalize_defaults(struct
> > clk_si5341 *data)
> >   	int res;
> >   	u32 revision;
> >   
> > +	res = regmap_write(data->regmap, SI5341_IO_VDD_SEL,
> > +			   data->iovdd_33 ? 1 : 0);
> > +	if (res < 0)
> > +		return res;
> > +
> >   	res = regmap_read(data->regmap, SI5341_DEVICE_REV, &revision);
> >   	if (res < 0)
> >   		return res;
> > @@ -1565,6 +1571,8 @@ static int si5341_probe(struct i2c_client *client,
> >   	}
> >   	data->xaxb_ext_clk = of_property_read_bool(client->dev.of_node,
> >   						   "silabs,xaxb-ext-clk");
> > +	data->iovdd_33 = of_property_read_bool(client->dev.of_node,
> > +					       "silabs,iovdd-33");
> >   
> 
> Seems a waste to me to store this in the 'data' object forever while it 
> is to be used only once during init and never again after that.

That is true, but it would then have to be passed down into the
si5341_finalize_defaults function separately and it would be inconsistent with
how all of the other configuration is handled. So I'm not sure it's worth
saving ~ 1 byte in the data object..

> 
> 
> >   	if (initialization_required) {
> >   		/* Populate the regmap cache in preparation for "cache only" */
> 
> 

  reply	other threads:[~2021-03-12 15:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 22:24 [PATCH 0/9] Si5341 driver updates Robert Hancock
     [not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.b1dc66c0-d7df-44f1-9f1a-e729e77f49c2@emailsignatures365.codetwo.com>
     [not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.9334a909-9494-43d0-954a-ed0ddcbb7b5d@emailsignatures365.codetwo.com>
     [not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.a5c64a18-101d-4705-9716-1c41c644d43a@emailsignatures365.codetwo.com>
2021-03-11 22:24 ` [PATCH 1/9] dt-bindings: clock: clk-si5341: Add new attributes Robert Hancock
2021-03-11 22:24 ` [PATCH 2/9] clk: si5341: Wait for DEVICE_READY on startup Robert Hancock
2021-03-12  6:39   ` Mike Looijmans
2021-03-12 15:23     ` Robert Hancock
2021-03-11 22:24 ` [PATCH 3/9] clk: si5341: Avoid divide errors due to bogus register contents Robert Hancock
2021-03-11 22:24 ` [PATCH 4/9] clk: si5341: Check for input clock presence and PLL lock on startup Robert Hancock
2021-03-12  6:47   ` Mike Looijmans
2021-03-12 15:23     ` Robert Hancock
2021-03-11 22:24 ` [PATCH 5/9] clk: si5341: Update initialization magic Robert Hancock
2021-03-11 22:24 ` [PATCH 6/9] clk: si5341: Allow different output VDD_SEL values Robert Hancock
2021-03-12  0:09   ` kernel test robot
2021-03-12  0:09   ` [RFC PATCH] clk: si5341: si5341_remove() can be static kernel test robot
2021-03-12  0:48   ` [PATCH 6/9] clk: si5341: Allow different output VDD_SEL values kernel test robot
2021-03-11 22:24 ` [PATCH 7/9] clk: si5341: Add silabs,xaxb-ext-clk property Robert Hancock
2021-03-11 22:24 ` [PATCH 8/9] clk: si5341: Add silabs,iovdd-33 property Robert Hancock
2021-03-12  6:44   ` Mike Looijmans
2021-03-12 15:39     ` Robert Hancock [this message]
2021-03-11 22:24 ` [PATCH 9/9] clk: si5341: Add sysfs properties to allow checking/resetting device faults Robert Hancock

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=c49900a1b9179e081be4a36e605abc61d2ac6bf7.camel@calian.com \
    --to=robert.hancock@calian.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mike.looijmans@topic.nl \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox