From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Maxime Ripard <maxime@cerno.tech>,
Tomasz Figa <tfiga@chromium.org>,
Robert Foss <robert.foss@linaro.org>,
Dongchun Zhu <dongchun.zhu@mediatek.com>,
Fabio Estevam <festevam@gmail.com>,
linux-media <linux-media@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH v6 1/3] media: dt-bindings: ov8856: Document YAML bindings
Date: Wed, 8 Apr 2020 19:34:54 +0300 [thread overview]
Message-ID: <20200408163454.GG3676135@smile.fi.intel.com> (raw)
In-Reply-To: <20200408153051.GP6127@valkosipuli.retiisi.org.uk>
On Wed, Apr 08, 2020 at 06:30:51PM +0300, Sakari Ailus wrote:
> On Wed, Apr 08, 2020 at 06:28:57PM +0300, Sakari Ailus wrote:
> > On Wed, Apr 08, 2020 at 03:43:15PM +0200, Maxime Ripard wrote:
...
> > No sensor driver I've seen has used clk_set_rate_exclusive() but I guess
> > they should. The absence of practical problems has been probably because of
> > two factors; firstly, these are typically clocks dedicated to the sensors
> > and secondly, good luck.
As I heard in another thread clk_*_exclusive() is quite a big hammer with a lot
of side effects and if it can be avoided, it must be avoided.
--
With Best Regards,
Andy Shevchenko
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Maxime Ripard <maxime@cerno.tech>,
linux-kernel <linux-kernel@vger.kernel.org>,
Robert Foss <robert.foss@linaro.org>,
Tomasz Figa <tfiga@chromium.org>,
Dongchun Zhu <dongchun.zhu@mediatek.com>,
Fabio Estevam <festevam@gmail.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH v6 1/3] media: dt-bindings: ov8856: Document YAML bindings
Date: Wed, 8 Apr 2020 19:34:54 +0300 [thread overview]
Message-ID: <20200408163454.GG3676135@smile.fi.intel.com> (raw)
In-Reply-To: <20200408153051.GP6127@valkosipuli.retiisi.org.uk>
On Wed, Apr 08, 2020 at 06:30:51PM +0300, Sakari Ailus wrote:
> On Wed, Apr 08, 2020 at 06:28:57PM +0300, Sakari Ailus wrote:
> > On Wed, Apr 08, 2020 at 03:43:15PM +0200, Maxime Ripard wrote:
...
> > No sensor driver I've seen has used clk_set_rate_exclusive() but I guess
> > they should. The absence of practical problems has been probably because of
> > two factors; firstly, these are typically clocks dedicated to the sensors
> > and secondly, good luck.
As I heard in another thread clk_*_exclusive() is quite a big hammer with a lot
of side effects and if it can be avoided, it must be avoided.
--
With Best Regards,
Andy Shevchenko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-04-08 16:34 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 13:33 [PATCH v3 0/3] media: ov8856: Add devicetree support Robert Foss
2020-03-31 13:33 ` Robert Foss
2020-03-31 13:33 ` [PATCH v6 1/3] media: dt-bindings: ov8856: Document YAML bindings Robert Foss
2020-03-31 13:33 ` Robert Foss
2020-03-31 15:12 ` Marco Felsch
2020-03-31 15:12 ` Marco Felsch
2020-04-02 9:57 ` Robert Foss
2020-04-02 9:57 ` Robert Foss
2020-04-03 19:21 ` Marco Felsch
2020-04-03 19:21 ` Marco Felsch
2020-04-01 8:07 ` Maxime Ripard
2020-04-01 8:07 ` Maxime Ripard
2020-04-02 10:10 ` Robert Foss
2020-04-02 10:10 ` Robert Foss
2020-04-03 23:27 ` Sakari Ailus
2020-04-03 23:27 ` Sakari Ailus
2020-04-04 9:34 ` Maxime Ripard
2020-04-04 9:34 ` Maxime Ripard
2020-04-06 8:25 ` Robert Foss
2020-04-06 8:25 ` Robert Foss
2020-04-06 8:35 ` Sakari Ailus
2020-04-06 8:35 ` Sakari Ailus
2020-04-07 8:36 ` Maxime Ripard
2020-04-07 8:36 ` Maxime Ripard
2020-04-07 11:29 ` Robert Foss
2020-04-07 11:29 ` Robert Foss
2020-04-07 12:32 ` Maxime Ripard
2020-04-07 12:32 ` Maxime Ripard
2020-04-07 15:47 ` Robert Foss
2020-04-07 15:47 ` Robert Foss
2020-04-07 16:39 ` Sakari Ailus
2020-04-07 16:39 ` Sakari Ailus
2020-04-07 16:46 ` Tomasz Figa
2020-04-07 16:46 ` Tomasz Figa
2020-04-07 17:20 ` Sakari Ailus
2020-04-07 17:20 ` Sakari Ailus
2020-04-08 12:21 ` Maxime Ripard
2020-04-08 12:21 ` Maxime Ripard
2020-04-08 12:35 ` Tomasz Figa
2020-04-08 12:35 ` Tomasz Figa
2020-04-08 13:43 ` Maxime Ripard
2020-04-08 13:43 ` Maxime Ripard
2020-04-08 15:28 ` Sakari Ailus
2020-04-08 15:28 ` Sakari Ailus
2020-04-08 15:30 ` Sakari Ailus
2020-04-08 15:30 ` Sakari Ailus
2020-04-08 16:34 ` Andy Shevchenko [this message]
2020-04-08 16:34 ` Andy Shevchenko
2020-04-15 10:18 ` Maxime Ripard
2020-04-15 10:18 ` Maxime Ripard
2020-04-15 11:10 ` Robert Foss
2020-04-15 11:10 ` Robert Foss
2020-04-15 16:16 ` Sakari Ailus
2020-04-15 16:16 ` Sakari Ailus
2020-04-20 15:02 ` Maxime Ripard
2020-04-20 15:02 ` Maxime Ripard
2020-04-09 8:32 ` Robert Foss
2020-04-09 8:32 ` Robert Foss
2020-04-07 16:20 ` Sakari Ailus
2020-04-07 16:20 ` Sakari Ailus
2020-04-04 9:23 ` Maxime Ripard
2020-04-04 9:23 ` Maxime Ripard
2020-03-31 13:33 ` [PATCH v3 2/3] media: ov8856: Add devicetree support Robert Foss
2020-03-31 13:33 ` Robert Foss
2020-03-31 14:01 ` Andy Shevchenko
2020-03-31 14:01 ` Andy Shevchenko
2020-04-06 13:37 ` Robert Foss
2020-04-06 13:37 ` Robert Foss
2020-04-06 15:06 ` Andy Shevchenko
2020-04-06 15:06 ` Andy Shevchenko
2020-04-06 15:25 ` Robert Foss
2020-04-06 15:25 ` Robert Foss
2020-04-03 23:33 ` Sakari Ailus
2020-04-03 23:33 ` Sakari Ailus
2020-03-31 13:33 ` [PATCH v3 3/3] media: ov8856: Implement sensor module revision identification Robert Foss
2020-03-31 13:33 ` Robert Foss
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=20200408163454.GG3676135@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dongchun.zhu@mediatek.com \
--cc=festevam@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=robert.foss@linaro.org \
--cc=sakari.ailus@iki.fi \
--cc=tfiga@chromium.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 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.