From: Billy Tsai <billy_tsai@aspeedtech.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "lars@metafoo.de" <lars@metafoo.de>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"joel@jms.id.au" <joel@jms.id.au>,
"andrew@aj.id.au" <andrew@aj.id.au>,
"colin.king@canonical.com" <colin.king@canonical.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
BMC-SW <BMC-SW@aspeedtech.com>
Subject: Re: [PATCH 1/2] iio: adc: aspeed: Remove the trim valid dts property.
Date: Mon, 7 Nov 2022 02:34:51 +0000 [thread overview]
Message-ID: <16211538-3501-4A32-96B5-1AD1BF933CA5@aspeedtech.com> (raw)
In-Reply-To: <20221106144949.61731d8e@jic23-huawei>
On 2022/11/6, 10:50 PM, "Jonathan Cameron" <jic23@kernel.org> wrote:
On Mon, 31 Oct 2022 19:32:07 +0800
Billy Tsai <billy_tsai@aspeedtech.com> wrote:
> > The dts property "aspeed,trim-data-valid" is used to determin whether to
> > read the OTP register. If the image with the aspeed,trim-data-vali
> > install to the chip without valid trimming data the adc controller will
> > become confused. This patch use the default otp value 0 as a criterion
> > for determining whether trimming data is valid instead of the dts
> > property. The chip with actually trimming value is 0 should be filter out.
> Hi Billy,
> I'm not sure I correctly follow the patch description. Would the following
> be an accurate description?
> The dts property "aspeed,trim-data-valid" is currently used to determine
> whether to read trimming data from the OTP register. If this is set on
> a device without valid trimming data in the OTP the ADC will not function
> correctly. This patch drops he use of this property and instead uses the
> default (unprogrammed) OTP value of 0 to detect when a fallback value of
> 0x8 should be used rather then the value read from the OTP.
Hi Jonathan,
Yes, it's correct.
> Also, is this a bug fix we need to backport? If so please provide a fixes
> tag.
I will provide the fixes tag in next version of patch.
Thanks
Best Regards,
Billy Tsai
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-11-07 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 11:32 [PATCH 1/2] iio: adc: aspeed: Remove the trim valid dts property Billy Tsai
2022-10-31 11:32 ` [PATCH 2/2] dt-bindings: iio: adc: Remove the property "aspeed,trim-data-valid" Billy Tsai
2022-11-02 16:07 ` Rob Herring
2022-11-06 14:49 ` [PATCH 1/2] iio: adc: aspeed: Remove the trim valid dts property Jonathan Cameron
2022-11-07 2:34 ` Billy Tsai [this message]
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=16211538-3501-4A32-96B5-1AD1BF933CA5@aspeedtech.com \
--to=billy_tsai@aspeedtech.com \
--cc=BMC-SW@aspeedtech.com \
--cc=andrew@aj.id.au \
--cc=colin.king@canonical.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=joel@jms.id.au \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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