Linux I2C development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>,
	peda@axentia.se, p.zabel@pengutronix.de
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: muxes: pca954x: Allow sharing reset GPIO
Date: Mon, 11 Mar 2024 07:25:30 +0100	[thread overview]
Message-ID: <6785b149-a2bc-44ea-aec3-8477222d338b@linaro.org> (raw)
In-Reply-To: <20240311041412.3858710-1-chris.packham@alliedtelesis.co.nz>

On 11/03/2024 05:14, Chris Packham wrote:
> Some hardware designs with multiple PCA954x devices use a reset GPIO
> connected to all the muxes. Support this configuration by making use of
> the reset controller framework which can deal with the shared reset
> GPIOs. Fall back to the old GPIO descriptor method if the reset
> controller framework is not enabled.
> 
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
> 
> Notes:
>     This patch goes on top of Krzysztof's series adding the GPIO based reset
>     controller[1] which will be in linux-6.9. With this I'm able to
>     correctly describe my hardware platform in the DTS and have the resets
>     appropriately controlled.
>     
>     [1] - https://lore.kernel.org/all/20240129115216.96479-1-krzysztof.kozlowski@linaro.org/
> 

Where is the changelog? It was v3 or v4 already? Where are the tags?

It looks like you received a tag and forgot to add it.

If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new
versions, under or above your Signed-off-by tag. Tag is "received", when
provided in a message replied to you on the mailing list. Tools like b4
can help here. However, there's no need to repost patches *only* to add
the tags. The upstream maintainer will do that for tags received on the
version they apply.

https://elixir.bootlin.com/linux/v6.5-rc3/source/Documentation/process/submitting-patches.rst#L577

If a tag was not added on purpose, please state why and what changed.

Best regards,
Krzysztof


  reply	other threads:[~2024-03-11  6:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11  4:14 [PATCH] i2c: muxes: pca954x: Allow sharing reset GPIO Chris Packham
2024-03-11  6:25 ` Krzysztof Kozlowski [this message]
2024-03-11 20:07   ` Chris Packham
2024-06-06 21:58 ` Eddie James
2024-06-07  6:46   ` Krzysztof Kozlowski
  -- strict thread matches above, loose matches on Subject: below --
2024-01-08  4:19 Chris Packham
2024-01-11  8:53 ` Krzysztof Kozlowski
2024-01-11  9:27 ` Peter Rosin

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=6785b149-a2bc-44ea-aec3-8477222d338b@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=peda@axentia.se \
    /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