devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurentiu Mihalcea <laurentiumihalcea111@gmail.com>
To: Frank Li <Frank.li@nxp.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Daniel Baluta <daniel.baluta@nxp.com>,
	Shengjiu Wang <shengjiu.wang@nxp.com>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH v5 2/6] reset: imx8mp-audiomix: Replace mask with bit index
Date: Tue, 25 Nov 2025 01:59:31 -0800	[thread overview]
Message-ID: <4a022153-009c-44fd-8c4b-39819ae69390@gmail.com> (raw)
In-Reply-To: <aSR8q5cE/XXbZuF0@lizhi-Precision-Tower-5810>


On 11/24/2025 7:41 AM, Frank Li wrote:
> On Mon, Nov 24, 2025 at 01:28:32AM -0800, Laurentiu Mihalcea wrote:
>> On 11/21/2025 7:38 AM, Frank Li wrote:
>>> On Fri, Nov 14, 2025 at 05:37:34AM -0800, Laurentiu Mihalcea wrote:
>>>> From: Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
>>>>
>>>> Replace the reset map mask with the bit index to make it clear that all
>>>> reset lines are managed by exactly 1 bit.
>>> I don't think there are benefit because I met some periphal need a magic
>>> number to reset.
>>
>> Please provide more information. What SoC? Which peripherals? What block control?
>>
> I can't reminder exact one. I grep some code
>
> [IMX8MP_MEDIABLK_PD_LCDIF_1] = {
>                 .name = "mediablk-lcdif-1",
>                 .clk_names = (const char *[]){ "disp1", "apb", "axi", },
>                 .num_clks = 3,
>                 .gpc_name = "lcdif1",
>                 .rst_mask = BIT(4) | BIT(5) | BIT(23),
>                 .clk_mask = BIT(4) | BIT(5) | BIT(23),
>                 .path_names = (const char *[]){"lcdif-rd", "lcdif-wr"},
>                 .num_paths = 2,
>         },
>
> mask is more extenable and easily support more hardware in future. Change
> to bit number have not big benefit.


sure, I'm fine with the mask-based approach. The big idea here is to make this driver

usable in as many scenarios as possible.


Philipp, please let me know if you're okay with the proposal. Will also have to tweak

one of the subsequent patches since, so far, we've been operating under the assumption

that reset lines are 1 bit.


  reply	other threads:[~2025-11-25  9:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 13:37 [PATCH v5 0/6] Add support for i.MX8ULP's SIM LPAV Laurentiu Mihalcea
2025-11-14 13:37 ` [PATCH v5 1/6] reset: imx8mp-audiomix: Drop unneeded macros Laurentiu Mihalcea
2025-11-14 15:48   ` Philipp Zabel
2025-11-14 13:37 ` [PATCH v5 2/6] reset: imx8mp-audiomix: Replace mask with bit index Laurentiu Mihalcea
2025-11-14 15:48   ` Philipp Zabel
2025-11-21 15:38   ` Frank Li
2025-11-24  9:28     ` Laurentiu Mihalcea
2025-11-24 15:41       ` Frank Li
2025-11-25  9:59         ` Laurentiu Mihalcea [this message]
2025-11-25 10:40           ` Philipp Zabel
2025-11-25 23:34             ` Laurentiu Mihalcea
2025-11-14 13:37 ` [PATCH v5 3/6] reset: imx8mp-audiomix: Switch to using regmap API Laurentiu Mihalcea
2025-11-14 15:49   ` Philipp Zabel
2025-11-21 15:43   ` Frank Li
2025-11-14 13:37 ` [PATCH v5 4/6] reset: imx8mp-audiomix: Extend the driver usage Laurentiu Mihalcea
2025-11-14 16:02   ` Philipp Zabel
2025-11-21  9:29     ` Laurentiu Mihalcea
2025-11-21 15:18       ` Philipp Zabel
2025-11-14 13:37 ` [PATCH v5 5/6] reset: imx8mp-audiomix: Support i.MX8ULP SIM LPAV Laurentiu Mihalcea
2025-11-14 16:09   ` Philipp Zabel
2025-11-14 13:37 ` [PATCH v5 6/6] arm64: dts: imx8ulp: add sim lpav node Laurentiu Mihalcea

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=4a022153-009c-44fd-8c4b-39819ae69390@gmail.com \
    --to=laurentiumihalcea111@gmail.com \
    --cc=Frank.li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.baluta@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=shengjiu.wang@nxp.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).