From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752278AbcAFMTS (ORCPT ); Wed, 6 Jan 2016 07:19:18 -0500 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:38209 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751960AbcAFMTP (ORCPT ); Wed, 6 Jan 2016 07:19:15 -0500 Date: Wed, 6 Jan 2016 12:18:57 +0000 From: Mark Brown To: Laxman Dewangan Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, lgirdwood@gmail.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Message-ID: <20160106121857.GW6588@sirena.org.uk> References: <1452060922-24426-1-git-send-email-ldewangan@nvidia.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Wt10+cXOThorkX0z" Content-Disposition: inline In-Reply-To: <1452060922-24426-1-git-send-email-ldewangan@nvidia.com> X-Cookie: APL hackers do it in the quad. User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: 94.175.94.161 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH 1/1] regulator: max8973: add support for junction thermal warning X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --Wt10+cXOThorkX0z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Jan 06, 2016 at 11:45:22AM +0530, Laxman Dewangan wrote: > Enhanced transient response (ETR) will affect the configuration of CKADV. > +-maxim,junction-temp-warning: Junction temp warning on which device generates > + warning interrupts. This needs to specify what the values are - it looks like it's raw register values but I'd have expected from this that it'd be an actual temperature. > +-interrupt-flags: Interrupt flags for registering interrupt which can not be > + passed via interrupt properties. Why is this being specified and what are the values? Most devices don't have this... --Wt10+cXOThorkX0z Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWjQYwAAoJECTWi3JdVIfQ7koH/3gFVEW6aerJ/Phss435CRBg 0qHc74KVubTyaD72nVpuhSi04HBWo5LWAX9yLjfd6waugJtEthx/It4kZBnFGurK CM7Sc/5x99CZcO9Nyn0Y6EqO6BKIq7huLFJZHo1vvRc4F2SzmQOx+VbEnO8ARX20 /xg5FRUcfeOUPk0r/0bmEH4H1dOhk+P1VaJ9RX29QPjYCqWwjyqRCiyfDGqeyt8J qG0jeAiK9ZftPzOdyHAn/ydqscCvdMLlCuEzbeSD0953xf3E7INgzlOuV/Mm9asU QTyFVCmG8knWaYDfu2qQHrzKDb2c9ReI0MIMsOXe8ey+hZY1nzaBQBNmqTEoV6Y= =zj6H -----END PGP SIGNATURE----- --Wt10+cXOThorkX0z-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH 1/1] regulator: max8973: add support for junction thermal warning Date: Wed, 6 Jan 2016 12:18:57 +0000 Message-ID: <20160106121857.GW6588@sirena.org.uk> References: <1452060922-24426-1-git-send-email-ldewangan@nvidia.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Wt10+cXOThorkX0z" Return-path: Content-Disposition: inline In-Reply-To: <1452060922-24426-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Laxman Dewangan Cc: robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, pawel.moll-5wv7dgnIgG8@public.gmane.org, mark.rutland-5wv7dgnIgG8@public.gmane.org, ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org, galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org, lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: devicetree@vger.kernel.org --Wt10+cXOThorkX0z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Jan 06, 2016 at 11:45:22AM +0530, Laxman Dewangan wrote: > Enhanced transient response (ETR) will affect the configuration of CKADV. > +-maxim,junction-temp-warning: Junction temp warning on which device generates > + warning interrupts. This needs to specify what the values are - it looks like it's raw register values but I'd have expected from this that it'd be an actual temperature. > +-interrupt-flags: Interrupt flags for registering interrupt which can not be > + passed via interrupt properties. Why is this being specified and what are the values? Most devices don't have this... --Wt10+cXOThorkX0z Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWjQYwAAoJECTWi3JdVIfQ7koH/3gFVEW6aerJ/Phss435CRBg 0qHc74KVubTyaD72nVpuhSi04HBWo5LWAX9yLjfd6waugJtEthx/It4kZBnFGurK CM7Sc/5x99CZcO9Nyn0Y6EqO6BKIq7huLFJZHo1vvRc4F2SzmQOx+VbEnO8ARX20 /xg5FRUcfeOUPk0r/0bmEH4H1dOhk+P1VaJ9RX29QPjYCqWwjyqRCiyfDGqeyt8J qG0jeAiK9ZftPzOdyHAn/ydqscCvdMLlCuEzbeSD0953xf3E7INgzlOuV/Mm9asU QTyFVCmG8knWaYDfu2qQHrzKDb2c9ReI0MIMsOXe8ey+hZY1nzaBQBNmqTEoV6Y= =zj6H -----END PGP SIGNATURE----- --Wt10+cXOThorkX0z-- -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html