From: Miquel Raynal <miquel.raynal@bootlin.com>
To: William Zhang <william.zhang@broadcom.com>
Cc: Linux MTD List <linux-mtd@lists.infradead.org>,
Linux ARM List <linux-arm-kernel@lists.infradead.org>,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
f.fainelli@gmail.com, kursad.oney@broadcom.com,
joel.peshkin@broadcom.com, anand.gore@broadcom.com,
dregan@mail.com, kamal.dasu@broadcom.com,
tomer.yacoby@broadcom.com, dan.beygelman@broadcom.com,
David Regan <dregan@broadcom.com>,
linux-kernel@vger.kernel.org,
Vignesh Raghavendra <vigneshr@ti.com>,
Brian Norris <computersforpeace@gmail.com>,
Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH v6 12/13] mtd: rawnand: brcmnand: Add support for getting ecc setting from strap
Date: Thu, 29 Feb 2024 11:31:19 +0100 [thread overview]
Message-ID: <20240229113119.30f7cee6@xps-13> (raw)
In-Reply-To: <be75db7d-a698-43ab-b29e-dea3a0f60ba2@broadcom.com>
Hi William,
william.zhang@broadcom.com wrote on Mon, 26 Feb 2024 12:05:18 -0800:
> On 2/26/24 00:36, Miquel Raynal wrote:
> > Hi William,
> >
> > william.zhang@broadcom.com wrote on Fri, 23 Feb 2024 09:25:09 -0800:
> >
> >> Hi Miquel,
> >>
> >> On 2/23/24 01:18, Miquel Raynal wrote:
> >>> Hi William,
> >>>
> >>> william.zhang@broadcom.com wrote on Thu, 22 Feb 2024 19:47:57 -0800:
> >>> >>>> BCMBCA broadband SoC based board design does not specify ecc setting in
> >>>> dts but rather use the SoC NAND strap info to obtain the ecc strength
> >>>> and spare area size setting. Add brcm,nand-ecc-use-strap dts propety for
> >>>> this purpose and update driver to support this option. However these two
> >>>> options can not be used at the same time.
> >>>>
> >>>> Signed-off-by: William Zhang <william.zhang@broadcom.com>
> >>>> Reviewed-by: David Regan <dregan@broadcom.com>
> >>>> >>>
> >>> FYI I did not receive patches 7, 8, 9, which makes the series numbering
> >>> very odd.
> >>> >> I was using the get maintainer script mainly and it sends to the linux MTD list. I will add your email directly next time.
> >
> > Yes, I prefer to be in Cc of the whole series, please.
> >
> Sure. And thanks for applying other patches. Do you want me to just send a new single patch for the update?
Yes just the missing patch.
> >>>> >> +static int brcmnand_get_sector_size_1k(struct brcmnand_host *host)
> >>>> +{
> >>>> + struct brcmnand_controller *ctrl = host->ctrl;
> >>>> + int sector_size_bit = brcmnand_sector_1k_shift(ctrl);
> >>>> + u16 acc_control_offs = brcmnand_cs_offset(ctrl, host->cs,
> >>>> + BRCMNAND_CS_ACC_CONTROL);
> >>>> + u32 acc_control;
> >>>> +
> >>>> + if (sector_size_bit < 0)
> >>>> + return 0;
> >>>> +
> >>>> + acc_control = nand_readreg(ctrl, acc_control_offs);
> >>>> +
> >>>> + return (acc_control & BIT(sector_size_bit)) >> sector_size_bit;
> >>>
> >>> FIELD_PREP, FIELD_GET, *please*.
> >> You probably missed my reply to your comments on the same patch in v5. Here is the link for the post in case it lost in your email:
> >> https://lore.kernel.org/lkml/c145b90c-e9f0-4d82-94cc-baf7bfda5954@gmail.com/T/#m1d911d2f119f3bd345c575a81b60bc2bd8c461eb
> >
> > I didn't miss it, but the reason does not sound legitimate to me.
> > Please work on it, it will be so much cleaner.
> >
> I understand FIELD_PREP/GET is the preferred way of linux accessing the register fields but it requires a constant MASK value and does not apply to our case as we have different versions of the register and have different mask. There is way to workaround it. i.e defining the multiple constants directly and using these macros with if/else based on reg version. But it is not clean and since we already have helper functions that handle and return different shift/mask value, I see this is a perfect way for our situation and can adapt to future reg version change easily and cleanly.
>
> >> The mask is not constant here and cause build errors.
Which errors?
+ acc_control = nand_readreg(ctrl, acc_control_offs);
+ return FIELD_GET(BIT(sector_size_bit), acc_control);
Does not return any error here.
Thanks,
Miquèl
_______________________________________________
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:[~2024-02-29 10:31 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 3:47 [PATCH v6 00/13] mtd: rawnand: brcmnand: driver and doc updates William Zhang
2024-02-23 3:47 ` [PATCH v6 01/13] mtd: rawnand: brcmnand: exec_op helper functions return type fixes William Zhang
2024-02-23 4:20 ` Florian Fainelli
2024-02-26 10:44 ` Miquel Raynal
2024-02-23 3:47 ` [PATCH v6 02/13] mtd: rawnand: brcmnand: fix style issues William Zhang
2024-02-26 10:44 ` Miquel Raynal
2024-02-23 3:47 ` [PATCH v6 03/13] mtd: rawnand: brcmnand: update log level messages William Zhang
2024-02-26 10:44 ` Miquel Raynal
2024-02-23 3:47 ` [PATCH v6 04/13] dt-bindings: mtd: brcmnand: Updates for bcmbca SoCs William Zhang
2024-02-26 10:44 ` Miquel Raynal
2024-02-23 3:47 ` [PATCH v6 05/13] dt-bindings: mtd: brcmnand: Add WP pin connection property William Zhang
2024-02-26 10:44 ` Miquel Raynal
2024-02-23 3:47 ` [PATCH v6 06/13] dt-bindings: mtd: brcmnand: Add ecc strap property William Zhang
2024-02-23 18:47 ` Conor Dooley
2024-02-26 10:44 ` Miquel Raynal
2024-02-23 3:47 ` [PATCH v6 07/13] ARM: dts: broadcom: bcmbca: Add NAND controller node William Zhang
2024-02-26 10:44 ` Miquel Raynal
2024-02-23 3:47 ` [PATCH v6 08/13] arm64: " William Zhang
2024-02-26 10:44 ` Miquel Raynal
2024-02-23 3:47 ` [PATCH v6 09/13] arm64: dts: broadcom: bcmbca: Update router boards William Zhang
2024-02-26 10:44 ` Miquel Raynal
2024-02-23 3:47 ` [PATCH v6 10/13] mtd: rawnand: brcmnand: Rename bcm63138 nand driver William Zhang
2024-02-26 10:43 ` Miquel Raynal
2024-02-23 3:47 ` [PATCH v6 11/13] mtd: rawnand: brcmnand: Add BCMBCA read data bus interface William Zhang
2024-02-26 10:43 ` Miquel Raynal
2024-02-23 3:47 ` [PATCH v6 12/13] mtd: rawnand: brcmnand: Add support for getting ecc setting from strap William Zhang
2024-02-23 9:18 ` Miquel Raynal
2024-02-23 17:25 ` William Zhang
2024-02-26 8:36 ` Miquel Raynal
2024-02-26 20:05 ` William Zhang
2024-02-29 10:31 ` Miquel Raynal [this message]
2024-02-29 23:34 ` William Zhang
2024-02-23 3:47 ` [PATCH v6 13/13] mtd: rawnand: brcmnand: Support write protection setting from dts William Zhang
2024-02-26 10:43 ` Miquel Raynal
2024-02-26 17:36 ` [PATCH v6 00/13] mtd: rawnand: brcmnand: driver and doc updates Florian Fainelli
2024-02-29 9:11 ` Miquel Raynal
2024-02-29 17:32 ` Florian Fainelli
2024-03-14 22:04 ` Miquel Raynal
2024-03-14 23:02 ` Florian Fainelli
2024-03-14 23:03 ` Miquel Raynal
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=20240229113119.30f7cee6@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=dan.beygelman@broadcom.com \
--cc=dregan@broadcom.com \
--cc=dregan@mail.com \
--cc=f.fainelli@gmail.com \
--cc=joel.peshkin@broadcom.com \
--cc=kamal.dasu@broadcom.com \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=tomer.yacoby@broadcom.com \
--cc=vigneshr@ti.com \
--cc=william.zhang@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).