All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shayne Chen <shayne.chen@mediatek.com>
To: Felix Fietkau <nbd@nbd.name>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
	Ryder Lee <ryder.lee@mediatek.com>,
	linux-mediatek <linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH] mt76: mt7915: add debugfs knob to read efuse value from FW
Date: Fri, 28 May 2021 22:20:25 +0800	[thread overview]
Message-ID: <1a8b17744553235236560734aac6f83ce782f3e3.camel@mediatek.com> (raw)
In-Reply-To: <32908981-c864-aa13-b182-8081610baa9c@nbd.name>

On Fri, 2021-05-28 at 10:56 +0200, Felix Fietkau wrote:
> On 2021-05-04 14:52, Shayne Chen wrote:
> > In efuse mode, mt7915 only reads efuse values from FW which driver
> > need.
> > Add a debugfs knob to read addtional efuse values from a specific
> > field,
> > which is useful in some cases such as checking if rf values in
> > efuse
> > are properly burned.
> > 
> > An example of usage:
> > echo 0x400 > efuse_idx
> > hexdump -C eeprom
> > 
> > Signed-off-by: Shayne Chen <shayne.chen@mediatek.com>
> 
> I'd prefer if we read the entire efuse and put it in a "otp" debugfs
> file, like on older chips.
> 
> - Felix

Hi Felix,

Got it. I'll send another patch, please drop this one.

Thanks,
Shayne

WARNING: multiple messages have this Message-ID (diff)
From: Shayne Chen <shayne.chen@mediatek.com>
To: Felix Fietkau <nbd@nbd.name>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
	Ryder Lee <ryder.lee@mediatek.com>,
	linux-mediatek <linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH] mt76: mt7915: add debugfs knob to read efuse value from FW
Date: Fri, 28 May 2021 22:20:25 +0800	[thread overview]
Message-ID: <1a8b17744553235236560734aac6f83ce782f3e3.camel@mediatek.com> (raw)
In-Reply-To: <32908981-c864-aa13-b182-8081610baa9c@nbd.name>

On Fri, 2021-05-28 at 10:56 +0200, Felix Fietkau wrote:
> On 2021-05-04 14:52, Shayne Chen wrote:
> > In efuse mode, mt7915 only reads efuse values from FW which driver
> > need.
> > Add a debugfs knob to read addtional efuse values from a specific
> > field,
> > which is useful in some cases such as checking if rf values in
> > efuse
> > are properly burned.
> > 
> > An example of usage:
> > echo 0x400 > efuse_idx
> > hexdump -C eeprom
> > 
> > Signed-off-by: Shayne Chen <shayne.chen@mediatek.com>
> 
> I'd prefer if we read the entire efuse and put it in a "otp" debugfs
> file, like on older chips.
> 
> - Felix

Hi Felix,

Got it. I'll send another patch, please drop this one.

Thanks,
Shayne
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

  reply	other threads:[~2021-05-28 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 12:52 [PATCH] mt76: mt7915: add debugfs knob to read efuse value from FW Shayne Chen
2021-05-04 12:52 ` Shayne Chen
2021-05-28  8:56 ` Felix Fietkau
2021-05-28  8:56   ` Felix Fietkau
2021-05-28 14:20   ` Shayne Chen [this message]
2021-05-28 14:20     ` Shayne Chen

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=1a8b17744553235236560734aac6f83ce782f3e3.camel@mediatek.com \
    --to=shayne.chen@mediatek.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=nbd@nbd.name \
    --cc=ryder.lee@mediatek.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.