All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "Miclaus, Antoniu" <Antoniu.Miclaus@analog.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org"
	<krzysztof.kozlowski+dt@linaro.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"jdelvare@suse.com" <jdelvare@suse.com>,
	"noname.nuno@gmail.com" <noname.nuno@gmail.com>,
	"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
	Ibrahim Tilki <Ibrahim.Tilki@analog.com>,
	"Arslanbenzer, Zeynep" <Zeynep.Arslanbenzer@analog.com>
Subject: Re: [PATCH v6 2/2] dt-bindings: rtc: add max313xx RTCs
Date: Wed, 7 Feb 2024 07:00:53 -0800	[thread overview]
Message-ID: <392dbedc-6b5b-48f6-a7f2-94a2aa6bbc33@roeck-us.net> (raw)
In-Reply-To: <CY4PR03MB3399844E78F84B6CFA18280A9B452@CY4PR03MB3399.namprd03.prod.outlook.com>

On 2/7/24 01:54, Miclaus, Antoniu wrote:
[ ... ]
>>
>> The max31335 is not available
>>
>   
> Indeed, the max31355 datasheet is not available yet. This is also stated in the
> cover letter of the patch series for max31335.
> 
> It was an urgent request from a customer to have it mainline as soon as possible.
> 
> If there are questions about the part functionality, I can definitely help.
> 

It seems to be quite common for automotive chips, though, that they are held
tightly under wrap, making it all but impossible to properly review their drivers.
I have observed several times now that information not available to reviewers
resulted in bad or buggy drivers. This isn't about willingness to help, it is
about the ability to understand chip capabilities and requirements.

Guenter


      reply	other threads:[~2024-02-07 15:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02  2:52 [PATCH v6 0/2] drivers: rtc: add max313xx series rtc driver Chris Packham
2024-02-02  2:52 ` [PATCH v6 1/2] " Chris Packham
2024-02-03  7:07   ` kernel test robot
2024-02-04  2:25   ` kernel test robot
2024-02-02  2:52 ` [PATCH v6 2/2] dt-bindings: rtc: add max313xx RTCs Chris Packham
2024-02-02  8:28   ` Krzysztof Kozlowski
2024-02-06 20:21     ` Chris Packham
     [not found]     ` <5d4b7fa1-5cc2-4a4a-8fa4-d2c7a8d070b7@alliedtelesis.co.nz>
2024-02-06 21:12       ` Alexandre Belloni
2024-02-06 21:41         ` Chris Packham
2024-02-06 22:16           ` Alexandre Belloni
2024-02-07  9:54             ` Miclaus, Antoniu
2024-02-07 15:00               ` Guenter Roeck [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=392dbedc-6b5b-48f6-a7f2-94a2aa6bbc33@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=Antoniu.Miclaus@analog.com \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=Ibrahim.Tilki@analog.com \
    --cc=Zeynep.Arslanbenzer@analog.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=noname.nuno@gmail.com \
    --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 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.